Professional Software Engineering wrote:
Well, as written that second one has a syntax problem - it's missing the
opening bracket before the 2-9
I noticed that too; just didn't want to rub it in ;-).
5 days is a common delivery failure. OTOH, mail being delivered _to_ me
never experiences delays that long unless someone is relaying mail
through their own internal network and that is fscked up. That'd be
their problem anwyay.
As I recall now I think 5 days is a common default. My outbound MTA
is cranked down to 3 and I think I will knock that down to 1 or 2
soon. Sort of off topic for the procmail list but these days people
expect email to get through almost instantly and it is probably
better for an MTA to bounce it sooner rather than later. Unless,
I suppose, you have it configured to do delay notifications. Of
course even in that case the info is often moot after a day anyhow
so it might as well never be delivered.
If if there are mail interuptions I would not want to tag a pile of
legit mail as spam merely because it was a few days late.
Which is why it is fortunate that smart people _file_ their spam instead
of dev/null'ing it. That means that they can simply revise a rule and
reprocess their spam mailbox with a formail split operation to reclaim
messages which may have errantly been filed. if you had a downtime, you
might opt to tweak your rules anyway.
I considered that last point already and would certainly mod the
rule temporarily if my mail server had significant down time; but
I was more thinking of problems with a remote site. Of course I
think I have talked my self down to a day now anyhow.
--
Daryle A. Tilroe
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail