← Back to team overview

launchpad-dev team mailing list archive

Re: RFC: One True Way of addressing notification emails.

 

On 9 June 2010 20:30, Gavin Panella <gavin.panella@xxxxxxxxxxxxx> wrote:
> On 9 June 2010 16:25, Graham Binns <graham@xxxxxxxxxxxxx> wrote:
> ...
>> As for the third bug, I'm trying to work out a way to have an
>> impersonal To address for bugmail (probably $bugno@xxxxxxxxxxxxxxxxxx,
>> or some noreply address). The first solution to come to mind was to
>> have:
>>
>>  To: $bugno@xxxxxxxxxxxxxxxxxx
>>  Bcc: graham@xxxxxxxxxxxxx
>>
>> Which seems to fit the description of the bug. I'm open to other
>> solutions, however.
>
> Unless I've missed the point, I don't think the Bcc: is needed. The
> recipient gets set via SMTP's RCPT TO command. The message itself
> (headers and body together) is sent via SMTP's DATA command; most MTAs
> treat this as an opaque-ish lump (though I might be corrected). This
> is a bit like how you can send a jiffy bag full of lasagne to anyone
> without having to write their name in Béchamel on the top.
>

Okay, so, reading between the layers of pasta... yes, I see what you
mean. And doing some poking around in MP email headers I can see that
the MPs do exactly what we're trying to do here (they're To:
mp+$foo@xxxxxxxxxxxxxxxxxx but they still reach me), so I guess fixing
this may be a lot less simple than just hacking mailnotification.py to
do what we want.

Thanks for explaining this; I'll look into it more tomorrow. And then
my head may explode, rather like how a jiffy bag full of lasagne does
if you drop it from six  feet onto concrete.


-- 
Graham Binns | PGP Key: EC66FA7D



References