public inbox for mlmmj@mlmmj.org
 help / color / mirror / Atom feed
From: Yuri D'Elia <wavexx@thregr.org>
To: mlmmj@mlmmj.org
Subject: [mlmmj] mlmmj, envelope address and BATV
Date: Fri, 01 Jun 2012 13:08:50 +0000	[thread overview]
Message-ID: <4FC8BEE2.1080707@thregr.org> (raw)

Hi everyone. I've posted some time ago this bug report:

   http://mlmmj.org/bugs/bug.php?id3

along with some patches, fixing mlmmj behavior regarding the 
envelope/mail from address. I've been using these patches ever since to 
fix gmane (which I use for all my mailing lists).

Got the first complaint today from a user coming from a BATV address:

   http://en.wikipedia.org/wiki/Bounce_Address_Tag_Validation

this is news to me. As was discussed before:

   http://article.gmane.org/gmane.mail.mlmmj.general/1277

this clearly requires re-reading a whole lot of stuff now. It has been 
several years since I stopped lurking on nanae, but so far SPF/DKIM have 
been completely transparent. Doesn't seem to be the same for BATV.

ezmlm seem to have the same issue, since it processes addresses 
according to the envelope from, and not from the "From:" header. I've 
been trying to read what exactly mailman does, as mailman also uses 
(used to) to process addresses based on the envelope address, but I 
stopped because of lack of time.

The current version of mlmmj will "work" for these addresses as it will 
trust the "From:" header, but probably breaks a heap of other stuff such 
as bounce/loop detection. Apparently, trusting the From: address 
/should/ be safe whenever DKIM is being used, but this poses some 
additional problems as to where to process DKIM validation entirely (at 
the MTA level?).

I'm at loss here about what to do here (BATV is still a draft afterall), 
but I figured this would be important to discuss.


                 reply	other threads:[~2012-06-01 13:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FC8BEE2.1080707@thregr.org \
    --to=wavexx@thregr.org \
    --cc=mlmmj@mlmmj.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox