All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Morten K. Poulsen" <morten@afdelingp.dk>
To: mlmmj@mlmmj.org
Subject: Re: Treatment of Return-Path: headers (Re: mlmmj-recieve silently discarding messages
Date: Sun, 22 Jan 2006 00:13:48 +0000	[thread overview]
Message-ID: <20060122001348.GI58097@mmj.dk> (raw)
In-Reply-To: <Pine.LNX.4.61.0601202210510.6540@e-smith.charlieb.ott.istop.com>

* Charlie Brady <charlieb@budge.apana.org.au> [Jan 21. 2006 20:15]:
> > > One of the stated goals of mlmmj is mail server independence, so
> > > it should be very careful about strict RFC compliance.
> >
> > Sure, but it's possible for every MTA to be configured to add it, ..
> 
> You can't say that, because you can't possibly know about all MTAs which 
> currently exist or which might exist in the future. But you are right, it 
> will usually be possible to find a way to provide it.

OK. The interface between the MTA and the MDA is - as far as I know -
not defined in any RFC. Please correct me, if I am wrong. Therefore we
CANNOT know how EVERY MTA will be passing us the envelope information.
It can be some environment variables, added headers, written to
inhireted open file descriptors, as X Window Events, whatever...

If you know a way to make sure that we - inspite of having NO RFC - can
make sure that we get that info from any current or future MTA... Please
send us the patch ;-)

Morten

-- 
Morten K. Poulsen <morten@afdelingp.dk>

      parent reply	other threads:[~2006-01-22  0:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21  3:23 Treatment of Return-Path: headers (Re: mlmmj-recieve silently Charlie Brady
2006-01-21  7:20 ` Michael Fleming
2006-01-21 19:03 ` Charlie Brady
2006-01-21 19:05 ` Treatment of Return-Path: headers (Re: mlmmj-recieve silently discarding messages Mads Martin Joergensen
2006-01-21 19:15 ` Treatment of Return-Path: headers (Re: mlmmj-recieve silently Charlie Brady
2006-01-21 19:28 ` Charlie Brady
2006-01-22  0:13 ` Morten K. Poulsen [this message]

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=20060122001348.GI58097@mmj.dk \
    --to=morten@afdelingp.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 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.