MLMMJ Mailing List Manager
 help / color / mirror / Atom feed
From: Mads Martin Joergensen <mmj@mmj.dk>
To: mlmmj@mlmmj.org
Subject: Re: Treatment of Delivered-To headers (Re: mlmmj-recieve silently discarding messagesail?)
Date: Sat, 21 Jan 2006 11:56:24 +0000	[thread overview]
Message-ID: <20060121115624.GF58097@mmj.dk> (raw)
In-Reply-To: <Pine.LNX.4.61.0601202202460.6540@e-smith.charlieb.ott.istop.com>

* Morten K. Poulsen <morten@afdelingp.dk> [Jan 21. 2006 12:55]:
> Quoting Mads Martin Joergensen <mmj@mmj.dk>:
> >>Unless you tell me I'm way off track, I'll try to get a patch together. It
> >>should be safe to assume that $RECIPIENT won't be set under other MTAs. If
> >>you think it's not, then we could use a command line flag to only activate
> >>the environment check under qmail.
> >
> >I would love a patch doing this, with a a commandline option to
> >configure it. No need to read environment variables anywhere else than
> >qmail AFAIK.
> 
> Do we need a commandline switch? If qmail puts the values (which other 
> MTAs put in headers) in environment variables, the code could be 
> changed to something like the following pseudo code:
> 
> envelope_to = getenv("RECIPIENT");
> 
> if (!envelope_to)
>    envelope_to = getheader("Delivered-To");
> 
> if (!envelope_to)
>    envelope_to = getheader("To");
> 
> if (!envelope_to)
>    abort();
> 
> ... and likewise for sender.
> 
> Having an extra commandline switch just makes it a tiny bit more 
> difficult to set up.

Agreed it's a bit more difficult. I'm just pr. default cautious about
reading environment variables :-)

-- 
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
 and totally illogical, with just a little bit more effort?"
                                 -- A. P. J.

  parent reply	other threads:[~2006-01-21 11:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21  3:10 Treatment of Delivered-To headers (Re: mlmmj-recieve silently Charlie Brady
2006-01-21  8:44 ` Treatment of Delivered-To headers (Re: mlmmj-recieve silently discarding messagesail?) Mads Martin Joergensen
2006-01-21 11:55 ` Treatment of Delivered-To headers (Re: mlmmj-recieve silently Morten K. Poulsen
2006-01-21 11:56 ` Mads Martin Joergensen [this message]
2006-01-21 12:05 ` Morten K. Poulsen
2006-01-21 15:33 ` Treatment of Delivered-To headers (Re: mlmmj-recieve silently discarding messagesail?) Mads Martin Joergensen
2006-01-21 19:20 ` Treatment of Delivered-To headers (Re: mlmmj-recieve silently Charlie Brady
2006-01-21 19:23 ` Charlie Brady

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=20060121115624.GF58097@mmj.dk \
    --to=mmj@mmj.dk \
    --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