We started getting these, for reasons unknown, for
some pacbell.net email addresses,
550 5.0.0 ylpvm35.prodigy.net Access Denied. To request removal, send the complete error message, including your ip addresses, in an E-mail to removeme@sbc.sbcglobal.net
With great trepidation, I went ahead and tried the email
address despite Googling it first and seeing few success
stories and in fact some chat on this list about the
sooper-lameness.
But I had to laugh when I got this bounce back,
Interesting... we just started getting a bunch of these too. I wonder if
there's a glitch on their side.
w
550 5.0.0 ylpvm35.prodigy.net Access Denied. To request removal, send the
complete error message, including your ip addresses, in an E-mail to
removeme@sbc.sbcglobal.netInteresting... we just started getting a bunch of these too. I wonder if
there's a glitch on their side.
I just did an MX lookup for sbcglobal.net, which yielded a bunch of hosts
with prodigy.net hostnames:
;; QUESTION SECTION:
;sbcglobal.net. IN MX
;; ANSWER SECTION:
sbcglobal.net. 4021 IN MX 10 sbcmx4.prodigy.net.
sbcglobal.net. 4021 IN MX 10 sbcmx5.prodigy.net.
sbcglobal.net. 4021 IN MX 10 sbcmx6.prodigy.net.
sbcglobal.net. 4021 IN MX 10 sbcmx1.prodigy.net.
sbcglobal.net. 4021 IN MX 10 sbcmx2.prodigy.net.
sbcglobal.net. 4021 IN MX 10 sbcmx3.prodigy.net.
And when I connected to one of them it seemed not to know it was an
sbcglobal.net MX:
mail:~ postmstr$ telnet sbcmx1.prodigy.net 25
Trying 207.115.57.15...
Connected to sbcmx1.prodigy.net.
Escape character is '^]'.
220 ylpvm21.prodigy.net ESMTP Sendmail 8.13.6 inb/8.13.6; Tue, 5 Dec 2006
17:22:34 -0500
helo mail.alfordmedia.com
250 ylpvm21.prodigy.net Hello mail.alfordmedia.com [12.106.209.189], pleased
to meet you
mail from:<dave.pooser@alfordmedia.com>
250 2.1.0 <dave.pooser@alfordmedia.com>... Sender ok
rcpt to:<[someuser]@sbclobal.net>
553 5.3.0 <[someuser]@sbclobal.net>... Relaying is NOT allowed here
quit
221 2.0.0 ylpvm21.prodigy.net closing connection
I'm going with "clueless until proven otherwise."
I'm going with "clueless until proven otherwise."
Okay, maybe I'm the clueless one-- that's a typo. If I add the silent
invisible "g" into sbcglobal it works.
Sigh.
On the other hand, we do appear to have some nonresponsive machines in the
round-robin:
mail:~ postmstr$ telnet sbcmx1.prodigy.net 25
Trying 207.115.57.15...
telnet: connect to address 207.115.57.15: Connection refused
telnet: Unable to connect to remote host
mail:~ postmstr$ telnet sbcmx1.prodigy.net 25
Trying 207.115.57.15...
telnet: connect to address 207.115.57.15: Connection refused
telnet: Unable to connect to remote host
mail:~ postmstr$ telnet sbcmx1.prodigy.net 25
Trying 207.115.57.15...
Connected to sbcmx1.prodigy.net.
Escape character is '^]'.
I still think there is a real problem on their end, besides my fat fingers.
