On 12/1/2004 22:02, "Zain Memon" <[EMAIL PROTECTED]> wrote:
> If it was being bounced back by Speakeasy servers since the email
> isn't right, I would expect the maillog entry to at least have a
> speakeasy relay.
>
> I know for sure that the speakeasy email address is correct. I can get
> regular email on it.
>
> Since this is a production server, I can't really have some addresses
> that don't work; what can I do to get mail through to speakeasy?
>
>
> On Wed, 1 Dec 2004 10:58:20 +0100, Brad Knowles
> <[EMAIL PROTECTED]> wrote:
>> At 6:48 PM -0800 2004-11-30, Zain Memon wrote:
>>
>>> The log entry for the speakeasy one looks like this:
>>> to=<....speakeasy.net>, relay=virtual, delay=0, status=bounced
>>> (unknown user: "....speakeasy.net")
For an invalid username, the speakeasy.net mail server returns an error at
the moment the RCPT TO: command is issued during the SMTP conversation. As
in
;; ADDITIONAL SECTION:
mx01.speakeasy.net. 3600 IN A 216.254.0.195
mx02.speakeasy.net. 3600 IN A 216.254.0.196
;; Query time: 32 msec
;; SERVER: 198.133.237.1#53(198.133.237.1)
;; WHEN: Wed Dec 1 22:29:26 2004
;; MSG SIZE rcvd: 147
[EMAIL PROTECTED] namedb]# telnet 216.254.0.195 25
Trying 216.254.0.195...
Connected to 216.254.0.195.
Escape character is '^]'.
220 mail11.speakeasy.net ESMTP
ehlo fox.olympus.net
250-mail11.speakeasy.net
250-PIPELINING
250-SIZE 20971520
250-STARTTLS
250-AUTH LOGIN PLAIN
250 8BITMIME
mail from:<[EMAIL PROTECTED]>
250 ok
rcpt to:<[EMAIL PROTECTED]>
554 Sorry, no mailbox here by that name. (#5.1.1)
Quit
For an invalid address (which doesn't seem to be the case here), I would
expect your log entry to look the way it does.
Perhaps your mailing list server is not liked by Speakeasy (you sent your
message to the list via gmail, so we don't know what your server is). Many
servers reject at RCPT TO: time if they dislike the connecting server (IP
address or behavior), and may well claim there is no such mailbox in that
situation (to avoid giving away information).
[It might seem more logical to reject the connection from a disliked server
at connection time, but...
a. even if they dislike the server, they should accept mail for
Postmaster (and, these days, also [EMAIL PROTECTED] as well) and at connect
time they can't know that's coming
b. the sending mail server is apt to try again on the assumption that
the refusal to connect is temporary. In fact, it really should do so for
several days (a significant number of Washington state school districts shut
down their mail servers over the weekend...or at least long weekends, for
example).
Or, they could reject after the EHLO (or for an old-fashioned mail transfer
agent HELO) command), but argument a above still applies, and there are many
broken mail transfer agents out there which refuse to take no for an answer
at EHLO time and try again.]
--John
------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
