In article Pine.LNX.4.21.0201171335540.17733-100000@orbital.cuenet.com, Paul Thomas cueman@cuenet.com writes:
Has anyone come up with any heuristics that procmail can use to determine that a message to a mailing list from a poorly configured autoresponder (the message appears to come from an individual and does not include headers from daemons, proper Precendence: , etc) and prevent it from creating an infinite loop with the mailing list?
My experience has been that SmartList already has implemented most of those heuristics: the daemon-sender hints, the Precedence header, the X-Loop header, etc. If you've been unlucky enough to hit an autoresponder that slips through all of these, you'll probably have to write some new rules for it, and the rules may not apply to any other system. It's a rotten situation.