Network Admin writes on 7 August 1997 at 02:41:29
On Wed, 6 Aug 1997, David W. Tamkin wrote:
It should be noted that "Precedence: (bulk|list|junk)" is part of the
expansion of procmail's ^FROM_DAEMON token [but not ^FROM_MAILER], so any
procmailrc recipe diverting mail matching ^FROM_DAEMON to a folder for mail
sent by programs will put mail with junk precedence there. Likewise a
* !^FROM_DAEMON condition on recipes for autoresponders will make it ignore
mail with junk precedence.
Ouch, that doesnt sound good. It seems odd to me to regard error messages
from mail daemons, which may (from my perspective as a sysadmin anyway) be
fairly critical, as junk. I would have tought that if the mailer-daemon
You missed David's careful explanation of the difference in semantics
a few messages ago. The "Precedence:" header is intended for use by
the MTA - the systems that move your email message from it's origin to
the final destination. A "Precedence: junk" header does NOT mean
"this is junk mail", rather it means "this message does not need to be
delivered as quickly as others".
An analogy or two from the real world: every week I get a FedEx
package from the US containing my personal mail, which is mostly
magazines. The "Precedence:" of this package is "overnight", but the
"Priority:" would be "low", as I don't need to read _Sports
Illustrated_ immediately. Conversely, I got a new stock certificate
in the mail a few weeks ago; the "Priority:" of this letter was "high"
although it was sent bulk-mail.
As for what header to use, you might also consider the following
# Thanks to Pegasus mail, we have this:
:0:
* ^X-Distribution:[ ]?(moderate|bulk|mass)
toread/spam
Dan
------------------- message is author's opinion only ------------------
J. Daniel Smith <DanS(_at_)bristol(_dot_)com>
http://www.bristol.com/~DanS
Bristol Technology B.V. +31 33 450 50 50, ...51 (FAX)
Amersfoort, The Netherlands {info,jobs}(_at_)bristol(_dot_)com