Kevin Scaldeferri on Mon, 15 Mar 2004 18:37:58 -0600 (CST)


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [ALACPP] mail server issues


Well, here's a test to see if things work for me. This message ought to use mail.scaldeferri.com rather than the Overture servers. (For some reason, Mozilla makes it somewhat convoluted to set up different outgoing SMTP servers for different email accounts, and warns you that dire things might happen if you do...)


Kevin


Jon Stewart wrote:

I think this mainly effects Yahoo! folks, but the charybdis sysadmin
recently switched from qmail to Postfix and has enabled RFC-strictness to
cut down on spam (good). Unfortunately for us, Postfix is detecting
inconsistencies between IP addresses and DNS names from legitimate hosts,
as below (bad), so it looks like Chris and Kevin have had some email
silently rejected.

We're working on a resolution to the problem.


Jon

------- Forwarded Message

Replied: Mon, 15 Mar 2004 16:02:53 -0800
Return-Path: uckelman@xxxxxxxxxxx
Delivery-Date: Mon Mar 15 17:18:42 2004
Return-Path: <uckelman@xxxxxxxxxxx>
X-Original-To: stew1@xxxxxxxxxxx
Delivered-To: stew1@xxxxxxxxxxx
Received: from scylla.ellipsis.cx (scylla.ellipsis.cx [192.168.1.2])
	by charybdis.ellipsis.cx (Postfix) with ESMTP id 008F423174
	for <stew1@xxxxxxxxxxx>; Mon, 15 Mar 2004 17:18:42 -0600 (CST)
Received: by scylla.ellipsis.cx (Postfix, from userid 500)
	id EA6BE9D4F; Mon, 15 Mar 2004 17:18:41 -0600 (CST)
To: stew1@xxxxxxxxxxx
Subject: argh, another one
From: Joel Uckelman <uckelman@xxxxxxxxx>
Date: Mon, 15 Mar 2004 17:18:41 -0600
Sender: uckelman@xxxxxxxxxxx
Message-Id: <20040315231841.EA6BE9D4F@xxxxxxxxxxxxxxxxxx>

Looks like we have another person on your list who's mail server doesn't
follow RFC 2821:

Mar 15 16:01:20 charybdis postfix/smtpd[2332]: 4B0FE23174: reject: RCPT from ou
tsmtp-corp.overture.com[216.52.229.76]: 450 <msweep1.Corpsys.P4pnet.net>: Helo
command rejected: Host not found; from=<kevin@xxxxxxxxxxxxxxx> to=<alacpp@ellip
sis.cx> proto=ESMTP helo=<msweep1.Corpsys.P4pnet.net>

msweep1.Corpsys.P4pnet.net isn't in DNS, which is what 216.52.229.76
identifies itself as.

Hmmm. This is making me wonder whether being RFC-strict is going to result
in my having to fix every broken thing on the net myself. Perhaps just
getting things squared away with the people who regularly send mail here
is good enough? Thoughs?

------- End of Forwarded Message


_______________________________________________
alacpp mailing list
alacpp@xxxxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/alacpp