You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2021/09/09 10:46:00 UTC
[jira] [Commented] (JAMES-3648) RSET do not impact ESMTP ID in
Received header
[ https://issues.apache.org/jira/browse/JAMES-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412506#comment-17412506 ]
Benoit Tellier commented on JAMES-3648:
---------------------------------------
RFC-822 states https://datatracker.ietf.org/doc/html/rfc822#section-4.3.2 :
{code:java}
Some transport services queue mail; the internal message iden-
tifier that is assigned to the message may be noted, using the
"id" parameter.
{code}
https://datatracker.ietf.org/doc/html/rfc5321#section-4.4 defines it as:
{code:java}
o The ID clause MAY contain an "@" as suggested in RFC 822, but this
is not required.
{code}
Which is not enough to get a clear understanding of the expectations...
> RSET do not impact ESMTP ID in Received header
> ----------------------------------------------
>
> Key: JAMES-3648
> URL: https://issues.apache.org/jira/browse/JAMES-3648
> Project: James Server
> Issue Type: Bug
> Components: SMTPServer
> Affects Versions: 3.6.0
> Reporter: Benoit Tellier
> Priority: Major
>
> The ESMTP ID is correlated to the channel number thus sending two mails with a RSET in between result in the same ESMTP ID in the received log.
> Here is such an example using telnet:
> {code:java}
> $ telnet 172.17.0.2 25
> Trying 172.17.0.2...
> Connected to 172.17.0.2.
> Escape character is '^]'.
> 220 Apache JAMES awesome SMTP Server
> ehlo other.com
> 250-880f224968ec Hello other.com [172.17.0.1])
> 250-PIPELINING
> 250-ENHANCEDSTATUSCODES
> 250 8BITMIME
> mail from: <al...@other.com>
> 250 2.1.0 Sender <al...@other.com> OK
> rcpt to: <bo...@localhost>
> 250 2.1.5 Recipient <bo...@localhost> OK
> data
> 354 Ok Send data ending with <CRLF>.<CRLF>
> .
> 250 2.6.0 Message received
> rset
> 250 2.0.0 OK
> ehlo other.com
> 250-880f224968ec Hello other.com [172.17.0.1])
> 250-PIPELINING
> 250-ENHANCEDSTATUSCODES
> 250 8BITMIME
> mail from: <al...@other.com>
> 250 2.1.0 Sender <al...@other.com> OK
> rcpt to: <bo...@localhost>
> 250 2.1.5 Recipient <bo...@localhost> OK
> data
> 354 Ok Send data ending with <CRLF>.<CRLF>
> Subject: 2
> .
> 250 2.6.0 Message received
> quit
> 221 2.0.0 880f224968ec Service closing transmission channel
> Connection closed by foreign host.
> {code}
> It result in duplicated Received ESMTP ID being stored:
> {code:java}
> retr 4
> +OK Message follows
> Return-Path: <al...@other.com>
> Delivered-To: bob@localhost
> Received: from 172.17.0.1 (EHLO other.com) ([172.17.0.1])
> by 880f224968ec (JAMES SMTP Server ) with ESMTP ID 1194716406
> for <bo...@localhost>;
> Thu, 09 Sep 2021 09:42:32 +0000 (UTC)
> .
> retr 5
> +OK Message follows
> Return-Path: <al...@other.com>
> Delivered-To: bob@localhost
> Received: from 172.17.0.1 (EHLO other.com) ([172.17.0.1])
> by 880f224968ec (JAMES SMTP Server ) with ESMTP ID 1194716406
> for <bo...@localhost>;
> Thu, 09 Sep 2021 09:42:57 +0000 (UTC)
> Subject: 2
> .
> {code}
> I do not have at hand specifications and expectations for that ESMTP ID.
> We maybe rather look at what Postfix does.
> I do not know ifit need to be unique on a per-mail bases.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org