John Buckman writes:
> > Hmmm. I don't know if I buy the idea that Netcom is not responsible. All
> > the mail I've seen from NetCruiser users has, so far as I can tell,
> > passed through a Netcom server on its way from the user's PC to the rest
> > of the Net.
> > A typical "Received:" line might look like
> > Received: from dfw-ix2.ix.netcom.com (dfw-ix2.ix.netcom.com
> > [184.108.40.206]) by server.postmodern.com (8.7.4/mcb-960422) with
> > SMTP id MAA06937; Fri, 26 Apr 1996 12:14:05 -0700 (PDT)
> James told me that this person is using Pegasus Mail, which by
> default uses the person's POP3 info to build the From: address.
> Thus, if the POP3 server they use is "ix4.ix.netcom.com" and their
> username is "jane", Pegasus gives them the email address
> My guess is that Netcom uses some sort of POP3 use-balancing scheme,
> so the person is using any one of a number POP3 servers each time
> they use Pegasus, and each time a different default From: is being
Right. But it shouldn't matter what sort of random cruft Pegasus (or
any other client mailer) sticks in the From: line; when the Netcom
mail relay processes it, it should rewrite the From: line to a
canonical form. That's trivial, and most ISPs seem to do that.
> The solution for them was to use the Pegasus "advanced configuration
> options" and tell Pegasus what their "From" address is (and to use it
> in the SMTP envelope), so that Pegasus doesn't auto-generate the
> From: address.
It would seem that their support burden would be greatly lessened if
they just fixed their mail relays to take care of this, instead of
trying to support every !~@#$% PC mailer out there. But this is
Netcom we are talking about here, who is not exactly known for their
Michael C. Berch
firstname.lastname@example.org / email@example.com