Randy Cassingham wrote:
> > It appears that Netcom Communications uses a dynamicly changing element
> > JohnSmith@ix.netcom.com shows up in extended headers in form of
> > JohnSmith@ix4.ix.netcom.com, then JohnSMithfirstname.lastname@example.org and so on.
> > This extended, variable element changes in every single email from such user.
> > [...]
> > Any recommendations on how to deal with this variable field?
> This isn't netcom's fault, it's the user's, who has probably not set up
> his netscape mailer properly. "Netcruiser" (ix.netcom.com) accounts,
> which should NOT be confused with Netcom shell (plain netcom.com)
> accounts, are ALWAYS in the form email@example.com; any extra server
> names can be -- and should be -- omitted to avoid bounces.
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
[220.127.116.11]) by server.postmodern.com (8.7.4/mcb-960422) with
SMTP id MAA06937; Fri, 26 Apr 1996 12:14:05 -0700 (PDT)
If this were not the case, that would imply that NetCruiser users
deliver their mail directly to the recipient MX via SMTP, which does
not sound likely, and would not work well in a non-fulltime, dial-up
So assuming that outgoing NetCruiser mail goes through a Netcom server,
Netcom CAN and SHOULD rewrite the "From:" line to firstname.lastname@example.org,
just like many/most sites do with the "masquerade as" variable in
Sendmail. Heck, I think Netcom even *uses* sendmail, in which case they
have no excuse.
Michael C. Berch
email@example.com / firstname.lastname@example.org