Prahlad Vaidyanathan on 31/01/2002 at 04:08 opined thusly: > Hmm .. I thought fetchmail injected things into your MTA. So, it should > have the same route as if you called it from the command-line. ie : > > fetchmail -> MTA -> procmail -> folder(s) > You are correct. That is the default behavior of fetchmail but fetchmail can be configured to bypass the MTA and deliver straight to your MDA, procmail for most of us.
From the fetchmail man page: -m <command>, --mda <command> (Keyword: mda) You can force mail to be passed to an MDA directly (rather than forwarded to port 25) with the --mda or -m option. To avoid losing mail, use this option only with MDAs like procmail or sendmail that return a nonzero status on disk-full and other resource exhaustion errors; the nonzero status tells fetchmail that delivery failed and prevents the message from being deleted off the server. If fetchmail is running as root, it sets its userid to that of the target user while delivering through an MDA. Some possible MDAs are "sendmail -oem -f %F %T", "/usr/bin/deliver" and /usr/bin/procmail -d %T" (but the latter is usually redundant as it's what SMTP listeners usually forward to). Local delivery addresses will be inserted into the MDA command where you place an %F. Do not use an MDA invocation like "sendmail -oem -t" that dispatches on the contents of To/Cc/Bcc, it will create mail loops and bring the just wrath of many postmasters down upon your head. -- Ken Wahl [EMAIL PROTECTED] http://www.kenwahl.org/mutt/ PGP/GPG Key C225AA5A: http://www.kenwahl.org/pubkey.gpg Mutt: All mail clients suck, this one just sucks less.. Weaponized Linux Kernel 2.4.9-12 Uptime: 1 day, 22:52
msg24015/pgp00000.pgp
Description: PGP signature
