Volker concurred, and suggested:
- date parsing operations
Correction: date supplying functions/variables
- mail address parsing support. Reliably and correctly parse the
addresses in TO: FROM: and any other headers. Once the address
has been broken out, support splitting it into name and address
and host name part.
Splitting into email, name, comment parts. ALso splitting email into
user, domain parts?
- Add builtin features which make it easier to perform frequently needed
operations, such as vacation processing, auto-replies, mailing list
determination and sorting. In particular, the builtin operations would
make sure an X-loop is added, and so on.
The expressions used for this should come from a variable, because they
may change over time. For example, the built_in expression for
FROM_DAEMON is essentially no good any more because it matches all
info@, but addresses of the form info(_at_)someonesbusiness(_dot_)com are very
common these days. The info@ part needs to be removed from the
FROM_DAEMON expression.
Volker
--
Volker Kuhlmann is possibly list0570 with the domain in header
http://volker.dnsalias.net/ Please do not CC list postings to me.
____________________________________________________________
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