RE: Strange 550 error

2003-02-13 Thread Jeffrey Dubyn
Jim -

Relax.  

I'm just some poor schlub who subscribes to a cable ISP - it's not my
company.  Heck, I'd be off jetting around the world like the owners of this
cable company do if it was my company.  The bastards own the Knicks,
Rangers, Madison Square Garden and a host of other small luxuries.  Anyway,
we're off-topic here so no need to man the flame-thrower over this issue.  

Regards,

Jeff

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Blunt, James H
(Jim)
Sent: Thursday, February 13, 2003 4:27 PM
To: Exchange Discussions
Subject: RE: Strange 550 error


So...

You don't consider sending bulk e-mail from accounts like the ones below as
SPAM?

[EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED]

Your company is listed in the FiveTen block list and was already in MY
personal block list and has been for several 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


Actually the name "optonline.net" is misleading, the company I believe is
"Optimum Online" or some such, n'est ce pas? But the name was a point of
discussion, Jeffrey; it appears that the first thing that a spammer does
after bringing the KFC and Schlitz into his trailer is to pick a domain name
with the phrase "opt-in" in it. At the moment I am turfing email from
optinforyou, optindeals, opt-inemail, optinllc, and about 30 other domains
with the word "opt" in them.

-- 
be - MOS

The use of money is all the advantage there is to having money.
-- 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, is not listed at ordb.org, there 
> has not been any spamming coming from this domain from this
> server, and the
> problem is sporadic - so I don't think that's the issue.  
> 
> And what's you got against Optonline.net :)  Although the owners won't 
> let us watch the Yankees (can't get it on cable here on Long
> Island!), they give
> kick as* Internet speeds.
> 
> Regards,
> 
> Jeff
> 
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of Blunt, James 
> H
> (Jim)
> Sent: Wednesday, February 12, 2003 2:17 PM
> To: Exchange 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 like optonline.net,
> I'd be tempted
> to drop 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).
> 
> 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 commands in RFC821 will allow you to confirm this 
> for yourself if
> you'd like.[1]
> 
> [1] Essential skills to pick up, now is as good a time as any.
> 
> On 2/12/03 7:42, "Jeffrey Dubyn" <[EMAIL PROTECTED]> wrote:
> 
> 
> 
> I have an issue with an Exchange 2000 SP3 server where an email sent 
> from inside the Exchange organization is not getting to some
> recipients in a 
> specific domain.  I have logging turned up, and found a 
> strange message: 
> 
> 550+not+local+host+recipientdomain.com,+not+a+gateway
> 
> The 550 error maps to a generic protocol error (SMTP error), but I 
> can't make heads or tails out of the rest of the message.
> 
> What is strange is that the domain comes up successfully in nslookup 
> and from the Exchange server, I can connect via telnet to port
> 25.  The users 
> have had no trouble sending email to this recipient at this 
> domain before or
> 
> since, except for this most important email (or course).   
> There was no NDR,
> 
> no nothin' - just seems like the email went into a black hole.
> 
> Thanks for any assistance!
> 
> 
> 

Re: Strange 550 error

2003-02-13 Thread Chris Scharff
Real domain names would be the only way we could possibly provide more info
now.

On 2/12/03 13:39, "Jeffrey Dubyn" <[EMAIL PROTECTED]> wrote:



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 you 
check out MSKB 284204, it does say that 550 maps to a "Generic protocol 
error (SMTP error)".  Any suggestions on how to use the info in rfc821 to 
determine what the issue is and why it is sporadic?  Thanks! 

-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 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 commands in RFC821 will allow you to confirm this for yourself if

you'd like.[1] 

[1] Essential skills to pick up, now is as good a time as any. 

On 2/12/03 7:42, "Jeffrey Dubyn" <[EMAIL PROTECTED]> wrote: 



I have an issue with an Exchange 2000 SP3 server where an email sent from 
inside the Exchange organization is not getting to some recipients in a 
specific domain.  I have logging turned up, and found a strange message: 

550+not+local+host+recipientdomain.com,+not+a+gateway 

The 550 error maps to a generic protocol error (SMTP error), but I can't 
make heads or tails out of the rest of the message.  

What is strange is that the domain comes up successfully in nslookup and 
from the Exchange server, I can connect via telnet to port 25.  The users 
have had no trouble sending email to this recipient at this domain before or


since, except for this most important email (or course).   There was no NDR,


no nothin' - just seems like the email went into a black hole. 

Thanks for any assistance! 


_ 
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm 
Archives:   http://www.swynk.com/sitesearch/search.asp 
To unsubscribe: mailto:[EMAIL PROTECTED] 
Exchange List admin:[EMAIL PROTECTED] 






_ 
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm 
Archives:   http://www.swynk.com/sitesearch/search.asp 
To unsubscribe: mailto:[EMAIL PROTECTED] 
Exchange List admin:[EMAIL PROTECTED] 


_ 
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm 
Archives:   http://www.swynk.com/sitesearch/search.asp 
To unsubscribe: mailto:[EMAIL PROTECTED] 
Exchange List admin:[EMAIL PROTECTED] 






_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Strange 550 error

2003-02-13 Thread Blunt, James H (Jim)
So...

You don't consider sending bulk e-mail from accounts like the ones below as
SPAM?

[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

Your company is listed in the FiveTen block list and was already in MY
personal block list and has been for several 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


Actually the name "optonline.net" is misleading, the company I believe is
"Optimum Online" or some such, n'est ce pas? But the name was a point of
discussion, Jeffrey; it appears that the first thing that a spammer does
after bringing the KFC and Schlitz into his trailer is to pick a domain name
with the phrase "opt-in" in it. At the moment I am turfing email from
optinforyou, optindeals, opt-inemail, optinllc, and about 30 other domains
with the word "opt" in them.

-- 
be - MOS

The use of money is all the advantage there is to having money.
-- 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, is not listed at
> ordb.org, there has
> not been any spamming coming from this domain from this 
> server, and the
> problem is sporadic - so I don't think that's the issue.  
> 
> And what's you got against Optonline.net :)  Although the
> owners won't let
> us watch the Yankees (can't get it on cable here on Long 
> Island!), they give
> kick as* Internet speeds.
> 
> Regards,
> 
> Jeff
> 
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of
> Blunt, James H
> (Jim)
> Sent: Wednesday, February 12, 2003 2:17 PM
> To: Exchange 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 like optonline.net, 
> I'd be tempted
> to drop 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).
> 
> 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 commands in RFC821 will allow you to confirm this 
> for yourself if
> you'd like.[1]
> 
> [1] Essential skills to pick up, now is as good a time as any.
> 
> On 2/12/03 7:42, "Jeffrey Dubyn" <[EMAIL PROTECTED]> wrote:
> 
> 
> 
> I have an issue with an Exchange 2000 SP3 server where an
> email sent from 
> inside the Exchange organization is not getting to some 
> recipients in a 
> specific domain.  I have logging turned up, and found a 
> strange message: 
> 
> 550+not+local+host+recipientdomain.com,+not+a+gateway
> 
> The 550 error maps to a generic protocol error (SMTP error),
> but I can't 
> make heads or tails out of the rest of the message.  
> 
> What is strange is that the domain comes up successfully in
> nslookup and 
> from the Exchange server, I can connect via telnet to port 
> 25.  The users 
> have had no trouble sending email to this recipient at this 
> domain before or
> 
> since, except for this most important email (or course).   
> There was no NDR,
> 
> no nothin' - just seems like the email went into a black hole.
> 
> Thanks for any assistance!
> 
> 
> _ 
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm 
> Archives:   http://www.swynk.com/sitesearch/search.asp 
> To unsubscribe: mailto:[EMAIL PROTECTED] 
> Exchange List admin:[EMAIL PROTECTED] 
> 
> 
> 
> 
> 
> 
> _
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
> Archives:   http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
>

RE: Strange 550 error

2003-02-12 Thread East, Bill
Actually the name "optonline.net" is misleading, the company I believe is
"Optimum Online" or some such, n'est ce pas? But the name was a point of
discussion, Jeffrey; it appears that the first thing that a spammer does
after bringing the KFC and Schlitz into his trailer is to pick a domain name
with the phrase "opt-in" in it. At the moment I am turfing email from
optinforyou, optindeals, opt-inemail, optinllc, and about 30 other domains
with the word "opt" in them.

-- 
be - MOS

The use of money is all the advantage there is to having money.
-- 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, is not listed at 
> ordb.org, there has
> not been any spamming coming from this domain from this 
> server, and the
> problem is sporadic - so I don't think that's the issue.  
> 
> And what's you got against Optonline.net :)  Although the 
> owners won't let
> us watch the Yankees (can't get it on cable here on Long 
> Island!), they give
> kick as* Internet speeds.
> 
> Regards,
> 
> Jeff
> 
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of 
> Blunt, James H
> (Jim)
> Sent: Wednesday, February 12, 2003 2:17 PM
> To: Exchange 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 like optonline.net, 
> I'd be tempted
> to drop 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).
> 
> 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 commands in RFC821 will allow you to confirm this 
> for yourself if
> you'd like.[1]
> 
> [1] Essential skills to pick up, now is as good a time as any.
> 
> On 2/12/03 7:42, "Jeffrey Dubyn" <[EMAIL PROTECTED]> wrote:
> 
> 
> 
> I have an issue with an Exchange 2000 SP3 server where an 
> email sent from 
> inside the Exchange organization is not getting to some 
> recipients in a 
> specific domain.  I have logging turned up, and found a 
> strange message: 
> 
> 550+not+local+host+recipientdomain.com,+not+a+gateway
> 
> The 550 error maps to a generic protocol error (SMTP error), 
> but I can't 
> make heads or tails out of the rest of the message.  
> 
> What is strange is that the domain comes up successfully in 
> nslookup and 
> from the Exchange server, I can connect via telnet to port 
> 25.  The users 
> have had no trouble sending email to this recipient at this 
> domain before or
> 
> since, except for this most important email (or course).   
> There was no NDR,
> 
> no nothin' - just seems like the email went into a black hole. 
> 
> Thanks for any assistance! 
> 
> 
> _ 
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm 
> Archives:   http://www.swynk.com/sitesearch/search.asp 
> To unsubscribe: mailto:[EMAIL PROTECTED] 
> Exchange List admin:[EMAIL PROTECTED] 
> 
> 
> 
> 
> 
> 
> _
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
> Archives:   http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin:[EMAIL PROTECTED]
> 
> _
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
> Archives:   http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin:[EMAIL PROTECTED]
> 
> 
> _
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
> Archives:   http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin:[EMAIL PROTECTED]
> 

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



Re: Strange 550 error

2003-02-12 Thread Chris Scharff
Microsoft's definitions are sometimes interesting. Where the Mx records
point generally doesn't matter... 
http://mail-resources.com/modules.php?op=modload&name=Sections&file=index&re
q=viewarticle&artid=2 might help you to troubleshoot.


On 2/12/03 13:39, "Jeffrey Dubyn" <[EMAIL PROTECTED]> wrote:



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 you 
check out MSKB 284204, it does say that 550 maps to a "Generic protocol 
error (SMTP error)".  Any suggestions on how to use the info in rfc821 to 
determine what the issue is and why it is sporadic?  Thanks! 

-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 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 commands in RFC821 will allow you to confirm this for yourself if

you'd like.[1] 

[1] Essential skills to pick up, now is as good a time as any. 

On 2/12/03 7:42, "Jeffrey Dubyn" <[EMAIL PROTECTED]> wrote: 



I have an issue with an Exchange 2000 SP3 server where an email sent from 
inside the Exchange organization is not getting to some recipients in a 
specific domain.  I have logging turned up, and found a strange message: 

550+not+local+host+recipientdomain.com,+not+a+gateway 

The 550 error maps to a generic protocol error (SMTP error), but I can't 
make heads or tails out of the rest of the message.  

What is strange is that the domain comes up successfully in nslookup and 
from the Exchange server, I can connect via telnet to port 25.  The users 
have had no trouble sending email to this recipient at this domain before or


since, except for this most important email (or course).   There was no NDR,


no nothin' - just seems like the email went into a black hole. 

Thanks for any assistance! 


_ 
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm 
Archives:   http://www.swynk.com/sitesearch/search.asp 
To unsubscribe: mailto:[EMAIL PROTECTED] 
Exchange List admin:[EMAIL PROTECTED] 






_ 
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm 
Archives:   http://www.swynk.com/sitesearch/search.asp 
To unsubscribe: mailto:[EMAIL PROTECTED] 
Exchange List admin:[EMAIL PROTECTED] 


_ 
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm 
Archives:   http://www.swynk.com/sitesearch/search.asp 
To unsubscribe: mailto:[EMAIL PROTECTED] 
Exchange List admin:[EMAIL PROTECTED] 






_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Strange 550 error

2003-02-12 Thread Charles Marriott
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 and have successfully sent email through by telnetting from
the Exchange server to that domain.  What I'm trying to figure out is how to
ensure this doesn't happen in the future as the issue is sporadic, but is
quite perturbing to the customer.

Regards,

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 replies one at a time. The best way to ts SMTP issues imo.
(I am not Chris and not speaking for him)

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jeffrey Dubyn
Sent: 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 you
check out MSKB 284204, it does say that 550 maps to a "Generic protocol
error (SMTP error)".  Any suggestions on how to use the info in rfc821 to
determine what the issue is and why it is sporadic?  Thanks!

-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 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 commands in RFC821 will allow you to confirm this for yourself if
you'd like.[1]

[1] Essential skills to pick up, now is as good a time as any.

On 2/12/03 7:42, "Jeffrey Dubyn" <[EMAIL PROTECTED]> wrote:



I have an issue with an Exchange 2000 SP3 server where an email sent from
inside the Exchange organization is not getting to some recipients in a
specific domain.  I have logging turned up, and found a strange message:

550+not+local+host+recipientdomain.com,+not+a+gateway

The 550 error maps to a generic protocol error (SMTP error), but I can't
make heads or tails out of the rest of the message.

What is strange is that the domain comes up successfully in nslookup and
from the Exchange server, I can connect via telnet to port 25.  The users
have had no trouble sending email to this recipient at this domain before or

since, except for this most important email (or course).   There was no NDR,

no nothin' - just seems like the email went into a black hole.

Thanks for any assistance!


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]






_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Strange 550 error

2003-02-12 Thread Jeffrey Dubyn
Charles -

I fully agree and have successfully sent email through by telnetting from
the Exchange server to that domain.  What I'm trying to figure out is how to
ensure this doesn't happen in the future as the issue is sporadic, but is
quite perturbing to the customer.  

Regards,

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 replies one at a time. The best way to ts SMTP issues imo.
(I am not Chris and not speaking for him)

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jeffrey Dubyn
Sent: 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 you
check out MSKB 284204, it does say that 550 maps to a "Generic protocol
error (SMTP error)".  Any suggestions on how to use the info in rfc821 to
determine what the issue is and why it is sporadic?  Thanks!

-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 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 commands in RFC821 will allow you to confirm this for yourself if
you'd like.[1]

[1] Essential skills to pick up, now is as good a time as any.

On 2/12/03 7:42, "Jeffrey Dubyn" <[EMAIL PROTECTED]> wrote:



I have an issue with an Exchange 2000 SP3 server where an email sent from
inside the Exchange organization is not getting to some recipients in a
specific domain.  I have logging turned up, and found a strange message:

550+not+local+host+recipientdomain.com,+not+a+gateway

The 550 error maps to a generic protocol error (SMTP error), but I can't
make heads or tails out of the rest of the message.

What is strange is that the domain comes up successfully in nslookup and
from the Exchange server, I can connect via telnet to port 25.  The users
have had no trouble sending email to this recipient at this domain before or

since, except for this most important email (or course).   There was no NDR,

no nothin' - just seems like the email went into a black hole.

Thanks for any assistance!


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]






_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Strange 550 error

2003-02-12 Thread Charles Marriott
Telnet to port 25 and run the SMTP commands is the simple way to send
commands and read replies one at a time. The best way to ts SMTP issues imo.
(I am not Chris and not speaking for him)

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jeffrey Dubyn
Sent: 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 you
check out MSKB 284204, it does say that 550 maps to a "Generic protocol
error (SMTP error)".  Any suggestions on how to use the info in rfc821 to
determine what the issue is and why it is sporadic?  Thanks!

-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 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 commands in RFC821 will allow you to confirm this for yourself if
you'd like.[1]

[1] Essential skills to pick up, now is as good a time as any.

On 2/12/03 7:42, "Jeffrey Dubyn" <[EMAIL PROTECTED]> wrote:



I have an issue with an Exchange 2000 SP3 server where an email sent from
inside the Exchange organization is not getting to some recipients in a
specific domain.  I have logging turned up, and found a strange message:

550+not+local+host+recipientdomain.com,+not+a+gateway

The 550 error maps to a generic protocol error (SMTP error), but I can't
make heads or tails out of the rest of the message.

What is strange is that the domain comes up successfully in nslookup and
from the Exchange server, I can connect via telnet to port 25.  The users
have had no trouble sending email to this recipient at this domain before or

since, except for this most important email (or course).   There was no NDR,

no nothin' - just seems like the email went into a black hole.

Thanks for any assistance!


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]






_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Strange 550 error

2003-02-12 Thread Jeffrey Dubyn
Jim -

The customer is not on optonline.net, is not listed at ordb.org, there has
not been any spamming coming from this domain from this server, and the
problem is sporadic - so I don't think that's the issue.  

And what's you got against Optonline.net :)  Although the owners won't let
us watch the Yankees (can't get it on cable here on Long Island!), they give
kick as* Internet speeds.

Regards,

Jeff

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Blunt, James H
(Jim)
Sent: Wednesday, February 12, 2003 2:17 PM
To: Exchange 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 like optonline.net, I'd be tempted
to drop 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).

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 commands in RFC821 will allow you to confirm this for yourself if
you'd like.[1]

[1] Essential skills to pick up, now is as good a time as any.

On 2/12/03 7:42, "Jeffrey Dubyn" <[EMAIL PROTECTED]> wrote:



I have an issue with an Exchange 2000 SP3 server where an email sent from 
inside the Exchange organization is not getting to some recipients in a 
specific domain.  I have logging turned up, and found a strange message: 

550+not+local+host+recipientdomain.com,+not+a+gateway

The 550 error maps to a generic protocol error (SMTP error), but I can't 
make heads or tails out of the rest of the message.  

What is strange is that the domain comes up successfully in nslookup and 
from the Exchange server, I can connect via telnet to port 25.  The users 
have had no trouble sending email to this recipient at this domain before or

since, except for this most important email (or course).   There was no NDR,

no nothin' - just seems like the email went into a black hole. 

Thanks for any assistance! 


_ 
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm 
Archives:   http://www.swynk.com/sitesearch/search.asp 
To unsubscribe: mailto:[EMAIL PROTECTED] 
Exchange List admin:[EMAIL PROTECTED] 






_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Strange 550 error

2003-02-12 Thread Jeffrey Dubyn
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 you
check out MSKB 284204, it does say that 550 maps to a "Generic protocol
error (SMTP error)".  Any suggestions on how to use the info in rfc821 to
determine what the issue is and why it is sporadic?  Thanks!

-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 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 commands in RFC821 will allow you to confirm this for yourself if
you'd like.[1]

[1] Essential skills to pick up, now is as good a time as any.

On 2/12/03 7:42, "Jeffrey Dubyn" <[EMAIL PROTECTED]> wrote:



I have an issue with an Exchange 2000 SP3 server where an email sent from 
inside the Exchange organization is not getting to some recipients in a 
specific domain.  I have logging turned up, and found a strange message: 

550+not+local+host+recipientdomain.com,+not+a+gateway

The 550 error maps to a generic protocol error (SMTP error), but I can't 
make heads or tails out of the rest of the message.  

What is strange is that the domain comes up successfully in nslookup and 
from the Exchange server, I can connect via telnet to port 25.  The users 
have had no trouble sending email to this recipient at this domain before or

since, except for this most important email (or course).   There was no NDR,

no nothin' - just seems like the email went into a black hole. 

Thanks for any assistance! 


_ 
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm 
Archives:   http://www.swynk.com/sitesearch/search.asp 
To unsubscribe: mailto:[EMAIL PROTECTED] 
Exchange List admin:[EMAIL PROTECTED] 






_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Strange 550 error

2003-02-12 Thread Jeffrey Dubyn
Thank you, that's a very good point.  The MX record for the customers domain
is actually mail.oldcompanyname.com, not mail.newcompanyname.com even though
the IP address is correct.  Thanks again!  Jeff

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf 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.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-
> From: Jeffrey Dubyn [mailto:[EMAIL PROTECTED]]
> Posted At: Wednesday, February 12, 2003 5:42 AM
> Posted To: Exchange
> Conversation: Strange 550 error
> Subject: Strange 550 error
> 
> 
> I have an issue with an Exchange 2000 SP3 server where an
> email sent from
> inside the Exchange organization is not getting to some 
> recipients in a
> specific domain.  I have logging turned up, and found a 
> strange message: 
> 
> 550+not+local+host+recipientdomain.com,+not+a+gateway
> 
> The 550 error maps to a generic protocol error (SMTP error),
> but I can't
> make heads or tails out of the rest of the message.  
> 
> What is strange is that the domain comes up successfully in
> nslookup and
> from the Exchange server, I can connect via telnet to port 
> 25.  The users
> have had no trouble sending email to this recipient at this 
> domain before or
> since, except for this most important email (or course).   
> There was no NDR,
> no nothin' - just seems like the email went into a black hole.
> 
> Thanks for any assistance!
> 
> 
> _
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
> Archives:   http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin:[EMAIL PROTECTED]
> 

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Strange 550 error

2003-02-12 Thread Jeffrey Dubyn
Bill -

The mail was not coming from optonline.net, but from a customer site using a
different ISP to another domain.  I didn't change the error at all - it's a
copy and paste from the log.  I didn't post the domains as I'm not sure if
the customer would appreciate it in a public forum.  

As for Optonline, it is a cable modem provider (excellent speeds!), but it
does allow people inside the network to relay - send out messages with no
regard for where it is coming from or where it is going to.  If I'm NOT
inside this network though, it does not allow relaying.  

Jeff

-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 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 non-local address. If you could give us the address to which you are
sending, even in the format @theaddress.tld, we might be able to
guess a little better. Oh, and did you munge the 550 message at all, or is
that how it appeared verbatim?

FWIW, there has been some discussion of your provider, optonline.com, on
news.admin.net-abuse.email in recent days, with the general concensus (hah!)
being that optonline is not a spammer, just a cable modem provider with a
lot of potentially abusable clients. So there is a small but existing
possiblity that you are being blocked due to your address.

-- 
be - MOS



Yow!  I just went below the poverty line!


> -Original Message-
> From: Jeffrey Dubyn [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 12, 2003 8:42 AM
> To: Exchange Discussions
> Subject: Strange 550 error
> 
> 
> I have an issue with an Exchange 2000 SP3 server where an
> email sent from
> inside the Exchange organization is not getting to some 
> recipients in a
> specific domain.  I have logging turned up, and found a 
> strange message: 
> 
> 550+not+local+host+recipientdomain.com,+not+a+gateway
> 
> The 550 error maps to a generic protocol error (SMTP error),
> but I can't
> make heads or tails out of the rest of the message.  
> 
> What is strange is that the domain comes up successfully in
> nslookup and
> from the Exchange server, I can connect via telnet to port 
> 25.  The users
> have had no trouble sending email to this recipient at this 
> domain before or
> since, except for this most important email (or course).   
> There was no NDR,
> no nothin' - just seems like the email went into a black hole.
> 
> Thanks for any assistance!
> 
> 
> _
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
> Archives:   http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin:[EMAIL PROTECTED]
> 

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Strange 550 error

2003-02-12 Thread Blunt, James H (Jim)
"...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 like optonline.net, I'd be tempted
to drop 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).

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 commands in RFC821 will allow you to confirm this for yourself if
you'd like.[1]

[1] Essential skills to pick up, now is as good a time as any.

On 2/12/03 7:42, "Jeffrey Dubyn" <[EMAIL PROTECTED]> wrote:



I have an issue with an Exchange 2000 SP3 server where an email sent from 
inside the Exchange organization is not getting to some recipients in a 
specific domain.  I have logging turned up, and found a strange message: 

550+not+local+host+recipientdomain.com,+not+a+gateway

The 550 error maps to a generic protocol error (SMTP error), but I can't 
make heads or tails out of the rest of the message.  

What is strange is that the domain comes up successfully in nslookup and 
from the Exchange server, I can connect via telnet to port 25.  The users 
have had no trouble sending email to this recipient at this domain before or

since, except for this most important email (or course).   There was no NDR,

no nothin' - just seems like the email went into a black hole. 

Thanks for any assistance! 


_ 
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm 
Archives:   http://www.swynk.com/sitesearch/search.asp 
To unsubscribe: mailto:[EMAIL PROTECTED] 
Exchange List admin:[EMAIL PROTECTED] 






_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



Re: Strange 550 error

2003-02-12 Thread Chris Scharff
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 commands in RFC821 will allow you to confirm this for yourself if
you'd like.[1]

[1] Essential skills to pick up, now is as good a time as any.

On 2/12/03 7:42, "Jeffrey Dubyn" <[EMAIL PROTECTED]> wrote:



I have an issue with an Exchange 2000 SP3 server where an email sent from 
inside the Exchange organization is not getting to some recipients in a 
specific domain.  I have logging turned up, and found a strange message: 

550+not+local+host+recipientdomain.com,+not+a+gateway 

The 550 error maps to a generic protocol error (SMTP error), but I can't 
make heads or tails out of the rest of the message.  

What is strange is that the domain comes up successfully in nslookup and 
from the Exchange server, I can connect via telnet to port 25.  The users 
have had no trouble sending email to this recipient at this domain before or

since, except for this most important email (or course).   There was no NDR,

no nothin' - just seems like the email went into a black hole. 

Thanks for any assistance! 


_ 
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm 
Archives:   http://www.swynk.com/sitesearch/search.asp 
To unsubscribe: mailto:[EMAIL PROTECTED] 
Exchange List admin:[EMAIL PROTECTED] 






_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Strange 550 error

2003-02-12 Thread Public Folder: Exchange

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-
> From: Jeffrey Dubyn [mailto:[EMAIL PROTECTED]] 
> Posted At: Wednesday, February 12, 2003 5:42 AM
> Posted To: Exchange
> Conversation: Strange 550 error
> Subject: Strange 550 error
> 
> 
> I have an issue with an Exchange 2000 SP3 server where an 
> email sent from
> inside the Exchange organization is not getting to some 
> recipients in a
> specific domain.  I have logging turned up, and found a 
> strange message: 
> 
> 550+not+local+host+recipientdomain.com,+not+a+gateway
> 
> The 550 error maps to a generic protocol error (SMTP error), 
> but I can't
> make heads or tails out of the rest of the message.  
> 
> What is strange is that the domain comes up successfully in 
> nslookup and
> from the Exchange server, I can connect via telnet to port 
> 25.  The users
> have had no trouble sending email to this recipient at this 
> domain before or
> since, except for this most important email (or course).   
> There was no NDR,
> no nothin' - just seems like the email went into a black hole.
> 
> Thanks for any assistance!
> 
> 
> _
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
> Archives:   http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin:[EMAIL PROTECTED]
> 

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Strange 550 error

2003-02-12 Thread East, Bill
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 non-local address. If you could give us the address to which you are
sending, even in the format @theaddress.tld, we might be able to
guess a little better. Oh, and did you munge the 550 message at all, or is
that how it appeared verbatim?

FWIW, there has been some discussion of your provider, optonline.com, on
news.admin.net-abuse.email in recent days, with the general concensus (hah!)
being that optonline is not a spammer, just a cable modem provider with a
lot of potentially abusable clients. So there is a small but existing
possiblity that you are being blocked due to your address.

-- 
be - MOS



Yow!  I just went below the poverty line!


> -Original Message-
> From: Jeffrey Dubyn [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 12, 2003 8:42 AM
> To: Exchange Discussions
> Subject: Strange 550 error
> 
> 
> I have an issue with an Exchange 2000 SP3 server where an 
> email sent from
> inside the Exchange organization is not getting to some 
> recipients in a
> specific domain.  I have logging turned up, and found a 
> strange message: 
> 
> 550+not+local+host+recipientdomain.com,+not+a+gateway
> 
> The 550 error maps to a generic protocol error (SMTP error), 
> but I can't
> make heads or tails out of the rest of the message.  
> 
> What is strange is that the domain comes up successfully in 
> nslookup and
> from the Exchange server, I can connect via telnet to port 
> 25.  The users
> have had no trouble sending email to this recipient at this 
> domain before or
> since, except for this most important email (or course).   
> There was no NDR,
> no nothin' - just seems like the email went into a black hole.
> 
> Thanks for any assistance!
> 
> 
> _
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
> Archives:   http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin:[EMAIL PROTECTED]
> 

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]