Re: [Nmh-workers] Domain Leakage Despite -messageid random.

[Ralph Corderoy]

Hi Ken,

> I'm not sure you can, in practice, guarantee that they are globally
> unique.

Ditto Message-ID?

> it occurs to me that if you really care what the content-id is (like
> you're sending some HTML email that refers to images in the email) you
> want to choose your Content-ID before the message has been completely
> constructed.
>
> All I'm suggesting is that -nocontentid be the default for mhbuild; if
> you want to still generate them, it's an easy change.

What if the recipient wants to refer back to that seventh JPEG of nine?

I had a shufty at emails here.  Ignoring those from nmh, I found
Content-ID in the email's headers of other MUAs.  Pine was one, and
Microsoft do it too, on occasion.

These two are from different organisations, but MacOutlook is common.

    Content-ID: <address@hidden>
    user-agent: Microsoft-MacOutlook/14.3.4.130416

    Content-ID: <address@hidden>
    user-agent: Microsoft-MacOutlook/14.3.6.130613

These institutions pump `sent from my iPhone', etc., through Outlook.

    Content-ID: <address@hidden>
    Message-ID: <address@hidden>

    Content-ID: <address@hidden>
    Message-ID: <address@hidden>

    Content-ID: <address@hidden>
    Message-ID: <address@hidden>

So does this one, but Liz manages to tweak Message-ID somehow.

    Content-ID: <address@hidden>
    Message-ID: <address@hidden>

BTW, Paul Fox, hi Paul, sent some, with nmh I presume, where one "host"
was shorter than the other, e.g.

    Content-ID: <address@hidden>
    Message-Id: <address@hidden>

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy