Re: message-ids containing slashes was: Can I use Mutt from Bash to extract attachments into an arbitrary directory?

[David Champion]

* On 19 Nov 2016, Cameron Simpson wrote: 
> Just to followup on this, here I am code reviewing some stuff for work and
> what does github use for Message-IDs? This:
> 
>  Message-ID: 

Interesting. I guess I would be inclined to solve this by simply
urllib.quote()ing the string - consistent and predictable encoding no
matter what oddities appear in the original string.

-- 
David Champion • d...@bikeshed.us


signature.asc
Description: PGP signature

message-ids containing slashes was: Can I use Mutt from Bash to extract attachments into an arbitrary directory?

[Cameron Simpson]

On 15Sep2016 11:52, Cameron Simpson  wrote:

On 14Sep2016 18:35, David Champion  wrote:

It will create a directory under /tmp/foo named for the message's
message-id, and store each attachment inside. Filenames are taken
from the MIME or generated sequentially if there is no filename.


Just an aside, now often do you encounter "/" in a Message-ID? It is 
legal, and has long discouraged me from the otherwise obvious and inuitive 
name-a-file-after-the-message-id.


Just to followup on this, here I am code reviewing some stuff for work and what 
does github use for Message-IDs? This:


 Message-ID: 

So there we have it, slashes in message-ids in the wild. I'm not objecting - it 
is perfectly legal and reasonable and very readable. Just an inconvenient 
datum.


Cheers,
Cameron Simpson