On Sat, Oct 28, 2000 at 02:29:11AM +0100, Ricardo Cerqueira wrote:
> On Fri, Oct 27, 2000 at 03:39:43PM -0700, [EMAIL PROTECTED] wrote:
> > Hmm. Maybe I'm confused. How do people think the envelope sender
> > value is determined in the first instant? Eg, how does Eudora go from
> > a mail in a window to "Mail From: " in SMTP? Or how does qmail-inject
> > for that matter?
> >
>
> qmail-inject uses environment variables for From (not From:).
What are you talking about? What does "From (not From:)" mean?
If you deduced this from qmail/djb-docs, all of these references
(unless specifically talking about final delivery) mean the "From:"
header. You might care to read cr.yp.to/immhf.htm for a more general
discussion on mail headers.
The only "From" that qmail-inject deals with is "From:". If you think
otherwise show us some output from qmail-inject -n that has this
mysterious "From (not From:)" that you refer to.
If you are referring to the "From " line, this is not a mail header,
that any part of the mail injection deals with. Instead, "From " is a
very poorly defined delimiter in V7 mailboxes that is generated at
final delivery which has nothing to do with injection.
If you still don't believe me and you don't want to bother explain
by demonstration, have a look at this code from qmail-inject.c:
void defaultfrommake()
{
...
df.t[df.len].s = "From";
df.t[df.len].slen = 4;
++df.len;
df.t[df.len].type = TOKEN822_COLON;
It's the only piece of code that has "From" and it looks like "From:" to me.
> For those who do not use qmail-inject directly (Like those using remote
> SMTP with Eudora, to use your example), the "From" is generated by the MUA.
> So yes, those cases are "hopeless". "From:" will almost certainly be the base
> for "From"
I think you're confused. There is no "From" that is separate from "From:".
If you think otherwise, inject a mail into qmail via SMTP using a mail client
like Eudora and show us the queue file with this "From" header you refer to.
(Use a target address that cannot be delivered so you can catch the queue
entry).
> > The answer is that it's mostly derived from a parse of the various
> > headers in the original mail when it's injected into the MTA. In
> > many cases the most likely header that will be used to derive the
> > envelope sender will be the From: header. So to suggest that the
> > unparsed From: header is a better place to look for the sender
> > seems a bit silly to me because in many cases the envelope sender is
> > simply a parsed version of the From: header.
>
> Not really. You can have very odd "From:" lines (with 8bit chars, spaces),
> but From is (or should always be) a plain old user@domain string. It's
> easier to parse, and probably less prone to error.
Are you sure you're not confusing this discussion with the "From " line
that is generated on delivery into a mailbox? Which by the way *is*
used to stash the envelope sender address, which *is* original derived
from fields like "From: ".
Regards.
