All,
I contacted Colorado CSC on this one. I spoke with Tammy in the sendmail
group and gave her the senario. After about 30 minutes on the phone, we
tracked down the sendmail.cf rule set that was doing this. Here it is:
===============================================================
########################################
# Utility: canonicalize local domain #
########################################
S9
# (next four lines are only generated if $N isn't LOCAL)
R$*<_at_$->$* $:$1<_at_$2.$N>$3 qualify
R$*<_at_$+.$=T>$* $_at_$1<_at_$2.$3>$4 trash pseudodom, lv aln
R$*<_at_$+.$=T.$P>$* $_at_$1<_at_$2.$3.$P>$4 qualified trash, lv aln
#R$*<_at_$+>$* $:$1<_at_$[$2$]>$3 canon'ize complex names
#Above Line Commented out by ACS--- 5/17/96
================================================================
This rule was indeed stripping the COMSOURCE.NET domain from the mail when
forwarding it. As you can see above, I commented out the last line in the
S9 ruleset. After restarting sendmail and testing... everything worked
great! Gonna have to send Tammy at DEC a BIG fruit basket on this one!
This appears to be a bug in DEC's sendmail because she was able to
replicate the problem on her system. So everyone... here's the fix!
Hope this helps everyone.
-Andy Saylor, Systems Administration
On Fri, 17 May 1996, Andres Henckens wrote:
acs> > Ok,
acs> > Heres the situation:
acs> >
acs> > We have a Dec 2100 running dUnix 3.2b and DEC's sendmail 5.65. When we
acs> > send a piece of email from another machine (for example a Linux box or an
acs> > SCO box we have here) to the alpha it works fine.
acs> >
acs> > However, if the user has a .forward file in their home directory,
acs> > wierdness occures. The email gets forwarded correctly but when arriving at
acs> > the off-site machine, the return address reads:
acs> >
acs> > xxxx_at_gold (gold being the name of the linux box in this case).
acs> >
acs> > There is no domain name attached to the line and thus when "Reply"ing to
acs> > the email, it sends to xxx_at_#gold which is an invalid address and bounces.
acs> > This does not occure if the mail was originally sent from a remote machine
acs> > (not in the comsource.net domain). Here's a copy of the mail headers:
acs> >
acs> > ****************************
acs> > Return-Path: <root_at_GOLD>
acs> > Received: from PSUVM (NJE origin SMTP_at_PSUVM) by PSUVM.PSU.EDU (LMail
acs> > V1.2a/1.8a) with BSMTP id 0941; Fri 17 May 1996 09:34:17 -0400
acs> > Received: from alpha.comsource.net by PSUVM.PSU.EDU (IBM VM SMTP V2R2)
acs> > with TCP;
acs> >
acs> > Fri 17 May 96 09:34:15 EDT
acs> > Received: from gold by alpha.comsource.net; (5.65/1.1.8.2/20Mar96-1058AM)
acs> > id AA14391; Fri 17 May 1996 08:35:03 -0500
acs> > Received: (from root_at_localhost) by gold.comsource.net (8.7.3/8.6.9) id
acs> > IAA09380
acs> > for test_at_comsource.net; Fri 17 May 1996 08:34:15 -0500
acs> > Date: Fri 17 May 1996 08:34:15 -0500
acs> > From: root <root_at_gold>
acs> > Message-Id: <199605171334.IAA09380_at_gold.comsource.net>
acs> > To: test_at_comsource.net
acs> >
acs> > Test from Gold
acs> > ****************************
Received on Fri May 17 1996 - 17:43:01 NZST