[TAG] [MAILER-DAEMON at localhost.localdomain: Undelivered Mail Returned to Sender]
Benjamin A. Okopnik
ben at linuxgazette.net
Thu Aug 17 20:00:48 MSD 2006
On Thu, Aug 17, 2006 at 03:00:27AM -0700, Rick Moen wrote:
> Quoting Claude Sutton (cssutto at attglobal.net):
> > Should I send a copy of this to the tech guy at 2it.net or should I wait
> > to see if there is something I am doing that causes the address to look
> > like a fake?
> At the risk of sounding cranky: Why don't you _read_ them, first?
I don't mean to sound like we're ganging up on you, Claude, but - yeah,
that seems to be the broken component in the communication here. Not
horribly broken, since you seem to eventually follow the advice that's
given, but it does take several repetitions. Now, Rick and I both get
paid large amounts of^W^W^Wnot enough money to do this professionally; I
can't speak for him, but from my perspective, giving advice *without
charge* and having it ignored is pretty galling. I'd appreciate it if
you would not do that anymore.
I realize that it's been a lot of new information and things to do - but
I assure you that paying careful attention to what's been said will
greatly reduce the amount of labor necessary, while ignoring it will
multiply it by a large factor. This is part of the reason that this
process has taken so long.
> Also, I hope you're aware that I have no idea who "2it.net" is, or why
> they are relevant to your situation. Again, it's best if your help
> requests are specific, concise, and self-contained. If helping you
> requires knowing something about "2it.net", then it's best for you to
> include that information.
> Anyhow: The first DSN was from my host. You had sent mail claiming to
> be from "claudesutton at suttonmachine.com". While considering whether to
> accept the mail, my server did a "callout" SMTP session to verify that
> "claudesutton at suttonmachine.com" is a deliverable address, as required
> by the RFCs. It was not: Upon reaching IP address 220.127.116.11
> (presumably, one of the mail exchangers for suttonmachine.com), it was
> told "550 (permanent reject): Relaying denied."
> My server requires that delivering machines obey key RFCs (absent manual
> whitelisting by me); otherwise, it rejects the mail and explains why.
> Your job, of course, is to figure out why mail is not being accepted for
> "claudesutton at suttonmachine.com" and fix that.
ben at Fenrir:~$ telnet mail.suttonmachine.com 25
Connected to hermes.ncaccess.net.
Escape character is '^]'.
220 [hermes.ncaccess.net ESMTP for 2it.net; Thu, 17 Aug 2006 11:36:39 -0400]
250-hermes.ncaccess.net Hello 84.sub-70-197-138.myvzw.com [18.104.22.168], pleased to meet you
250-AUTH LOGIN PLAIN
MAIL FROM: ben at linuxgazette.net
250 2.1.0 ben at linuxgazette.net... Sender ok
RCPT TO: claudesutton at suttonmachine.com
550 5.7.1 claudesutton at suttonmachine.com... Relaying denied. Proper authentication required.
RCPT TO: claudesutton
550 5.1.1 claudesutton... User unknown
To summarize: your mail server (mail.suttonmachine.net/2it.net) is
broken in that it doesn't know who "suttonmachine.com" is - see that
"Relaying denied" message? It also doesn't know anything about a user
named "claudesutton". Therefore, every time you try to send mail to
"claudesutton at suttonmachine.com", you're going to get a DSN telling you
that there's a problem - and you keep including that address in the CC
list when you send us mail.
That, as far as I can tell, covers the entire situation.
* Ben Okopnik * Editor-in-Chief, Linux Gazette * http://linuxgazette.net *
More information about the TAG