[HOME] [NSRG] [インフラ] [fml4] [fml8] [北海道] [おすすめの本] Powered by NetBSD and [nuinui.net] .

Troubleshoot

1. I want to know fml version.
2. Check Postfix version.
3. Check Sendmail version.
4. List up pre-defined addresses on this host.
5. List up defined aliases on this host
6. List up all ML addresses containing the specific member address.

1. I want to know fml version.

[Example: in the case of "test" ML]
% fmlconf test fml_version
fml_version                          = fml-devel current-20021029

2. Check Postfix version.

% postconf mail_version

3. Check Sendmail version.

% echo '$v' | sendmail -bt

4. List up pre-defined addresses on this host.

"fmladdr" command lists up users defined at both /etc/passwd and aliases.

% fmladdr

Warning

The difference between "fmladdr" and "fmlalias" is whether it contains users defined at /etc/passwd or not. "fmladdr" contains it but fmlalias not. "fmlalias" lists up only users defined at aliases.

5. List up defined aliases on this host

Run "fmlalias". It shows all addresses defined in aliases files.

% fmlalias

Warning

The difference between "fmladdr" and "fmlalias" is whether it contains users defined at /etc/passwd or not. "fmladdr" contains it but fmlalias not. "fmlalias" lists up only users defined at aliases.

6. List up all ML addresses containing the specific member address.

For each ML, run the following command:

% fml ML list |grep ADDRESS

When The File System Error Ocuurs

When the file system error occurs, fml8 exit abnormally to make MTA re-deliver the message again to fml8 or fml8 re-delivers it by itself without saving the article on the file system. So fml8 do not lost received messages whereas both log or summary file lack something.

Describe below what happans when the file system error occurs in the delivery process.

When Passed From MTA MTA To fml8

fml8 reads a message and writes it into the disk once. If succeeded, it processes more. If failed, fml8 exits abnormally as exit(EX_TEMPFAIL) for MTA to re-deliver it. See the Section called Incoming Queuing in the Chapter called fml8 Mail Delivery System for more details.

In this case, incoming message queue may have a incomplete message. fml8 tries to remove it in abnormal exit. Even if failed, the queue management system removes it later.

If Updating Of The Article Sequence Number Failed

In normal case, fml8 updates the article sequence number and re-reads it and compares it again. If the check fails, fml8 exit(EX_TEMPFAIL) for MTA to re-deliver it.

Caution

The article sequence number updated. After that, fml8 does not do exit(EX_TEMPFAIL) to deliver the message on memory as could as possible.

When Saving Of Article Failed

Caution

In this stage, the article sequence has been updated.

In this case, fml8 does not create a new article file but the original message is already on the disk. The header of the article differs from the original one but the body content is same. So fml8 tries to link(2) the original mail in the incoming queue to the article file to save the content. [1]

fml8 tries to deliver the message on memory.

If the delivery process exits abnormally, distribution of article ends incompletely since fml8 can not use outgoing queue due to file system error.

Delivery Process

fml8 saves the message into the outgoing queue, after succeeded, the delivery process runs.

When fml8 fails to write the outgoing queue, fml8 exits incompletely.

See the Section called fml Sends Back A Mail Message in the Chapter called fml8 Mail Delivery System for more details.

Notes

[1]

If it could be, it is useful to implement another command which fixes the article header later. It is not implemented.

[HOME] [NSRG] [インフラ] [fml4] [fml8] [北海道] [おすすめの本] Powered by NetBSD and [nuinui.net] .
Copyright (C) 1993-2017 Ken'ichi Fukamachi mail:< fukachan at fml.org >