--Gerhard Pfeiffer wrote on 03.12.2001 14:58 +0100: >> The mx for test.bnbt.de (earth) does not run on Courier, kill >> the other smtp-server or tell us the contents of the bounce :) > > earth:/usr/lib/courier # lsof -i | grep smtp > couriertc 20850 root 5u inet 1151630 TCP *:smtp (LISTEN) > > But it is courier?
I was too quick, a telnet there showed: 220 earth ESMTP which violates RFC??? and cant possibly come from Courier... > Received: from earth (earth.bnbt.de [213.167.167.151]) Put a fqdn into etc/me and list this also in locals. > From: "Courier mail server at earth" <"Courier mail server at earth"> Courier usually completes the From: in bounces with @me or @defaultdomain, but this one is completely bogus. The receiving end will probably add the own hostname and mess up even more. > Received: from earth (earth.bnbt.de [::ffff:213.167.167.151]) > by earth with esmtp; Mon, 03 Dec 2001 06:52:30 +0100 > Received: from earth (earth.bnbt.de [::ffff:213.167.167.151]) > by earth with esmtp; Mon, 03 Dec 2001 06:52:30 +0100 > (... and some more received: - lines) Courier detects 'himself' via hostnames only, if this does not match anyting listed in locals, hosteddomains or aliases the mail will be forwarded to the primary mx, even if its at the same IP as the own esmtpd listes. The 'local detection' could be improved if also the ip-address would be checked. > Thanks for the tip with hosteddomains. hosteddomains will also need an entry in the authentification like '[EMAIL PROTECTED]', aliases points to an existing entry but will rewrite the host-part with @me which is not very pretty if your server receives mail on behalf of customers. Roland _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
