A NOTE has been added to this issue.
======================================================================
http://www.dbmail.org/mantis/view.php?id=435
======================================================================
Reported By: bjohnson
Assigned To:
======================================================================
Project: DBMail
Issue ID: 435
Category: LMTP daemon
Reproducibility: always
Severity: minor
Priority: normal
Status: new
target:
======================================================================
Date Submitted: 03-Nov-06 22:26 CET
Last Modified: 06-Nov-06 23:11 CET
======================================================================
Summary: dbmail-lmtp rejects mail from supposedly valid
address
Description:
Version: 2.2 branch current SVN
dbmail-lmtp rejects mail that has made it through the entire delivery
chain (postfix,amavis,spamassassin,tmda). I don't know if this address is
legal or not, but I suspect it is as no other program has complained about
it thus far.
C19FF938BB4 4910 Fri Nov 3 14:31:31 "dr."@feminine-attraction.com
(host 127.0.0.1[127.0.0.1] said: 500 No address found. (in reply to MAIL
FROM command))
[EMAIL PROTECTED]
Here are a few others:
"k..am--hw"@magentawall.com
"qbdd2hc.."@monetlily.com
"GovSearchAsst."@helpfulbuddiez.com
======================================================================
----------------------------------------------------------------------
jasb - 04-Nov-06 00:52
----------------------------------------------------------------------
I've posted something to the mailling list that may be related to this.
I just can't receive emails on users that have sieve scripts with the last
2.2 branch with libsieve 2.2.1.
I resolved moving back to libsieve 2.1.13.
----------------------------------------------------------------------
bjohnson - 04-Nov-06 01:55
----------------------------------------------------------------------
These errors were running with libsieve 2.1.13.
----------------------------------------------------------------------
aaron - 04-Nov-06 02:03
----------------------------------------------------------------------
If its a problem with a particular script, please post the script.
Please also try with and without an active script to narrow the issue down
from the general delivery chain to the Sieve sorting specifically.
----------------------------------------------------------------------
bjohnson - 04-Nov-06 03:19
----------------------------------------------------------------------
There are no users on this system with an active sieve script.
----------------------------------------------------------------------
aaron - 04-Nov-06 23:55
----------------------------------------------------------------------
The issue is that the double quote (") is not a valid character for LMTP. I
can add quotes to the valid chars, but it's not going to help with user
deliveries because we don't currently do any de-quoting of the strings.
The messages will be delivered successfully to domain catch all mailboxes,
though.
Would someone please tell me how libSieve has anything to do with this
bug?
----------------------------------------------------------------------
bjohnson - 05-Nov-06 10:43
----------------------------------------------------------------------
> The issue is that the double quote (") is not a valid character for
LMTP.
Are you saying that SMTP can accept email addresses that LMTP doesn't
accept standards-wise? Or that this is a limitation of the dbmail LMTP?
As I read it (and I could be wrong), RFC 2821 allows for quoted local-part
addresses (section 4.1.2). If I'm right, that would explain why nothing
else in the delivery chain barfed until it hit dbmail-lmtp.
> Would someone please tell me how libSieve has anything to do with this
bug?
jasb is having a similar problem related to libsieve. This bug is not the
same.
----------------------------------------------------------------------
aaron - 05-Nov-06 17:35
----------------------------------------------------------------------
Right, I am going to make the validchars a little more lenient to comply
with the RFC which allows these additional characters. I haven't committed
the changes yet; later today!
----------------------------------------------------------------------
paul - 06-Nov-06 23:11
----------------------------------------------------------------------
Aaron,
I believe this is in already, correct?
Issue History
Date Modified Username Field Change
======================================================================
03-Nov-06 22:26 bjohnson New Issue
04-Nov-06 00:51 jasb Issue Monitored: jasb
04-Nov-06 00:52 jasb Note Added: 0001522
04-Nov-06 01:55 bjohnson Note Added: 0001523
04-Nov-06 02:03 aaron Note Added: 0001524
04-Nov-06 03:19 bjohnson Note Added: 0001525
04-Nov-06 23:55 aaron Note Added: 0001530
05-Nov-06 10:43 bjohnson Note Added: 0001533
05-Nov-06 17:35 aaron Note Added: 0001537
06-Nov-06 23:11 paul Note Added: 0001545
======================================================================
