Duplicate emails coming in

[boomschtick]

I have been getting quite a few duplicate messages in my inbox. The fact that the mail account name is being incremented, It seems to be something to do with SpamGourmet.com. These are all XOXY.NET addresses.

Here are a couple of dupes title lines.

New Issue Of Best Magazine - Available Online (BESTBUY: message 3 of 10)
New Issue Of Best Magazine - Available Online (BESTBUY: message 3 of 10) (BESTBUY: message 4 of 10)
Kingston Email Notification (FRYS: message 9 of 10)
Kingston Email Notification (FRYS: message 8 of 10)

[josh]

apologies -- this one is killing me. It's not all the messages, right?

[boomschtick]

apologies -- this one is killing me. It's not all the messages, right?

Nope... seems to be fairly random.

[boomschtick]

apologies -- this one is killing me. It's not all the messages, right?

Got some more today:

This Summer Only - Member Exclusive (BESTBUY: message 5 of 10)
This Summer Only - Member Exclusive (BESTBUY: message 5 of 10) (BESTBUY: message 6 of 10)

[sugar]

I'm experiencing the same thing - sent a test msg to myself and got two forwarded:

test (mLife: message 1 of 20)
test (mLife: message 1 of 20) (mlife: message 2 of 20)

Please fix thanks!

[jgombos]

Is it just xoxy.net messages that experience this?

[sugar]

um... not sure what xoxy.net is, but this odd duplication only seems to occur for one of my spamgourmet addresses. my other SG addresses seem to be working/forwarding/counting fine...

test2 (mLife: message 3 of 20)
test2 (mLife: message 3 of 20) (mlife: message 4 of 20)

[josh]

OK - I've seen two patterns that could cause this -- when a message has the same disposable address in two different places in the headers (for instance in the To: and in the "delivered to" that's derived from the BCC, etc.) and the sender used different case (such as all caps on one, but not the other), the code was treating that as two different addresses, each of which needed to be handled separately. I think I fixed that by setting the code to ignore case.

The other is when the sender uses two different alternative domains (such as spamgourmet.com and xoxy.net) for recipients, but both resolve to the same disposable address (eg, test.user@spamgourmet.com and test.user@xoxy.net) -- I haven't handled this one yet.

Josh

[sugar]

I re-read the FAQs.. had forgotten there are other acceptable domains like xoxy.net etc ...

I've only been using the spamgourmet.com domain. So it appears that the first pattern you mentioned was the culprit - for me at least.

Thanks for the quick response and the fix!