Re: Rationale for non-standard VERP in MJ2?

On Sat, 25 Aug 2007 10:25:04 -0400 (EDT), John L wrote
> In any event, as we've been telling you over and over, MJ2 sends 
> perfectly normal, standard-conformant mail, and it does what it does 
> for good reasons.  If you don't like the way that your inbound MTA 
> handles it, you can easily fix your MTA.

I can't find any RFC about VERP, meaning it never went through proper IETF
process. As such, it's nothing else than a hack - or a way how to (ab)use
envelope sender for purposes it was never meant for. This is why other
listservers typically use VERP with extreme care - e.g. only once per month for
subscription reminders, but not for regular email on the list.

Yes, I can "fix" my MTA, but this is clearly not the correct way to solve this
problem. All other sites which use greylisting will experience the same problem 
and will have to make manual adjustments just because MJ2. In other words, you
made your life easier and instead of fixing the problem at its root you're now
requesting all greylisting sites to make special arrangements which are not
needed for any other listserver software. This is clearly not is sync with "Be
liberal in what you accept, and conservative in what you send".
 
Last but not least, the message number is definitely not needed in envelope
sender.  The bounce processor could easily use other methods to achieve the same
goal instead of passing unnecessary burden on third parties.


    With kind regards,

           M.