On Wed, Nov 15 2017, David Bremner wrote: > Kai Harries <kai.harries@gmail.com> writes: > >> David Bremner <david@tethera.net> writes: >> >>> During off-list discussion, Kai mentioned id:87a7zsm5ol.fsf@gmail.com as >>> a message that he cannot bounce (and also not forward?). For me this >>> forwards fine, but does not bounce because it has a corrupted Cc header, >>> and my MTA rejects it. That doesn't sound related to the original >>> problem report (nothing about line endings). >> >> Can you please evaluate the following on your system: >> >> (call-process "notmuch" nil t nil "show" "--format=raw" "id:87a7zsm5ol.fsf@gmail.com") >> >> If I do this on my system, then the text that is inserted into the >> buffer has ^M (CR) at the line endings. Is this expected? > > No ^M line endings for me. Can you check the file on disk? Maybe "od -a" > lacking a better idea. $ notmuch search --output=files id:87a7zsm5ol.fsf@gmail.com outputs path to one file in my system. the mail content is base64-encoded and there is no cr characters in my system (I used base64 -d 'edited-mail ' | tr '\r' '$' | less to look) As Kai sent the mail, his local copy may be encoded differently... Tomi (Hoo, I just wondered whether there is base64-decode-region in emacs -- there is a function exactly that name... had to M-x read-only-mode (where did M-x toggle-read-only disappear) in notmuch-raw-id:... buffer before trying that (i.e. in emacs mua, in show buffer, first pressed 'V' to see raw message contents.) PS2: it is possible this mail doesn't reach Kai, as gmail is somewhat picky from where it accepts email... we may get this fixed any century now, though. _______________________________________________ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch