Michelle Konzack:
Message-ID: 20050428140913(_dot_)12345(_at_)freenet(_dot_)de
So how can I correct this problem ?
:0
* ! ^Message-Id:
{
# add a Message-Id?
}
:0E fhw
* ! ^Message-Id:.*<.*>
* ^Message-Id:.*\/[^ ]+
| formail -i "Message-Id: \<$MATCH\>"
If you never receive a message without a Message-Id, which
is normal because your receiving mail server will add it,
than this will be sufficient:
:0 fhw # beware: allows an empty <>
* ! ^Message-Id:.*<.*>
* ^Message-Id:.*\/[^ ]+
| formail -i "Message-Id: \<$MATCH\>"
(untested, so don't know whether the < and > really need to be escaped)
A Message-Id is not allowed to contain a comment, but sometimes
I see a Message-Id that does contain one, like:
Message-Id: <date(_dot_)random(_at_)host(_dot_)domain(_dot_)tld> (added by
whatever)
But why repair it? I report such messages as RFC-ignorant.
--
Grtz, Ruud
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail