l weeks. In fact, had it not
been for Bill East replying to your post, I wouldn't have known this thread
exists.
-Original Message-
From: East, Bill [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 12:17 PM
To: Exchange Discussions
Subject: RE: Strange 550 error
Actual
s!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Chris Scharff
Sent: Wednesday, February 12, 2003 10:39 AM
To: Exchange Discussions
Subject: Re: Strange 550 error
It means exactly what it says (and 550 isn't terribly generic).
Domain.com is not
n for Bill East replying to your post, I wouldn't have known this thread
exists.
-Original Message-
From: East, Bill [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 12:17 PM
To: Exchange Discussions
Subject: RE: Strange 550 error
Actually the name "optonline.net
-- B. Franklin
> -Original Message-
> From: Jeffrey Dubyn [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 12, 2003 2:48 PM
> To: Exchange Discussions
> Subject: RE: Strange 550 error
>
>
> Jim -
>
> The customer is not on optonline.net,
Wednesday, February 12, 2003 10:39 AM
To: Exchange Discussions
Subject: Re: Strange 550 error
It means exactly what it says (and 550 isn't terribly generic).
Domain.com is not a local host on the server you connected to and that
server is also not a gateway for it. Either your DNS is
The present moment is all we have control of, on a good day. :-)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jeffrey Dubyn
Sent: Wednesday, February 12, 2003 12:54 PM
To: Exchange Discussions
Subject: RE: Strange 550 error
Charles -
I fully agree
rds,
Jeff
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Charles Marriott
Sent: Wednesday, February 12, 2003 2:52 PM
To: Exchange Discussions
Subject: RE: Strange 550 error
Telnet to port 25 and run the SMTP commands is the simple way to send
commands and read r
: Wednesday, February 12, 2003 12:39 PM
To: Exchange Discussions
Subject: RE: Strange 550 error
Chris - Thanks for the info - looks like it could be an MX issue as the MX
record for the customer points to oldcustomername.com not
newcustomername.com (although both names are still valid). FYI - If
hange Discussions
Subject: RE: Strange 550 error
"...no nothin' - just seems like the email went into a black hole."
Maybe you just answered your own question.
Have you checked the RBL's to see if your listed? Have you been spamming
this domain to death? With a domain name l
ns
Subject: Re: Strange 550 error
It means exactly what it says (and 550 isn't terribly generic).
Domain.com is not a local host on the server you connected to and that
server is also not a gateway for it. Either your DNS is fscked or one or
more of their Mx records is improperly configured. U
lf Of Public Folder:
Exchange
Sent: Wednesday, February 12, 2003 10:22 AM
To: Exchange Discussions
Cc: [EMAIL PROTECTED]
Subject: RE: Strange 550 error
I have seen misleading 550 errors if Reverse DNS to your domain is not
correct. If the IP address of your SMTP relay/server resolves to
mail.domai
ff
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of East, Bill
Sent: Wednesday, February 12, 2003 9:04 AM
To: Exchange Discussions
Subject: RE: Strange 550 error
As best as I can guess, the remote server is complaining that the format of
your messag
p you in a Blackhole list, just on general principles.
-Original Message-
From: Chris Scharff [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 7:39 AM
To: Exchange Discussions
Subject: Re: Strange 550 error
It means exactly what it says (and 550 isn't terribly generic).
It means exactly what it says (and 550 isn't terribly generic).
Domain.com is not a local host on the server you connected to and that
server is also not a gateway for it. Either your DNS is fscked or one or
more of their Mx records is improperly configured. Using telnet and the
basic SMTP command
I have seen misleading 550 errors if Reverse DNS to your domain is not
correct. If the IP address of your SMTP relay/server resolves to
mail.domain.com, but the SMTP server/relay actually claims to be a
different host name, then you can get a 550 error.
-Kevin
> -Original Message-
> Fro
As best as I can guess, the remote server is complaining that the format of
your message does not conform to the format it expects, which would be a
user at a local host in the recipient's domain. The other half of the
message is that it's not a gateway, so it will not pass on what appears to
be a
16 matches
Mail list logo
