>I am using Sergey's CDO 2000 email class.
>
>It's been working great.
>
>Friday, one of the user's had trouble sending out a proposal.
>I tested it on my machine and had the same problem.
>
>From within my Vfp application, I create a pdf package and email it.
>The email failed with the following error:
>
>1 ERROR: :1429 # send # 146
>The message could not be sent to the smtp server.
>The server response was not available.
>
>Do you know what the problem is?
>
>From what I've been told, the smtp server name, userid and password have not changed.
>Do I need to verify this?
>If so, how?
>
>Any help would be greatly appreciated.
>
>I'm using cdo2000.prg from 12/14/2009.

Can your user successfully send e-mail using a regular e-mail client such as Outlook? If so, that means their ISP's outgoing (SMTP) mail server is OK and there is some issue either with that user's PC or with your program's e-mail sending technique. If not, then something has changed with the SMTP server.

When you're testing, are you on the same network as the user who's having the problem, or at least using the same ISP? If you're not using the same ISP chances are your tests won't help diagnose the problem, because to reduce spam the vast majority of ISPs don't allow SMTP "relaying". For example:

- Suppose your user's ISP is yyy.com. Almost always, yyy.com will require that any outgoing mail messages be sent to their SMTP server, usually something like mail.yyy.com or smtp.yyy.com.

- Suppose you're using a different ISP, zzz.com. Likewise, your ISP will require that any e-mails you send go through their SMTP server e.g. mail.zzz.com or smtp.zzz.com.

- If, for test purposes, you try to send a mail and you've specified the SMTP server to be mail.yyy.com, then there are at least 2 chances it will get rejected:

- maybe immediately by zzz.com's SMTP server, which might refuse to relay it to yyy.com's SMTP server
- maybe by yyy.com's SMTP server, which may refuse to accept mail that has been relayed

In either case, you could get a misleading test failure.

Some more things worth checking:

- How large are any attachments that are being sent? For maximum reliability total attachment size should not exceed 3MB or so. In some cases you can get away with 5MB, and in a few special cases you might get 10MB or even more, but those are only with some ISPs and when sending strictly within the ISP i.e. from address1@bigemailisp.com to address2@bigemailisp.com.

- Most antivirus/Internet security suites these days include e-mail scanners, for both incoming and outgoing mail. If that's present, for test purposes try disabling at least the outgoing message scanning.