All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Jarosch <thomas.jarosch@intra2net.com>
To: mlmmj@mlmmj.org
Subject: Re: Re: [mlmmj] Allowing empty enevelope senders
Date: Thu, 10 Jul 2014 13:50:34 +0000	[thread overview]
Message-ID: <2861823.GP7UN3AmiU@storm> (raw)
In-Reply-To: <3154844.GYFGS8R0Q3@storm>

Hi Ben,

On Thursday, 10. July 2014 17:54:01 Ben Schmidt wrote:
> On 8/07/14 6:59 PM, Thomas Jarosch wrote:
> > I've found a good description why an empty envelope is a valid thing
> > according to RFC 821, page 15:
> > http://marc.merlins.org/netrants/nullenvelope.txt
> 
> That link correctly identifies empty envelope senders as used for bounce
> messages.
> 
> Furthermore, as you've identified, the mails are being discarded by
> Mlmmj, not the mail server. The mail server accepts them, meeting the
> requirements of the RFC and the document above. Mlmmj discards them,
> because they should not be delivered to the mailing list.
> 
> If they are getting to that point in Mlmmj, it probably means VERP is
> not working/misconfigured, because bounce messages should come back to
> listname+bounces and get handled by mlmmj-bounce so bouncing users are
> automatically unsubscribed (which helps prevent your mail server getting
> blacklisted, among other things).

the problem here is a bit more complex: The mlmmj managed mailinglist
gets the replies from a separate newsletter that is not managed by mlmmj.
So the return path of that newsletter is set to an address
that is managed by mlmmj :)

Would you be ok with if I develop a patch to make
the "discard of empty envelope address" configurable?
Default is to keep the current behavior.

Thomas



  parent reply	other threads:[~2014-07-10 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08  8:59 [mlmmj] Allowing empty enevelope senders Thomas Jarosch
2014-07-08 19:04 ` A. Schulze
2014-07-10  7:54 ` Ben Schmidt
2014-07-10 13:50 ` Thomas Jarosch [this message]
2014-07-10 20:55 ` Ben Schmidt
2014-07-11  7:40 ` Thomas Jarosch
2014-07-11 22:37 ` Ben Schmidt

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=2861823.GP7UN3AmiU@storm \
    --to=thomas.jarosch@intra2net.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.