Following the example in the oSMTP.SendMessage() help topic, I made a little program for testing.

loSmtp.cContentType = "text/html"
loSmtp.cSubject = "Test Message with wwSMTP"
loSmtp.cMessage = "<b>Test message from wwsmtp, to check out how this operation works.</b>"

The destination email address (one of mine) is hosted on Network Solutions.

When sending the message via oSMTP.SendMail(), it works fine.
When sending the message via oSMTP.SendMessage(), the message is flagged as SPAM. There's something different about SendMessage() that flagged the message...

 (reason: 554 5.7.1 The message from (<support@mydomain.net>) with the subject of (Test Message with wwSMT...hes a profile the Internet community may consider spam. Please revise your message before resending.)

Any ideas ?

Thanks,
Carl

Assuming you're using the .NET component for both, the routines use the same code. The only difference is that you have to set up the connection yourself by calling Connect() explicitly. But you can see the code - it actually is practically identical and the underlying .NET code actually uses the same bits - ie. SendMail() calls into SendMessage() to send the email.

It'd be hard to debug this without some sort of trace to compare exactly what's going over the wire in the two versions. I suspect some setting might be different.

+++ Rick ---

After further testing with SendMessage(), it looks like it may be an issue with Network Solutions.
I can consistently send messages to my Yahoo account (no spam flags) but to my Network Solutions accounts, it's hit and miss - the identical message could be flagged as spam on one attempt and not be flagged on another. In some cases, it's slow getting to the inbox but eventually it does. And Yes, .nMailMode is set to 0.

Carl

Many ISPs have send limits where you can only send so many messages in a given time frame. If you're doing any sort of bulk sending this can have a big effect right away.

I don't think there's any difference in how messages are sent because as I mentioned SendMail() uses the same SendMessage() code to actually send the message (it just wraps the connection code around it for you).

+++ Rick ---

Hi Rick,

I wouldn't consider this bulk sending - 40 messages over a 1/2 hour period. But the problem wasn't with sending - it was with receiving. At no time was an error returned by wwSMTP.

Just testing with SendMessage() ONLY, not using SendMail() at all, the spam flags were still hit and miss. It could be that the spam flagging I described in the O/P with SendMessage() but not with SendMail() was just coincidental.

Carl

As a customer of Network Solutions, if you have a "Partner" account, I think the tech support people there will help you trace down the problem. Have you tried calling them to see what might be going on?

I don't use them for email but I know they have a really helpful group of support staff.

Thanks Harvey,

Yeah, I've found their support to be pretty good in the past as well.

Carl