Thanks for the reply. Unfortunately, none of the 'spammed' emails I have seen give any useful indication as to what triggered it, and I take your point about 'no universal guidelines'.
However, I was thinking along the lines of the fields that make up the TSmtpCli headers. The component has a number of properties, such as FromName, HdrFrom, HdrReplyTo etc. that are filled in before calling the methods which actually send the email. If, for instance, I try and send an email with almost none of the properties filled in, I get an error message saying 'incomplete header' so there are obviously some key fields, such as Host, without which the email cannot be sent. Which ones are mandatory seems a matter of trial and error, but certainly ones like HdrReplyTo appear optional. My understanding is that most anti-spam systems try to make sure that where the email actually came from is the same as where it says it came from and although I use this purely as an example, I could imagine that if you had different values for HdrReplyTo and HdrReturnPath, it might trigger anti-spam to reject it. Of course, every mail server handles mail differently and the trigger point for each anti-spam system is different, but there must be some basic ideas about which TSmtpCli properties should be filled in and the implications of how they are used? Tim -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of S.Korotky Sent: 10 May 2006 19:32 To: ICS support mailing Subject: Re: [twsocket] Emails treated as spam Dear Tim! You should obtain from the users, which reported the problem, all info about why the messages were treated as spam. As a rule, anti-spam software inserts descriptions of activated spam filters either in the message headers or in notifications about intercepted spam. Without this it is almost impossible to say what's the problem with these "false positives". Once the reason is discovered, you should see if it is related to something in the sending software (smtp client) or some external factors, which are out of your control. If the later is the case, there is no software decision. All you can do is to contact 3-d parties, which are involved in the mail trasmission and provoked the "false positives" due to their facilities setup. Of course, you have no guarantee they decided to accept your propositions. Generally speaking, there is no universal guidelines for creating correct e-mails. Spam detection is just a matter of filter setup, which is up to local administrator in a destination domain/mail server. [S]he may have a different opinion about proper spam detection. ----- Original Message ----- From: "Tim" <[EMAIL PROTECTED]> To: <twsocket@elists.org> Sent: Wednesday, May 10, 2006 8:05 PM Subject: [twsocket] Emails treated as spam > I have an email application which has been working well with ICS for some > while. However, the application is now sending via Exchange Server 2003 and > a number of recipients have said that the emails are being treated as spam. > All emails are being sent to addresses outside of the company. > > Of course, the Exchange Server may not be the problem as it seems many of > the recipients are now using Outlook 2003 which has it's own anti-spam > system built in. > > Are there some guidelines as to how to create an email using the TSmtpCli > and make sure it is treated correctly by mail servers and email clients? > > Thanks. > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be > -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
