Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Qmail: users

Strange Destination address is written in a mail header.

 

 

Qmail users RSS feed   Index | Next | Previous | View Threaded


Shuichi_Tsuda at NIandC

Nov 7, 2011, 9:34 PM

Post #1 of 5 (1468 views)
Permalink
Strange Destination address is written in a mail header.

Hi All,

I have used qmail(1.03),ucspi-tcp(0.88),qmail-ldap(1.03-20060201)
and there is no problem except for the fact
that some mail addressed to a mailing list has a strange header at a "for" atom
in Received field.

I think "for" should be followed by "Destination address"
same as "Delivered-To:" field.

Why is this happen ?

Could you tell me the way to make the two address same,
or the way to make the address after "for" not be displayed ?

Thank you.

//////////////////////for example//////////////////////

A mailing list "sender [at] xxxxxxxxx" contains the following.
AAA [at] xxxxxxxxx
BBB [at] xxxxxxxxx
CCC [at] xxxxxxxxx
DDD [at] xxxxxxxxx

When SMTP Server received the mail to "sender [at] xxxxxxxxx",
SMTP Server sends four mails (TO:AAA,BBB,CCC,DDD) in one session.
===see "Reference information" under.===


The mail header of each mail is the following.

To: AAA [at] xxxxxxxxx ( This header has no problem.)
------------------------------
Return-Path: <sender [at] xxxxxxxxx>
Delivered-To: AAA [at] xxxxxxxxx
Received: (qmail 27447 invoked from network); 5 Aug 2011 16:27:10 +0900
Received: from unknown (HELO SMTP-server.xxxxxxxxx.jp) ([10.105.50.50])
(envelope-sender <sender [at] xxxxxxxxx>)
by 0 (qmail-ldap-1.03) with SMTP
for <AAA [at] xxxxxxxxx>; 5 Aug 2011 16:27:10 +0900 '<-- Good
------------------------------

To: BBB [at] xxxxxxxxx ( strange header )
------------------------------
Return-Path: <sender [at] xxxxxxxxx>
Delivered-To: BBB [at] xxxxxxxxx
Received: (qmail 27447 invoked from network); 5 Aug 2011 16:27:10 +0900
Received: from unknown (HELO SMTP-server.xxxxxxxxx.jp) ([10.105.50.50])
(envelope-sender <sender [at] xxxxxxxxx>)
by 0 (qmail-ldap-1.03) with SMTP
for <AAA [at] xxxxxxxxx>; 5 Aug 2011 16:27:10 +0900 '<-- NG
------------------------------

To: CCC [at] xxxxxxxxx ( strange header )
------------------------------
Return-Path: <sender [at] xxxxxxxxx>
Delivered-To: CCC [at] xxxxxxxxx
Received: (qmail 27447 invoked from network); 5 Aug 2011 16:27:10 +0900
Received: from unknown (HELO SMTP-server.xxxxxxxxx.jp) ([10.105.50.50])
(envelope-sender <sender [at] xxxxxxxxx>)
by 0 (qmail-ldap-1.03) with SMTP
for <AAA [at] xxxxxxxxx>; 5 Aug 2011 16:27:10 +0900 '<-- NG
------------------------------

To: DDD [at] xxxxxxxxx ( strange header )
------------------------------
Return-Path: <sender [at] xxxxxxxxx>
Delivered-To: DDD [at] xxxxxxxxx
Received: (qmail 27447 invoked from network); 5 Aug 2011 16:27:10 +0900
Received: from unknown (HELO SMTP-server.xxxxxxxxx.jp) ([10.105.50.50])
(envelope-sender <sender [at] xxxxxxxxx>)
by 0 (qmail-ldap-1.03) with SMTP
for <AAA [at] xxxxxxxxx>; 5 Aug 2011 16:27:10 +0900 '<-- NG
------------------------------



Reference information;

The mails above were sent in one session.
The following is the maillog on a SMTP server.
I judged it from the message "qp 27447 by POP-server".
(In four mails under, qmail process ID is same.)
------------------------------
Aug 5 16:27:09 SMTP-server postfix/smtpd[25479]: E221A2D003F: \
client=SMTP-server[127.0.0.1]
Aug 5 16:27:10 SMTP-server postfix/cleanup[25586]: E221A2D003F: \
message-id=<91D828C2465F49F5986AB76BE6F1F1FA [at] JPEXINTRA0>
Aug 5 16:27:10 SMTP-server postfix/smtp[25249]: D2C842D003E: to=<AAA [at] xxxxxxxxx>, \
orig_to=<mailing-list [at] xxxxxxxxx>, relay=localhost[127.0.0.1]:10025, delay=0.17, \
delays=0.03/0/0.03/0.1, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued \
as E221A2D003F)
Aug 5 16:27:10 SMTP-server postfix/smtp[25249]: D2C842D003E: to=<BBB [at] xxxxxxxxx>, \
orig_to=<mailing-list [at] xxxxxxxxx>, relay=localhost[127.0.0.1]:10025, delay=0.17, \
delays=0.03/0/0.03/0.1, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued \
as E221A2D003F)
Aug 5 16:27:10 SMTP-server postfix/qmgr[6368]: E221A2D003F: \
from=<sender [at] xxxxxxxxx>, size=1957, nrcpt=4 (queue active)
Aug 5 16:27:10 SMTP-server postfix/smtp[25249]: D2C842D003E: to=<CCC [at] xxxxxxxxx>, \
orig_to=<mailing-list [at] xxxxxxxxx>, relay=localhost[127.0.0.1]:10025, delay=0.17, \
delays=0.03/0/0.03/0.1, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued \
as E221A2D003F)
Aug 5 16:27:10 SMTP-server postfix/smtp[25249]: D2C842D003E: to=<DDD [at] xxxxxxxxx>, \
orig_to=<mailing-list [at] xxxxxxxxx>, relay=localhost[127.0.0.1]:10025, delay=0.17, \
delays=0.03/0/0.03/0.1, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued \
as E221A2D003F)
Aug 5 16:27:10 SMTP-server postfix/smtpd[25479]: disconnect from \
SMTP-server[127.0.0.1]
Aug 5 16:27:10 SMTP-server postfix/qmgr[6368]: D2C842D003E: removed
Aug 5 16:27:10 SMTP-server postfix/smtp[24928]: E221A2D003F: to=<AAA [at] xxxxxxxxx>, \
relay=10.105.50.17[10.105.50.17]:25, delay=0.11, delays=0.1/0.01/0/0, dsn=2.0.0, \
status=sent (250 ok 1312529230 qp 27447 by POP-server.xxxxxxxxx.jp)
Aug 5 16:27:10 SMTP-server postfix/smtp[24928]: E221A2D003F: to=<BBB [at] xxxxxxxxx>, \
relay=10.105.50.17[10.105.50.17]:25, delay=0.11, delays=0.1/0.01/0/0, dsn=2.0.0, \
status=sent (250 ok 1312529230 qp 27447 by POP-server.xxxxxxxxx.jp)
Aug 5 16:27:10 SMTP-server postfix/smtp[24928]: E221A2D003F: to=<CCC [at] xxxxxxxxx>, \
relay=10.105.50.17[10.105.50.17]:25, delay=0.11, delays=0.1/0.01/0/0, dsn=2.0.0, \
status=sent (250 ok 1312529230 qp 27447 by POP-server.xxxxxxxxx.jp)
Aug 5 16:27:10 SMTP-server postfix/smtp[24928]: E221A2D003F: to=<DDD [at] xxxxxxxxx>, \
relay=10.105.50.17[10.105.50.17]:25, delay=0.11, delays=0.1/0.01/0/0, dsn=2.0.0, \
status=sent (250 ok 1312529230 qp 27447 by POP-server.xxxxxxxxx.jp)
Aug 5 16:27:10 SMTP-server postfix/qmgr[6368]: E221A2D003F: removed
------------------------------


rwolfe at fpsoft

Nov 9, 2011, 5:53 AM

Post #2 of 5 (1326 views)
Permalink
Re: Strange Destination address is written in a mail header. [In reply to]

On 08.11.2011 00:34, Shuichi_Tsuda [at] NIandC wrote:

> Hi All,
>
> I have used qmail(1.03),ucspi-tcp(0.88),qmail-ldap(1.03-20060201)
> and there is no problem except for the fact
> that some mail addressed to a mailing list has a strange header at a
> "for" atom
> in Received field.
>
> I think "for" should be followed by "Destination address"
> same as "Delivered-To:" field.
>
> Why is this happen ?

Are these for emails going to different domains? What does the
official RFC say about this? I believe qmail follows the SMTP RFCs as
close as possible. As a sidenote, the way I see it is if it's working
as it should, then why worry about it? *smiles*


ar-djblists at acrconsulting

Nov 9, 2011, 9:35 AM

Post #3 of 5 (1328 views)
Permalink
Re: Strange Destination address is written in a mail header. [In reply to]

On Tuesday 08 November 2011 05:34:18 Shuichi_Tsuda [at] niandc wrote:
> Hi All,
>
> I have used qmail(1.03),ucspi-tcp(0.88),qmail-ldap(1.03-20060201)
> and there is no problem except for the fact
> that some mail addressed to a mailing list has a strange header at a "for"
> atom in Received field.
>
> I think "for" should be followed by "Destination address"
> same as "Delivered-To:" field.
>
> Why is this happen ?
>
> Could you tell me the way to make the two address same,
> or the way to make the address after "for" not be displayed ?
>
> Thank you.

The issue you describe looks to be specific to qmail-ldap. Simulating the same
scenario in netqmail (likely to have the same result as vanilla qmail too),
the netqmail headers do not have a 'for <name [at] domai>' component, so this
looks to be a feature introduced with qmail-ldap that adds the subtle issue
you have discovered at the same time.

I suspect the reason is that qmail-smtpd writes the Received: header when it
records the message in the queue, where the message is stored once for all
local recipients [also once for all remote recipients], such as your 4 example
recipients; just one of these recipients is used for the 'for' value. Later
this single message/file is split into separate deliveries.

If you haven't already done so you may also wish to explore this on the qmail-
ldap mailing list (see http://www.nrg4u.com/)

Best regards,

Andrew Richards.
--
====================================================================
* Custom email solutions * Systems Administration * Networking
http://www.acrconsulting.co.uk/email/qmail.html
====================================================================


Shuichi_Tsuda at NIandC

Nov 10, 2011, 4:27 AM

Post #4 of 5 (1322 views)
Permalink
Re: Strange Destination address is written in a mail header. [In reply to]

> Are these for emails going to different domains? What does the
> official RFC say about this? I believe qmail follows the SMTP RFCs as
> close as possible. As a sidenote, the way I see it is if it's working
> as it should, then why worry about it? *smiles*

Hi Robert

The all emails goes to same domeain.

RFC 2821 says,
--------------
4.4 Trace Information

The FOR field MAY contain a list of <path> entries when multiple
RCPT commands have been given. This may raise some security
issues and is usually not desirable; see section 7.2.
--------------

I'm afraid that the motion in this time at a "for" atom is not recommened.

Thank you !


Shuichi_Tsuda at NIandC

Nov 10, 2011, 5:09 AM

Post #5 of 5 (1336 views)
Permalink
Re: Strange Destination address is written in a mail header. [In reply to]

"Andrew Richards" <ar-djblists [at] acrconsulting> wrote on 2011/11/10 02:35:13:
> On Tuesday 08 November 2011 05:34:18 Shuichi_Tsuda [at] niandc wrote:
> > Hi All,
> >
> > I have used qmail(1.03),ucspi-tcp(0.88),qmail-ldap(1.03-20060201)
> > and there is no problem except for the fact
> > that some mail addressed to a mailing list has a strange header at a "for"
> > atom in Received field.
> >
> > I think "for" should be followed by "Destination address"
> > same as "Delivered-To:" field.
> >
> > Why is this happen ?
> >
> > Could you tell me the way to make the two address same,
> > or the way to make the address after "for" not be displayed ?
> >
> > Thank you.
>
> The issue you describe looks to be specific to qmail-ldap.
> Simulating the same
> scenario in netqmail (likely to have the same result as vanilla qmail too),
> the netqmail headers do not have a 'for <name [at] domai>' component, so this
> looks to be a feature introduced with qmail-ldap that adds the subtle issue
> you have discovered at the same time.
>
> I suspect the reason is that qmail-smtpd writes the Received: header when it
> records the message in the queue, where the message is stored once for all
> local recipients [also once for all remote recipients], such as your4 example
> recipients; just one of these recipients is used for the 'for' value. Later
> this single message/file is split into separate deliveries.
>
> If you haven't already done so you may also wish to explore this on the qmail-
> ldap mailing list (see http://www.nrg4u.com/)
>
> Best regards,
>
> Andrew Richards.
> --

Hi Andrew

I think so too that the reason is in a qmail-smtpd with qmail-ldap.
So I asked to qmail-ldap mailing list before, but I received no solution.
http://marc.info/?l=qmail-ldap&m=131660959918429&w=2

Thank you !

Shuichi Tsuda

Qmail users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.