Hello,
I can reproduce this. My workaround is to delete the email manually right now. This is happening in testing with just a couple of people sending emails back and fort. I am a little afraid to go to production with it.

Below is the header of one of the messages that had problems.

-Alex


Microsoft Mail Internet Headers Version 2.0
Received: from webaccess.egenera.com ([63.139.209.15]) by bart.corp.egenera.com with Microsoft SMTPSVC(6.0.3790.3959);
Tue, 15 Jul 2008 10:48:19 -0400
Received: from psmtp.com ([64.18.3.101]) by webaccess.egenera.com with Microsoft SMTPSVC(6.0.3790.3959);
Tue, 15 Jul 2008 10:49:03 -0400
Received: from source ([216.235.242.184]) (using TLSv1) by exprod8mx201.postini.com ([64.18.7.10]) with SMTP;
Tue, 15 Jul 2008 09:47:26 CDT
Received: from smithers.egenera.com (localhost.localdomain [127.0.0.1])
by smithers.egenera.com (8.13.1/8.13.1) with ESMTP id m6FElKl4024458
for <xxxxxxx@egenera.com>; Tue, 15 Jul 2008 10:47:20 -0400
Received: (from apache@localhost)
by smithers.egenera.com (8.13.1/8.13.1/Submit) id m6FElKxl024457;
Tue, 15 Jul 2008 10:47:20 -0400
To: xxxxxxx@egenera.com
Subject: RE: [SE FAQ & Tech Talk-t-375] 4 of 5 Dentists Recommend Bob
Date: Tue, 15 Jul 2008 10:47:17 -0400
From: Rhart <xxxxxxx@egenera.com>
Reply-To: XXXXXX@egenera.com
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
Message-Id: <375.640@emailintegration>
References: <375.635@emailintegration>
X-Priority: 3
X-Mailer: vBulletin Mail via PHP
Return-Path: apache@smithers.egenera.com
X-OriginalArrivalTime: 15 Jul 2008 14:49:03.0596 (UTC) FILETIME=[ECB08AC0:01C8E689]
X-EsetId: 58762D24FC8B26310D36

Try turning off strict email checking and let me know please if it still sticks. :)

Hello,
How do I turn that off ?

Also,
Would it help if I was able to access bart.corp.egenera.com directly instead of going through webaccess.egenera.com? I am not even sure if IT will allow that but if that is a workaround, I can always ask them.

Thanks,
Alex

We just started using this today on a new forum and one of the first responses to a thread by email kept coming through again and again - 15 times before I changed the user's status so they could no longer respond by email and then it stopped.

I'm guessing that the user's mail server did not recognise that the message had been received and just kept re-sending it.

Is there a way to prevent this from happening? (because it's a sure fire way to upset users quickly if they get the same email 15 times!)

We really need a means to detect and block identical posts.

Kevin,
I believe the reason the Email is being re-sent is that it is not being deleted from the IMAP/POP3 server after it is read. As such, every time the pHp cron activates the module to fetch mail from the IMAP/POP3 server, it fetches the same mail over and over again. In fact, if you look at the thread in the forum portal, you will see the reply is being posted multiple times. Cyricx who developed this module is aware of the problem. I have asked him a couple of questions above to find a quick workaround while he can perhaps rebuild the code.

We cannot use this feature on a large scale right now. It would be an administrative nightmare to troubleshoot.

-Alex

Thanks for this Alex. The post was indeed posted multiple time in the web view of the forum. Sadly this makes EI unusable for us until this is resolved, because it has the capacity to upset lots of users very quickly :)

Is it possible to simply disable email replies but retain the email notifications of new posts?

I set 'Strict Email Checking' to 'NO'.
I am testing now. I will send an update as soon as I have some results.

-Alex

That did not help.

I wonder if it would help if I used a different mail server or switch from IMAP to POP3.
Any ideas ?

Will keep you updated...