mirror of
https://git.sr.ht/~sircmpwn/aerc
synced 2026-01-23 15:51:34 +01:00
Hi! This patch will fix missing filename if it is RFC2231 encoded with charset different then ASCII or UTF8. Example how it looks like in mail: Content-Type: application/pdf; name="=?UTF-8?Q?Opis_przedmiotu_zam=c3=b3wienia_-_za=c5=82=c4=85cznik_nr_1?= =?UTF-8?Q?=2epdf?=" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename*0*=iso-8859-2''%4F%70%69%73%20%70%72%7A%65%64%6D%69%6F%74%75%20; filename*1*=%7A%61%6D%F3%77%69%65%6E%69%61%20%2D%20%7A%61%B3%B1%63%7A%6E; filename*2*=%69%6B%20%6E%72%20%31%2E%70%64%66 Yes, this should be forbidden :-). Anyway, best solotion in such cases is to failback to Content-Type name. I am not sure if it is guaranted to be there, but probably it will. Leszek |
||
|---|---|---|
| .. | ||
| account | ||
| compose | ||
| msg | ||
| msgview | ||
| terminal | ||
| cd.go | ||
| commands.go | ||
| ct.go | ||
| exec.go | ||
| global.go | ||
| help.go | ||
| history.go | ||
| new-account.go | ||
| next-tab.go | ||
| prompt.go | ||
| pwd.go | ||
| quit.go | ||
| set.go | ||
| term.go | ||
| util.go | ||