On Tue, Nov 17, 2009 at 01:49:22PM -0600, Lucas Nussbaum wrote:
> Hi,

Hi,

> I generate my mails on my laptop and send them using nullmailer.
> 
> The mails caff generates contain a Sender header, apparently based on
> the local hostname. That hostname can't be resolved, and as a result,
> caff's emails are rejected by some SMTP servers.
> 
> Example header generated by caff:
> <--------------
> Received: (nullmailer pid 25326 invoked by uid 1000);
>       Tue, 17 Nov 2009 19:44:12 -0000
> MIME-Version: 1.0
> Subject: Your signed PGP key 0x6AE1DF0D608F22DC
> User-Agent: caff 0.0.0.439 - http://pgp-tools.alioth.debian.org/
> X-Mailer: MIME-tools 5.427 (Entity 5.427)
> Sender: Lucas Nussbaum <[email protected]>
> Content-Type: multipart/encrypted;
>  protocol="application/pgp-encrypted";
>  boundary="----------=_1258487051-25273-1"
> To: [email protected]
> Content-Transfer-Encoding: 7bit
> From: Lucas Nussbaum <[email protected]>
> Date: Tue, 17 Nov 2009 13:44:12 -0600
> Message-Id: <[email protected]>
> ----------------->
> 
> It would be better to just drop that Sender header.

According to RFC 822 (http://www.faqs.org/rfcs/rfc822.html / 4.4.2) the Sender
field is not useful in our application.

quote RFC822 - 4.2.2:

 This field contains the authenticated identity  of  the  AGENT
 (person,  system  or  process)  that sends the message.  It is
 intended for use when the sender is not the author of the mes-
 sage,  or  to  indicate  who among a group of authors actually
 sent the message.  If the contents of the "Sender" field would
 be  completely  redundant  with  the  "From"  field,  then the
 "Sender" field need not be present and its use is  discouraged
 (though  still legal).  In particular, the "Sender" field MUST
 be present if it is NOT the same as the "From" Field

Thus, we could safely remove this header, as suggested by Lucas, since both
the *Sender* and *From* fields are the same.

I had a quick look at caff, and it seems the *Sender* field is automatically
filled by the MIME::Entity perl module. So far, I think we can only override it
by setting it as we do for the *From* field.

I will check that later, since I am on vacation tonight until January 5th.

Regards,

-- 
Franck Joncourt

Attachment: signature.asc
Description: Digital signature

Reply via email to