Re: AW: AW: HMM got lmtp dupicate entries HOW and WHY?

John Fawcett wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Peter Rabbitson wrote:
> 
>> Ah, I just wrote about this in another message. So
to confirm - when
>> displaying in a MUA a message retrieved from
dbmail, I see no return
>> path header (unless I add it at my MTA).
> 
> Peter
> that's exactly what I get.
> 
> However, if I do a select on dbmail_headervalues table,
I find the
> Return-PAth value stored there.
> 
> I'm not sure where MUAs are expecting to get this,
> from the message header or from the imap server
directly, but I
> think it should go into the message header too.
> 

So what is the verdict on this? Should I be adding a RP just
before handing 
email to dbmail, or should dbmail append it both in the
headers and 
physmessage, or does it matter at all?
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Rabbitson wrote:
> John Fawcett wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Peter Rabbitson wrote:
>>
>>> Ah, I just wrote about this in another message.
So to confirm - when
>>> displaying in a MUA a message retrieved from
dbmail, I see no return
>>> path header (unless I add it at my MTA).
>>
>> Peter
>> that's exactly what I get.
>>
>> However, if I do a select on dbmail_headervalues
table, I find the
>> Return-PAth value stored there.
>>
>> I'm not sure where MUAs are expecting to get this,
>> from the message header or from the imap server
directly, but I
>> think it should go into the message header too.
>>
> 
> So what is the verdict on this? Should I be adding a RP
just before
> handing email to dbmail, or should dbmail append it
both in the headers
> and physmessage, or does it matter at all?

with the patch applied I could not find issues whether you
add
RP in the MTA or not.

If passing messages via LMTP, I would not add a
RP in the MTA since dbmail gets this from the LMTP
envelope sender which is the most reliable place.

If passing messages via dbmail-smtp, I would specify the -r
$
flag to ensure that this is the header that is used rather
than any
pre-existing one, which may be forged.

John
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org


iD8DBQFHzs19d4I3jTtt9EIRApNPAKCuv0oPrrKSoeQNjc7vrDMEo2RL7ACe
IhaX
0MNyz+CSZapZOTcAvVHrZZE=
=jGUj
-----END PGP SIGNATURE-----
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail