Professional Software Engineering wrote:
IMO, one shouldn't "fix" the date, since more than likely, you'll be
bringing it into your timezone (not that of the sender) -- the date
header should reflect the attributes of the sender, not the recipient.
This holds especially true if you ever FORWARD one of these messages.
Maybe, i don't know procmail that well.
I don't know if you understand that script corretly. Normaly it do not
change any headers. The script is tollerant when comparing the date and
respects the timezone the sender resists. When you manage your computer
correctly, the you shouldn't have a time that is more than a hour in the
future, not even that. Normally a email do not need 3 days to get routet
through the internet, even with server problems in the route. Both
thresholds are adjustable. Only if one of them is surmounted, the date
will be replaced by a new one. The old is renamed to Old-Date.
This prevents your Mailbox from beeing flooded by mails from slutty users.
You should also note that some external scripting languages can incurr a
_significant_ CPU and memory load. I don't use Python since I'm
familiar with Perl and C/C++ and haven't seen anything compelling in
Python, but you should definatley benchmark the processing time against
a large mailbox with and without calls to your Python script to see what
sort of overhead you're adding.
Python is very fast.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail