Re: read-receipts & duplicate delivery suppression

2003-06-12 Thread Henrique de Moraes Holschuh
On Thu, 12 Jun 2003, Stephen Grier wrote:
> third party returned the read-receipt. It seems that when the third
> party then replied to the original message, lmtpd suppressed it because
> it contained a message-id identical to the one on the read-receipt sent

[...]

> non-standard, so I don't know if the client which did this, MS Outlook,
> Build 10.0.3416, behaved sensibly or not. We may have to disable
> duplicate delivery suppression if this is likely to happen again.

Disable MS Outlook Build 10.0.3416 instead.  Duplicating msgids is
EXTREMELY unacceptable.  Or you could tell your MTA to kill all msgids
coming from MS Outlook Build 10.0.3416 and regen it.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


read-receipts & duplicate delivery suppression

2003-06-12 Thread Stephen Grier
Hi,

We're currently running cyrus-imapd-2.1.11 with duplicate delivery
suppression enabled.

We recently received a complaint from a user who reported not receiving
a message he was sent. On investigation, it seems that he initially sent
a message to a third party along with a request for a read-receipt. The
third party returned the read-receipt. It seems that when the third
party then replied to the original message, lmtpd suppressed it because
it contained a message-id identical to the one on the read-receipt sent
earlier:

Jun 10 15:23:31 machine lmtpd[15702]: duplicate_check:
<[EMAIL PROTECTED]> user.XX 0
Jun 10 15:23:31 machine lmtpd[15702]: duplicate_mark:
<[EMAIL PROTECTED]> user.XX 1055255011
...
Jun 10 15:56:45 machine lmtpd[17525]: duplicate_check:
<[EMAIL PROTECTED]> user.XX 1055255011
Jun 10 15:56:45 machine lmtpd[17525]: dupelim: eliminated duplicate
message to user.XX

Has anyone else observed this happening? As far as I understand rfc-822
message-ids are supposed to be unique, but read-receipts are
non-standard, so I don't know if the client which did this, MS Outlook,
Build 10.0.3416, behaved sensibly or not. We may have to disable
duplicate delivery suppression if this is likely to happen again.

Thanks

-- 

Stephen Grier
Systems Developer
Computing Services
Queen Mary, University of London