[Wylug-help] mail server problems

[Lee Evans]

Hi Roger,

If you're using the NTL SMTP server, this is what I suspect is happening:

You send the email from Thunderbird, via the NTL SMTP server.

NTL SMTP server delivers message to roger-beaumont.co.uk, via Message Labs,
who I assume then forward that on to your home server (tower2)

Tower2 doesn't know what to do with the message, for one reason or another,
and wants to send a delivery failure back to the sender (also
roger-beamont.co.uk)

It tries to do so by direct MX delivery, thus tries to deliver back to
roger-beaumont.co.uk via messagelabs.

DUL is the 'dial up users list' - not so common these days with broadband
and static IPs common place. Because you're on it, Message Labs and many
other people won't accept your email.

If you can reconfigure your server (tower2) so that it doesn't send out via
direct to MX delivery, but instead uses the NTL SMTP servers you should at
least be able to get the failure or NDR that it's trying to send you, and
can further diagnose from there.

HTH

Lee

-----Original Message-----
From: wylug-help-bounces at wylug.org.uk
[mailto:wylug-help-bounces at wylug.org.uk] On Behalf Of Roger Beaumont
Sent: 03 October 2008 18:02
To: wylug-help at wylug.org.uk
Subject: [Wylug-help] mail server problems

I'm trying to move my mail-server from a cHaos box onto my new CentOS 
server (file serving via both nfs and samba and web-serving went across 
without too much pain).

The old system uses, I believe, fetchmail, postfix and dovecot.

1. I made sure that all 3 of those were installed on the new server.
2. I copied the contents of /home/roger/mail/ from the old box to the 
new one, then reconfigured thunderbird (on a third machine) to look at 
192.168.1.10 for its IMAP mail, instead of at 192.168.1.1 - the IP for 
the new server and got access to the new version.
3. I copied the configuration files (/root/.fetchmailrc 
/etc/postfix/main.cf /etc /postfix/master.cf and /etc/dovecot.conf) from 
the old box to the new box
4. dovecot complained about the configuration file and stopped, so I 
re-instated its previous default version, and started dovecot again - 
and once more the third machine had access to the new copy.

However, if I send a test message to myself, it always ends up in 
/var/spool/mail/root not in /home/roger/mail/

I've searched for the relevant stuff until I'm nearly blind, but cannot 
recognise anything useful.

fetchmail correctly reports (fetchmail -V -v -v) that it has identified 
my internet mail address as equivalent to the local user roger - and 
that it is operating in single drop mode.

Looking at /var/spool/mail/root shows the messages I tried to send 
interspersed with delivery failure messages like:
-------------------------------------------------------------
 From MAILER-DAEMON at tower2.internal  Fri Oct  3 17:06:22 2008
Return-Path: <MAILER-DAEMON at tower2.internal>
Received: from localhost (localhost)
        by tower2.internal (8.13.8/8.13.8) id m93G6MFl021285;
        Fri, 3 Oct 2008 17:06:22 +0100
Date: Fri, 3 Oct 2008 17:06:22 +0100
From: Mail Delivery Subsystem <MAILER-DAEMON at tower2.internal>
Message-Id: <200810031606.m93G6MFl021285 at tower2.internal>
To: postmaster at tower2.internal
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="m93G6MFl021285.1223049982/tower2.internal"
Subject: Postmaster notify: see transcript for details
Auto-Submitted: auto-generated (postmaster-notification)

This is a MIME-encapsulated message

--m93G6MFl021285.1223049982/tower2.internal

The original message was received at Fri, 3 Oct 2008 17:06:22 +0100
from localhost
with id m93G6MFk021285

   ----- The following addresses had permanent fatal errors -----
<roger at roger-beaumont.co.uk>
    (reason: 553-mail rejected because your IP is in DUL. See)

   ----- Transcript of session follows -----
... while talking to cluster3.eu.messagelabs.com.:
 >>> DATA
<<< 553-mail rejected because your IP is in DUL. See
<<< 553 http://www.mail-abuse.com/enduserinfo.html
550 5.1.1 <roger at roger-beaumont.co.uk>... User unknown
<<< 503 RCPT first (#5.5.1)

--m93G6MFl021285.1223049982/tower2.internal
Content-Type: message/delivery-status

Reporting-MTA: dns; tower2.internal
Received-From-MTA: DNS; tower2.internal
Arrival-Date: Fri, 3 Oct 2008 17:06:22 +0100

Final-Recipient: RFC822; roger at roger-beaumont.co.uk
Action: failed
Status: 5.1.3
Remote-MTA: DNS; cluster3.eu.messagelabs.com
Diagnostic-Code: SMTP; 553-mail rejected because your IP is in DUL. See
Last-Attempt-Date: Fri, 3 Oct 2008 17:06:22 +0100

-----------------------------------------------------------
and that confuses the hell out of me, because Thunderbird is set to use 
the NTL smtp server, so why is tower2.internal sending anything external?

Help!

Roger

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

_______________________________________________
Wylug-help mailing list
Wylug-help at wylug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/wylug-help