From: Thomas Jarosch <thomas.jarosch@intra2net.com>
To: mlmmj@mlmmj.org
Subject: [mlmmj] Allowing empty enevelope senders
Date: Tue, 08 Jul 2014 08:59:40 +0000 [thread overview]
Message-ID: <3154844.GYFGS8R0Q3@storm> (raw)
Hi,
we have one mlmmj list that gets back email bounces
from a newsletter. Such bounce emails are usually sent
using an empty envelope sender address "<>".
Currently mlmmj discards all emails with an empty envelope sender
address and this is not configurable (see mlmmj-process.c, line ~704)
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
Should we make this configurable or disable the code altogether?
If we make it configurable: Should we invert the default value?
Best regards,
Thomas
next reply other threads:[~2014-07-08 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 8:59 Thomas Jarosch [this message]
2014-07-08 19:04 ` [mlmmj] Allowing empty enevelope senders A. Schulze
2014-07-10 7:54 ` Ben Schmidt
2014-07-10 13:50 ` Thomas Jarosch
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=3154844.GYFGS8R0Q3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).