SmtpMail hell

[Jeremy]

I keep getting this message when I try to send mail with SmtpMail:

"The message could not be sent to the SMTP server. The transport error code
was 0x800ccc64. The server response was 502 Unknown command"

When I look in the mail server's log, the last thing it processes is the
command "SATA", then it 502's.

When I run the app locally, on my development machine, with a different SMTP
server, all is well. The server is Windows2000, all the latest updates. The
mail server is ArGoSoft, which has authentication enabled, but the WebServer
IP address is trusted.

Oh, one other bit of wierdness, when I use the same SMTP server as on my dev
machine, it gets the same error, but specifically states, "502: command SATA
unknown", the web server and my dev machine are both on the same network
(RR), so I expected this to work.

Any help would be great...

Jeremy

 

[J. Peter Mugaas]

I keep getting this message when I try to send mail with SmtpMail:

"The message could not be sent to the SMTP server. The transport error code
was 0x800ccc64. The server response was 502 Unknown command"

When I look in the mail server's log, the last thing it processes is the
command "SATA", then it 502's.

When I run the app locally, on my development machine, with a different SMTP
server, all is well. The server is Windows2000, all the latest updates. The
mail server is ArGoSoft, which has authentication enabled, but the WebServer
IP address is trusted.

Oh, one other bit of wierdness, when I use the same SMTP server as on my dev
machine, it gets the same error, but specifically states, "502: command SATA
unknown", the web server and my dev machine are both on the same network
(RR), so I expected this to work.

Any help would be great...

I'm not sure how helpful this is but you might want to consider seeing if
Indy (http://www.indyproject.org) would work better for you. One thing I
suspect is that the server doesn't support a SATA command. Are you really
that you didn't mean DATA command (I know I sound like I'm flaming but it
is important because the DATA command is part of the SMTP RFC 2821
specification while I saw no mention of a SATA command).I did search the
Indy 10 source-code and I saw not one mention of the word "SATA". If you
really did mean DATA, then we have another thing we need to discuss.

HTH.

--
J. Peter Mugaas - Indy Pit Crew
Internet Direct (Indy) Website - http://www.nevrona.com/Indy
Personal Home Page - http://www.wvnet.edu/~oma00215
If I want to do business with you, I will contact you. Otherwise, do not
contact me.

 

[Jeremy Cowles]

First off, thank you so much for the reply, I can't find any info on this,
and no one to help. I really appreciate it!

I'm not sure how helpful this is but you might want to consider seeing if
Indy (http://www.indyproject.org) would work better for you.

Does Indy have an SMTP component?

One thing I
suspect is that the server doesn't support a SATA command. Are you really
that you didn't mean DATA command (I know I sound like I'm flaming but it
is important because the DATA command is part of the SMTP RFC 2821
specification while I saw no mention of a SATA command).

You have hit the nail on the head, there is no SATA command, it's almost
like there is a typo in cdosys.dll!!

Any thoughts on this?

 

[Jon Skeet [C# MVP]]

Does Indy have an SMTP component?

Yes - SMTP client, relay and server components, in fact.

 

[J. Peter Mugaas]

[snip]
Does Indy have an SMTP component?

Yes, there's a client and server class.

[snip]
You have hit the nail on the head, there is no SATA command, it's almost
like there is a typo in cdosys.dll!!

Any thoughts on this?

I'm not completely sure about this myself because some SMTP servers and
clients support SMTP extensions. Some are in other RFC documents and IETF
Internet Drafts and some might have been adopted informally in some places
(I've seen that with FTP). I do not know of a SATA extension but I am
willing to entertain the possibility that there might be one. If that is
the case, you may still be talking about a possible bug with how such
extensions are handles. Usually, it is not a good idea to bet the farm one
what extensions a server will support. For example, part of the SMTP
protocol is a "HELO <domain-name>" command. There is an extended version
called "EHLO <domain-name>" that is in the RFC's but is not supported by
all servers. Indy handles this with a default to attempt an "EHLO" and if
that fails, then it does a "HELO" command as a fallback. This is handled
transparently. With most other extensions, a client can discover what SMTP
extensions are supported by using the EHLO command reply which lists those
extensions after a greeting. A SMTP client should not attempt to use an
extension which is not listed.

You may want to speak with the vendor about this "SATA" problem you have
been having.

HTH.

--
J. Peter Mugaas - Indy Pit Crew
Internet Direct (Indy) Website - http://www.nevrona.com/Indy
Personal Home Page - http://www.wvnet.edu/~oma00215
If I want to do business with you, I will contact you. Otherwise, do not
contact me.

 

[Jeremy]

I just tried the Indy SMTP, it worked fine on my local dev machine, but has
the same issue when I put it on the live server:

(IPs & Email have been changed)

2/23/2004 7:04:20 PM - Requested SMTP connection from 0.0.0.0 [0.0.0.0],
ID=31
2/23/2004 7:04:20 PM - ( 31) Connection from trusted IP address 0.0.0.0
2/23/2004 7:04:20 PM - ( 31) 220 ArGoSoft Mail Server Pro for
WinNT/2000/XP, Version 1.8 (1.8.5.0)
2/23/2004 7:04:20 PM - ( 31) EHLO [server]
2/23/2004 7:04:20 PM - ( 31) 250-Welcome, 0.0.0.0 [0.0.0.0], pleased to
meet you
2/23/2004 7:04:20 PM - ( 31) 250-AUTH=LOGIN
2/23/2004 7:04:20 PM - ( 31) 250-AUTH LOGIN
2/23/2004 7:04:20 PM - ( 31) 250-SIZE 5242880
2/23/2004 7:04:20 PM - ( 31) 250 HELP
2/23/2004 7:04:20 PM - ( 31) RSET
2/23/2004 7:04:20 PM - ( 31) 250 Reset state
2/23/2004 7:04:21 PM - ( 31) MAIL FROM:<>
2/23/2004 7:04:21 PM - ( 31) 250 Sender "[email]" OK (Trusted)
2/23/2004 7:04:21 PM - ( 31) RCPT TO:<[email]>
2/23/2004 7:04:21 PM - ( 31) 250 Recipient "[email]" OK...
2/23/2004 7:04:21 PM - ( 31) SATA
2/23/2004 7:04:22 PM - ( 31) 502 Unknown command
2/23/2004 7:04:22 PM - ( 31) QUIT

Any idea what in the world might be causing this?

 

[J. Peter Mugaas]

I just tried the Indy SMTP, it worked fine on my local dev machine, but has
the same issue when I put it on the live server:

[snip]
Any idea what in the world might be causing this?

No, not really. I wonder what is going on as I still think that SATA looks
strange. I may have to look at this myself including stepping through the
code. Something doesn't add up.

I'll follow up later about this matter.

--
J. Peter Mugaas - Indy Pit Crew
Internet Direct (Indy) Website - http://www.nevrona.com/Indy
Personal Home Page - http://www.wvnet.edu/~oma00215
If I want to do business with you, I will contact you. Otherwise, do not
contact me.

 

[J. Peter Mugaas]

I just tried the Indy SMTP, it worked fine on my local dev machine, but has
the same issue when I put it on the live server:

(IPs & Email have been changed)

2/23/2004 7:04:20 PM - Requested SMTP connection from 0.0.0.0 [0.0.0.0],
ID=31
2/23/2004 7:04:20 PM - ( 31) Connection from trusted IP address 0.0.0.0
2/23/2004 7:04:20 PM - ( 31) 220 ArGoSoft Mail Server Pro for
WinNT/2000/XP, Version 1.8 (1.8.5.0)

I did try to reproduce your problem but I couldn't. I was using Version
1.8 (1.8.5.2) Pro. I did find one bug with authentication when testing and
I just checked in a fix for that.

After another build is made, you probably do need to test with the updated
versiuon of ArgoSoft Mail Server Pro and see if that works as there
could've been a bug with that (I couldn't use the EXACT same version you
were using).

HTH.

--
J. Peter Mugaas - Indy Pit Crew
Internet Direct (Indy) Website - http://www.nevrona.com/Indy
Personal Home Page - http://www.wvnet.edu/~oma00215
If I want to do business with you, I will contact you. Otherwise, do not
contact me.