Good Morning,
The following scenario was originally reported as a possible bug in
MIMEDefang. However, further testing shows that it is an issue/error in
sendmail but I would appreciate feedback if anyone has seen anything similar
because this is driving me up a wall.
Here is the original scenario (based on some thoughts of what might be
causing the issue) and the steps we went through to try and resolve the
issue:
NOTE: Yes, we did make all the DB files and restart sendmail in between all
the tests.
Using MIMEDefang
FEATURE(always_add_domain)dnl
using virtusertable with a catchall for @defaultdomainadded.com
A user emails a domain that doesn't exist, the email is rewritten from:
[EMAIL PROTECTED] to [EMAIL PROTECTED]
The user does not get a bounce that the email did not arrive because the
catchall gets it instead (see header below).
Next Step:
Turning off always_add_domain did not fix the issue. Same output
received.
Third Step:
Turning off the catchall (I tried editing AND a blank virtusertable same
result on both) AND the always add gives a user the error: "The message
could not be sent because one of the recipients was rejected by the server.
The rejected e-mail address was '[EMAIL PROTECTED]'. Subject 'test',
Account: 'SUMMER', Server: 'mail.somewhere.com', Protocol: SMTP, Server
Response: '550 5.1.1 <[EMAIL PROTECTED]>... User unknown', Port: 2025,
Secure(SSL): No, Server Error: 550, Error Number: 0x800CCC79"
We should get a Host unknown error, not
Fourth Step:
Turning off MIMEDefang seems to point that this is a sendmail issue:
sendmail[18643]: i2DDb8lq018643: <[EMAIL PROTECTED]>... User unknown
So it looks to me like instead of a domain not resolvable error or what
not, we get a user unknown error
Fifth Step:
Upgraded to sendmail 8.12.11 with no apparent change in the behavior.
Sixth Step:
Another system setup similarly gave the proper DSN: Host unknown (Name
server: kjdsakjajd.com: host not found). Looked and looked for differences
and can't find one.
Seventh Step:
Change DNS resolution to same as system that worked proper without
success.
Eighth Step:
Changed to same sendmail.mc from machine that worked without success.
So essentially we have a standard sendmail installation from source that
doesn't seem to be handling unresolvable domains in the to: properly.
Anyone have any pointers?
Regards,
KAM
Header from Actual email showing the issue. Note the for and the to
differences. (Slightly modified to protect the server)
Return-Path: <[EMAIL PROTECTED]>
Received: from account2 (ip68-228-14-63.dc.dc.cox.net [68.228.14.63])
[ by mail.somewhere.com (8.12.10/8.12.10) with SMTP id i2DDOOpg018283
for <[EMAIL PROTECTED]>; Sat, 13 Mar 2004 08:24:24 -0500
Message-ID: <[EMAIL PROTECTED]>
From: "Kevin A. McGrail" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: test
Date: Sat, 13 Mar 2004 08:13:21 -0500
MIME-Version: 1.0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Scanned-By: MIMEDefang 2.38
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on
mail.somewhere.com
X-Spam-Status: No, hits=-4.9 required=6.5 tests=BAYES_00 autolearn=ham
version=2.63
X-Spam-Level:
_______________________________________________
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
