Re: non-existent msgids & duplicate delivery suppression

2003-06-27 Thread adi
On Fri, Jun 27, 2003 at 03:10:47PM +0200, Sebastian Hagedorn wrote:
> Every MTA along the way should add a message-id if there isn't one.

qmail don't add message-id for any messages that comes through
smtp (qmail-smtpd).

Regards,

P.Y. Adi Prasaja


Re: non-existent msgids & duplicate delivery suppression

2003-06-27 Thread Stephen Grier
On Fri, 2003-06-27 at 16:48, Rob Siemborski wrote:
> On Fri, 27 Jun 2003, Stephen Grier wrote:
> 
> > We use Exim here. The messages do have a Message-Id: header, but with an
> > empty value. I assume Exim will not add or alter the msg-id in this
> > case.
> 
> Any idea why this one user is getting a bunch of messages like this, or
> what might be generating them?  That's probably what wants to be fixed.

There are a number of users receiving messages of this sort, but one
domain in particular from which they originate. I've assumed it's a
problem with their MTA, and have contacted them about it, but it could
also be a broken client, Lotus Notes 5.0.8 according to the X-Mailer:
header.

-- 

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




Re: non-existent msgids & duplicate delivery suppression

2003-06-27 Thread Phil Chambers

On Fri, 27 Jun 2003 16:52:02 +0100 (BST) David Carter <[EMAIL PROTECTED]> wrote:

> On Fri, 27 Jun 2003, Stephen Grier wrote:
> 
> > We use Exim here. The messages do have a Message-Id: header, but with an
> > empty value.
> 
> Eeep. That's no fun at all.
> 
> > I assume Exim will not add or alter the msg-id in this case.
> 
> I suspect this is the case, though arguably Exim should do something about
> this case. I'll have a chat with Philip the next time that I see him.
> 

Exim can be made to replace a blank message-id with a good one.  Alternatively, if 
you switch on strict header testing it should reject the message because a blank 
message-id does not conform to the header syntax.

Replacing the header will depend on the version of exim.  With exim-4, in the 
relevant transport you could have a headers_remove line which is conditional on the 
message-id being blank, then have a headers_add line, similarly conditional.

I am not an expert, but a message to [EMAIL PROTECTED] should give a detailed 
solution (be sure to say what version of exim you have: "exim -bV" will give it).

Phil.
---
Phil Chambers ([EMAIL PROTECTED])
University of Exeter



Re: non-existent msgids & duplicate delivery suppression

2003-06-27 Thread Henrique de Moraes Holschuh
On Fri, 27 Jun 2003, Stephen Grier wrote:
> Yes, the messages do have a Message-Id: header with an empty value. I've
> identified 2 domains which appear to be doing this.
> 
> Would it be reasonable to have lmtpd not add an entry to the deliver db
> for zero-length message-ids?

It would be reasonable for lmtpd to reject delivering such crap with a 5xx
error.  Empty message-id are NOT acceptable anywhere in the email
transmission chain.

-- 
  "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


Re: non-existent msgids & duplicate delivery suppression

2003-06-27 Thread Rob Siemborski
On Fri, 27 Jun 2003, Stephen Grier wrote:

> We use Exim here. The messages do have a Message-Id: header, but with an
> empty value. I assume Exim will not add or alter the msg-id in this
> case.

Any idea why this one user is getting a bunch of messages like this, or
what might be generating them?  That's probably what wants to be fixed.

-Rob

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456
Research Systems Programmer * /usr/contributed Gatekeeper



Re: non-existent msgids & duplicate delivery suppression

2003-06-27 Thread David Carter
On Fri, 27 Jun 2003, Stephen Grier wrote:

> We use Exim here. The messages do have a Message-Id: header, but with an
> empty value.

Eeep. That's no fun at all.

> I assume Exim will not add or alter the msg-id in this case.

I suspect this is the case, though arguably Exim should do something about
this case. I'll have a chat with Philip the next time that I see him.

-- 
David Carter Email: [EMAIL PROTECTED]
University Computing Service,Phone: (01223) 334502
New Museums Site, Pembroke Street,   Fax:   (01223) 334679
Cambridge UK. CB2 3QH.


Re: non-existent msgids & duplicate delivery suppression

2003-06-27 Thread Stephen Grier
On Fri, 2003-06-27 at 14:27, David Carter wrote:
> On Fri, 27 Jun 2003, Stephen Grier wrote:
> 
> > I have noticed that this has been happening on other occasions, where
> > lmtpd does a duplicate_check and then a duplicate_mark on zero length
> > message-ids. This raises the possibility that the server is suppressing
> > messages that are not duplicates, but merely have no message-id header.
> >
> > Has anyone else seen this happening?. If this continues to happen we may
> > have to disable duplicate delivery suppression.
> 
> This seems quite likely. If a message doesn't contain a Message-ID, your
> mail system should really add one before it passes it on to Cyrus.
> 
> Exim does this automatically. I don't know about other MTAs.

We use Exim here. The messages do have a Message-Id: header, but with an
empty value. I assume Exim will not add or alter the msg-id in this
case.

-- 

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




Re: non-existent msgids & duplicate delivery suppression

2003-06-27 Thread Stephen Grier
On Fri, 2003-06-27 at 14:10, Sebastian Hagedorn wrote:
> -- Stephen Grier <[EMAIL PROTECTED]> is rumored to have mumbled on 
> Freitag, 27. Juni 2003 13:47 Uhr +0100 regarding non-existent msgids & 
> duplicate delivery suppression:
> 
> > I have noticed that this has been happening on other occasions, where
> > lmtpd does a duplicate_check and then a duplicate_mark on zero length
> > message-ids. This raises the possibility that the server is suppressing
> > messages that are not duplicates, but merely have no message-id header.
> 
> That in itself is very weird. Every MTA along the way should add a 
> message-id if there isn't one. Or are you saying there *is* a message-id, 
> but it's empty? That would be horribly broken, but might explain why one 
> isn't added by the MTAs ...

Yes, the messages do have a Message-Id: header with an empty value. I've
identified 2 domains which appear to be doing this.

Would it be reasonable to have lmtpd not add an entry to the deliver db
for zero-length message-ids?

-- 

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




Re: non-existent msgids & duplicate delivery suppression

2003-06-27 Thread David Carter
On Fri, 27 Jun 2003, Stephen Grier wrote:

> I have noticed that this has been happening on other occasions, where
> lmtpd does a duplicate_check and then a duplicate_mark on zero length
> message-ids. This raises the possibility that the server is suppressing
> messages that are not duplicates, but merely have no message-id header.
>
> Has anyone else seen this happening?. If this continues to happen we may
> have to disable duplicate delivery suppression.

This seems quite likely. If a message doesn't contain a Message-ID, your
mail system should really add one before it passes it on to Cyrus.

Exim does this automatically. I don't know about other MTAs.

-- 
David Carter Email: [EMAIL PROTECTED]
University Computing Service,Phone: (01223) 334502
New Museums Site, Pembroke Street,   Fax:   (01223) 334679
Cambridge UK. CB2 3QH.


Re: non-existent msgids & duplicate delivery suppression

2003-06-27 Thread Sebastian Hagedorn
-- Stephen Grier <[EMAIL PROTECTED]> is rumored to have mumbled on 
Freitag, 27. Juni 2003 13:47 Uhr +0100 regarding non-existent msgids & 
duplicate delivery suppression:

I have noticed that this has been happening on other occasions, where
lmtpd does a duplicate_check and then a duplicate_mark on zero length
message-ids. This raises the possibility that the server is suppressing
messages that are not duplicates, but merely have no message-id header.
That in itself is very weird. Every MTA along the way should add a 
message-id if there isn't one. Or are you saying there *is* a message-id, 
but it's empty? That would be horribly broken, but might explain why one 
isn't added by the MTAs ...
--
Sebastian Hagedorn M.A. - RZKR-R1 (Flachbau), Zi. 18, Robert-Koch-Str. 10
Zentrum für angewandte Informatik - Universitätsweiter Service RRZK
Universität zu Köln / Cologne University - Tel. +49-221-478-5587



non-existent msgids & duplicate delivery suppression

2003-06-27 Thread Stephen Grier
Hi,

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

One of our users complained that they were not receiving their mail.
Having looked at the logs I noticed a string of entries like the
following:

Jun 25 13:11:43 machine lmtpd[18521]:
duplicate_check: 
user.X  1056537904
Jun 25 13:11:43 machine lmtpd[18521]: dupelim: eliminated duplicate
message to user.X id

Notice that the message-id is missing. The entries correspond to mail
sent by the same sender which do not contain a message-id header. It
appears that lmtpd has been suppressing mail from this sender, because
it assumes that all mail with a zero length message-id is a duplicate of
the last.

I have noticed that this has been happening on other occasions, where
lmtpd does a duplicate_check and then a duplicate_mark on zero length
message-ids. This raises the possibility that the server is suppressing
messages that are not duplicates, but merely have no message-id header.

Has anyone else seen this happening?. If this continues to happen we may
have to disable duplicate delivery suppression.

Thanks

-- 

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