--- Begin Message ---
> you're asking the wrong group for such a question. Enigmail is not about
> creating or parsing MIME structures, but about encrypting & decrypting
> messages.
No worries, thank you Patrick.
I'll make sure to only ask email encryption/decryption related questions on
this email list.
My apologies.
Regards,
Random Noodles
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, February 17, 2019 3:50 PM, Patrick Brunschwig <[email protected]>
wrote:
> On 16.02.2019 21:38, Noodles wrote:
>
> > Hello,
> > Is this a valid email attachment header?
> >
> > > Content-Type: image/gif; name="nyan cat =?UTF-8?Q?=E2=9C=94=2Egif?="
> > > Content-ID: <[email protected] mailto:[email protected]>
> > > Content-Disposition: attachment;
> > > filename0=utf-8''nyan%20cat%20%E2%9C%94.gif
> > > Content-Transfer-Encoding: base64
> >
> > Why are there (0) characters after "filename" and after mentioning
> > "utf-8", why are there two single quotes before the attachment name
> > appears in the header?
> > If headers like these should be parsed without letting the user know of
> > any parsing errors then what regex (if any) can you recommend to extract
> > the attachment filename from the header?
> > I found the header on this
> > page:
> > https://github.com/nodemailer/mailparser/blob/master/examples/nodemailer.eml
> > https://github.com/nodemailer/mailparser/blob/master/examples/nodemailer.eml#L107.
>
> The "filename" line looks wrong to me, but generally speaking, you're
> asking the wrong group for such a question. Enigmail is not about
> creating or parsing MIME structures, but about encrypting & decrypting
> messages.
>
> -Patrick
--- End Message ---
_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
