Chapter 8: Command-Line Log Analysis Tools Up Main page

Suggested Reading

Footnotes

[A]DJB’s website can be found at http://cr.yp.to/
[B]Qmail’s hompage is located at http://cr.yp.to/qmail.html
[C]Courier IMAP’s website can be found at http://www.courier-mta.org/imap/
[D]SpamAssassin’s website can be found at http://spamassassin.apache.org/
[E]ClamAV’s website can be found at http://www.clamav.net
[F]The reason to limit this is mainly if disk space or processor capacity is at a premium.
[G]SMTP-Level Scanning will scan all e-mail using the SpamAssassin content filter as the e-mail enters the server. The SMTP connection will be dropped only if the Spam Score is higher than the SMTP Spam Score option below. Otherwise, the e-mail will still be delivered to the recipient.
[H]Lower values here are stricter. If you’re worried about blocking legitimate mail, try 7. If even 5 lets in too much spam, drop it to 4.
[I]The IMAP Leaning Limit sets a cap on how many e-mails users can submit to the Bayes engine in SpamAssassin for training as junk (spam) or not-junk (ham).
[J]Important note: if SMTP-Level Virus Scanning is enabled and the virus scanner stops running for some reason, e-mail will not be delivered.
[K]This value changes the tcpserver setting of the ucspi-tcp suite which is used to launch the program. http://cr.yp.to/ucspi-tcp/tcpserver.html
[L]Messages will only stay in queue if the message is deferred - i.e. qmail is able to determine the IP address of the remote MX server and either the connection timesout, or qmail is able to connect but the remote server rejects the message saying try again later. This is typical when a mail server gets black-listed by free webmail providers like GMail or Hotmail. If the remote server responds that the user doesn’t exist, qmail can’t determine the mx server of the host portion of the address, or the delivery is local and the user doesn’t exist, qmail will immediately bounce the message back since those are considered permanent failures.
[M]It’s not really a setting - it’s a file on disk that qmail reads from in /var/qmail/control
[N]This value changes the softlimit setting of the daemontools suite which is used to launch the program. http://cr.yp.to/daemontools/softlimit.html
[O]This value changes the tcpserver setting of the ucspi-tcp suite which is used to launch the program.http://cr.yp.to/ucspi-tcp/tcpserver.html
[P]This value changes the softlimit setting of the daemontools suite which is used to launch the program.http://cr.yp.to/daemontools/softlimit.html
[Q]This value changes the tcpserver setting of the ucspi-tcp suite which is used to launch the program.http://cr.yp.to/ucspi-tcp/tcpserver.html
[R]This value changes the softlimit setting of the daemontools suite which is used to launch the program. http://cr.yp.to/daemontools/softlimit.html
[S]This value changes the tcpserver setting of the ucspi-tcp suite which is used to launch the program.http://cr.yp.to/ucspi-tcp/tcpserver.html
[T]This value changes the softlimit setting of the daemontools suite which is used to launch the program. http://cr.yp.to/daemontools/softlimit.html
[U]This value changes the tcpserver setting of the ucspi-tcp suite which is used to launch the program.http://cr.yp.to/ucspi-tcp/tcpserver.html
[V]Part of the reason that manipulating the queue manually with cp/mv/rm commands is a bad idea is because the queue files are named based on the filesystem inode number - which obviously would change if you started moving stuff around. Not to mention qmail expects certain files to be in certain directories of the queue in order to know what state a message is in. An incorrect file state will lead to strange behavior - possibly the queue corrupting itself further.

(C) 2017 by InterWorx LLC