[Exim] Re: Exim rejecting email routed from ISP

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Derrick 'dman' Hudson
Datum:  
To: exim-users
Betreff: [Exim] Re: Exim rejecting email routed from ISP
--
On Sat, Jul 20, 2002 at 09:58:53AM -0700, Cam Ellison wrote:
| * Dr Andrew C Aitchison (A.C.Aitchison@???) wrote:
| > On Sat, 20 Jul 2002, Cam Ellison wrote:
| > > * Dr Andrew C Aitchison (A.C.Aitchison@???) wrote:
| > > > On Fri, 19 Jul 2002, Cam Ellison wrote:
| > > > > Unable to deliver to destination domain
| > > > >
| > > > > Mail server at localhost [127.0.0.1] has the same MailSite serial
| > > > > number (32073) as this machine.


| > Sorry, I wasn't very clear. The error message makes me think the
| > problem is related to MailSite not exim.


It would seem so, except that there's no reason that MailSite should
see the address "roo@localhost" (and if it was really MailSite's
problem then fetchmail wouldn't play any part and Cam wouldn't have
the bounce message).

Rereading the error message a few times after having realized the
cause of the problem (and written the rest of this message), I now see
where the *other* problem lies. MailSite apparently does some sort of
proprietary callback on the domain to try and prevent pirating. It
sees a (presumably) sender address of @localhost so it (stupidly) does
a callback to localhost and finds out that (surprise surprise) it has
the same serial number as itself. Thus instead of returning "550 No
such user <root@localhost>" it says "You pirated me". What a
perfectly crystal clear error message :-).

| This is an example of an entry from the mainlog before the problem
| started (lines are cut so there's no overflow):

[snip]

BTW you're missing 2 lines there. When using SA like that, each
message will have 2 different exim ids since exim sees each message
twice.

| Here is a post-"change" example:

|
| 2002-07-18 18:02:54 17VMAY-0001iL-00 <=
| bounce-debian-user=camellison=dccnet.com@??? H=localhost
| [127.0.0.1] P=esmtp S=4609 id=AQJ2DB.A.v4F.QK2N9@murphy
| 2002-07-18 18:02:55 17VMAY-0001iL-00 => root@localhost


Why is exim trying to deliver to "root@localhost"? What user do you
run fetchmail as? Do you have a "is <foo> here" option where "<foo>"
is your username on your system? I suspect that fetchmail is creating
that recipient, but it isn't what you really want.

| R=smarthost T=remote_smtp H=mailhost.dccnet.com [207.230.239.78]

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

For some reason, you are trying to deliver root's mail via your ISP's
server, and it doesn't know how to accept mail for "root@localhost".

(mail shouldn't go to root anyways, you should have an alias in
/etc/aliases that redirects it to your user account)

| It looks as though the message is not getting as far as the
| directors.


It isn't. Directors are only used for "local domains", and you don't
have 'localhost' as a local domain.

| "smarthost" is set in exim.conf as mailhost.dccnet.com.


That would be set on a router. (at least, I certainly hope you don't
have a "smarthost" director!)

| Here's my exim.conf (or the bits that are set [and a couple that are
| not, but seem important]):


You could add "localhost" to the local_domains list setting instead of
fixing the program(s) that generate @localhost addresses.

| qualify_domain = ellisonet.ca


If fetchmail wasn't putting @localhost on the address then exim would
have made it @ellisonet.ca and you wouldn't see this problem.

-D

--
The remote desktop feature of Windows XP is really nice (and *novel*!).
As a Microsoft consultant can *remotely* disable the personal firewall
and control the system.  We'll ignore the fact that this tampering with
the firewall is not logged, and more importantly, that the firewall
isn't restored when the clowns from Redmond are done with their job.
                                                            -- bugtraq


http://dman.ddts.net/~dman/
--
[ Content of type application/pgp-signature deleted ]
--