Hi there, if you see the the message a few times in the smtpserver.log then its not a problem in james..
About the message-id, yes it should be global unique and it "should" be in every message. See the rfc for more details: http://www.faqs.org/rfcs/rfc2822.html <- 3.6.4. Identification fields So you could try to check for the message-id and if you received the message already just set the state of the message to Mail.GHOST. An other idea would be to generate a md5 of the message and check if you have a match.. Bye, Norman 2010/7/19 Hillel <[email protected]>: > Hi, > > In the SMTP protocol when an email arrives does it always has a Message-ID? > Is the Message-ID always unique? > > We are having a problem with a customer that adamantly says they are sending > only one email to our JAMES 2.3.2 stable. > Our James smtpserver.log shows many duplicate emails from that customer. > If we look at the duplicate emails they all have the same Message-ID. > We don't know if the problem is with the client or somehow on James. > > So we are proposing to the client that we will save the Message-ID's from > the emails and if a new email comes in we will only process emails where the > Message-ID is unique and discard the rest. > > Have other James users tried this? > > Any suggestions appreciated. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
