Kavi Mailing List Manager Help
The Mail Delivery Logs tool is used to retrieve delivery status information for email so you can see whether delivery has been successful or not. By default, the Search Time box is set to 'Today', so today's mail logs are already displayed. You can narrow the results by searching for email messages based on a search string (e.g., an email address, email domain, alias, etc.). If you need to search back in time, use the Search Time box to set the number of days back that you want the search to go (e.g., 'Today', 'Yesterday', 'Last 2 Days', etc.). The Min. Recipients and Size fields are especially useful when you want to search for high-volume messages that take a long time to clear the mail queue, delaying mail delivery processes.
The information presented here is derived from the raw qmail logs, then refined for ease of use before being displayed. For example, multiple entries from the raw logs are combined into a single entry in the Mail Delivery Logs results table if they pertain to the same email message.
The results display date and time information about each host-to-host transfer in the email delivery process, such as when the transfer process began and when it terminated. Other information includes the originating sender and receiver(s) email addresses, the size of the message and whether delivery completed successfully.
Mail Delivery Logs searches are compute intensive. For best results, always set the Search Time field to the minimum number of days that will give you the information you need.
Search and view mail logs to determine if a message has been successfully delivered.
Search for high-volume messages.
Set search criteria and click the Search button to retrieve the mail logs that you wish to view. To change the number of results displayed per page, set the desired number in the pull-down list and click the Change button.
Search Criteria Options:
Enter the text string for which you'd like to search in this text box. This tool does partial matches, so you may search by any string, including all or part of an email address (e.g., just the domain), a username, alias (e.g., 'webmaster') or what have you. For instance, if you entered the partial email domain 'example.', the search would return any user whose email address contains that text string, including 'firstname.lastname@example.org', 'email@example.com' and 'firstname.lastname@example.org'.
- Search Time
The Search Time box is set to 'Today' by default, so today's logs are displayed. If you need to search further back, use the pull-down list to set the range of dates you'd like to search (e.g., 'Yesterday', 'Last 2 Days', etc.). For optimal query speed, remember to set this to the minimum number of days.
A lot of system resources are required to process a week's worth of logs, so if you do select the 'Last 7 Days' option, be prepared to wait a minute or more for the tool to read the raw logs, process the logs, then display the results.
- Min. Recipients
Enter a number in this text box to search for messages delivered to at least this number of recipients. The number of recipients is one of the factors in determinining message volume. The other is message size.
Select a message size in kilobytes (KB) in the pull-down list to search for messages over this size.
If you aren't familiar with mail logs, here is an example and explanation of how to interpret this information.
If this were a message posted to a mailing list, the entry for the transfer of the email from the originator to the mailing list's mailbox would look something like this:
2005-06-06 07:38:24 <email@example.com> ... sent 47957 bytes from qp 6629
2005-06-06 07:38:24 + firstname.lastname@example.org ... success: ezmlm-send: info: qp 6636
2005-06-06 07:38:24 end (1+0+0)
The first line displays the date and time that the email originated, the originator's email address, the size of the message in bytes and a qmail ID. The time is determined by the originating host's time clock, on a twenty-four hour clock (i.e., ANSI or military time), normalized to Universal Time.
The second line displays the date and time that the receiving host began processing the transfer, the receiving host's email address and a message indicating whether the transfer was completed successfully, was deferred (i.e., unable to be completed at this time, in which case the system will try to complete the transfer again later) or a failure. In this example, this line contains the name of the 'ezmlm-send' process and another qmail ID, which means the message has not completed it's journey to its final destination and is being forwarded via ezmlm-send. Since this is a mailing list, this entry shows the leg of the journey from the originator to the mailing list mailbox. As you may have guessed, the second qmail ID represents the next leg of the journey, the transfer from the mailing list to the individual subscribers, as shown in the next sample entry.
The last line displays the date and time that the transfer was completed, the word 'end' to indicate the end of the transfer process, and a set of numbers in parentheses, each of which represents a count of the number of messages that fall into a certain completion status. The first number in the series represents the number of successfully completed transfers, the second is the number of transfers deferred, and the third is the number of failures. In this case, one transfer was completed successfully, and there were no deferrals or failures.
2005-06-06 07:38:24 <email@example.com 10> ... resent 48021 bytes from qp 6636
2005-06-06 07:38:27 + firstname.lastname@example.org ... success: XXX.XXX.XXX.XXX accepted message.
2005-06-06 07:38:26 + email@example.com ... success: XXX.XXX.XXX.XXX accepted message.
2005-06-06 07:38:29 + firstname.lastname@example.org ... success: XXX.XXX.XXX.XXX accepted message.
2005-06-06 07:38:28 + email@example.com ... success: XXX.XXX.XXX.XXX accepted message.
2005-06-06 07:38:39 + firstname.lastname@example.org ... success: XXX.XXX.XXX.XXX accepted message.
2005-06-06 07:38:28 + email@example.com ... deferral: Remote host said: 451 HEUR: Error scanning message
2005-06-06 07:45:07 + firstname.lastname@example.org ... success: XXX.XXX.XXX.XXX accepted message.
2005-06-06 07:38:25 + email@example.com ... success: XXX.XXX.XXX.XXX accepted message.
2005-06-06 07:45:07 end (7+1+0)
This entry displays information about the transfer of a message that has been posted to a mailing list from the list mailbox to the subscribers mailboxes. This is a small, private list with only seven subscribers.
As in the previous entry, the first line displays the date and time that the email originated, the originator's email address (which in this case is the list name), the size of the message in bytes and a qmail ID. The difference is that this time the status information says that the message was 'resent', indicating it was forwarded by the mailing list. The status information also indicates the message is 'from qp 6636', which is, of course, the ID assigned to this stage of the transfer process during the previous stage of the process. You can use the qmail IDs to follow email through multiple discrete transfer processes until it reaches its final destination.
Each of the next eight lines represents an attempt to transfer the email from the list to a subscriber. The reason there are eight lines instead of seven is that one of the transfer attempts was temporarily deferred, although it was subsequently successful. Each line displays the date and time that the receiving host began processing the transfer, the receiver's email address and a message indicating whether the transfer was completed successfully, was deferred (i.e., unable to be completed at this time so the system will retry the transfer later) or a failure. This information would include the IP addresses of each resolvable email address, represented here by a series of X's.
As before, the last line displays the date and time that the transfer was completed, the word 'end' to indicate the end of the transfer process, and a set of numbers representing the total count of successful transfers, deferred transfers and failed transfers. The string of values in parentheses '(7+1+0)' indicates seven transfers were completed successfully, there was one deferral and no failures. If this final line is missing from a log entry, a deferred transfer was still pending at the time the log was generated.