[170829] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: procmail, was autoresponding to Yahoo DMARC breakage

daemon@ATHENA.MIT.EDU (Jack Bates)
Thu Apr 10 04:39:40 2014

Date: Wed, 09 Apr 2014 21:35:27 -0500
From: Jack Bates <jbates@paradoxnetworks.net>
To: George Michaelson <ggm@algebras.org>, "John R. Levine" <johnl@iecc.com>
In-Reply-To: <CAKr6gn1o_TxZKrJ_pJEBSo8YXxRBm6ZF_Pi9fF21bvToiCT8=w@mail.gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>, Dave Crocker <dcrocker@bbiw.net>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On 4/9/2014 9:21 PM, George Michaelson wrote:
> Aside from a horrid config notation. the main problem for me has always
> been getting sysadmins to include the changes which expose envelope-sender
> and envelope-recipient to procmail. Thats not procmail, its the way
> procmail is typically called. Without it, some stuff simply cannot be done
> because you don't know the values passed by protocol, only the values
> exposed in header.
>
> (this may have changed. I don't use it any more)
>
>
>
It can still be a problem, although I believe LMTP fixes this problem 
along with the others it was designed to fix.


Jack


home help back first fref pref prev next nref lref last post