Re: Forwarding email
>I have added the line forw: -format to my ~/.mh_profile. > >Now I find if I do: > >forw -mime 33 > >I get that empty #forw line and nothing else. I know this has been mentioned several times, but when you get this line you STILL need to run the "mime" command at the What now? prompt before you send the draft. We could improve on this, I think, but that's the reality of today. >However if I simply do: > >forw 33 > >I see the draft, the forwarded mail go out correctly and i can read it >in my Proton account. This won't preserve the MIME structure of the message, and I'm not quite sure what would happen if it's a 8-bit character set (probably the wrong thing). If you find this works for you then I suppose it will be sufficient. --Ken
Re: Forwarding email
I have added the line forw: -format to my ~/.mh_profile.
Now I find if I do:
forw -mime 33
I get that empty #forw line and nothing else.
However if I simply do:
forw 33
I see the draft, the forwarded mail go out correctly and i can read it
in my Proton account.
Thank you for working with me on this but I feel I've taken up enough
of your time.
Thank you
Arthur
In message <20230711155916.a0ffd196...@pb-smtp2.pobox.com>, Ken Hornstein
writes:
>
>I believe that if you modify the forw line with a disposition, the right
>thing will happen. That would look like this:
>
>#forw [forwarded message] {inline} ... rest of forw line
>
>>Finally, using dist to send to the iCloud account works. Using dist to
>>send to Proton fails with:
>>
>>Rejected due to unmatching envelope and header sender.
>
>Sigh, THAT is completely wrong in that Proton Mail isn't looking at the
>Resent-From header. You could add an Envelope-From header to set the
>Envelope from header to match the original message, but that will probably
>fail some other anti-spam feature.
>
>--Ken
Re: Forwarding email
>If I forward to my iCloud account, it works. If I forward to my
>Proton account wHat I get is an empty message with an attachment; the
>attachment consisting of a string of numb...@eddie.fios-router data 8 KB
>
>I have stumbled upon the fact that if I use MH-E within emacs I
>can forward in-line instead of as an attachment and that works.
>Unfortunately, I can't seem to find how to use nmh to forward in-line.
What does "forward in-line" mean, exactly? "forw -mime" does not mark
it as an attachment; technically, it does not put a disposition at all.
It may be that Proton Mail sees a MIME message with a disposition
header as an attachment (disposition headers are optional; in theory
the MUA is allowed to do whatever it wants with it).
I believe that if you modify the forw line with a disposition, the right
thing will happen. That would look like this:
#forw [forwarded message] {inline} ... rest of forw line
>Finally, using dist to send to the iCloud account works. Using dist to
>send to Proton fails with:
>
>Rejected due to unmatching envelope and header sender.
Sigh, THAT is completely wrong in that Proton Mail isn't looking at the
Resent-From header. You could add an Envelope-From header to set the
Envelope from header to match the original message, but that will probably
fail some other anti-spam feature.
--Ken
Re: Forwarding email
If I forward to my iCloud account, it works. If I forward to my Proton account wHat I get is an empty message with an attachment; the attachment consisting of a string of numb...@eddie.fios-router data 8 KB I have stumbled upon the fact that if I use MH-E within emacs I can forward in-line instead of as an attachment and that works. Unfortunately, I can't seem to find how to use nmh to forward in-line. Finally, using dist to send to the iCloud account works. Using dist to send to Proton fails with: Rejected due to unmatching envelope and header sender. Thanks, Arthur In message <20230710224555.cf42123...@pb-smtp21.pobox.com>, Ken Hornstein writes: >>Unfortunately, I am back again with the same issue. >>[...] > >I went back and looked at your original email about this, which is >here: > >https://lists.nongnu.org/archive/html/nmh-workers/2023-04/msg00083.html > >The original information you were given still holds true, in that doing >this should work: > >forw -mime 42 >[...] >What now? mime >What now? send > >Now you reported back then it "didn't work" to a Proton Email account. >Drilling down into this, it seems that it made it to Proton but it wasn't >viewable. > >Let's talk about what is going on here. When you run "forw -mime" it's >inserting a mhbuild directive into the reply message. That's the line >that begins with "#forw ...". The "mime" command runs mhbuild and you >end up with a message that contains a message/rfc822 part. If you don't >add anything before or after the "#forw" line, that's ALL the message >contains. > >It looks like Proton Mail (I am presuming the web interface) doesn't quite >deal with a message with a single message/rfc822 MIME part properly; it >treats it as an "attachment" and you can't view the content. Which is >unfortunate. You could try adding some text before the #forw line (this >is before you run "mime"), and MAYBE that would work. But if you goal >is to just forward a single message you COULD use dist(1); that will just >pop up a draft where you can just enter the recipient's names and they >will get an exact copy of the message (with the Resent-From and Resent-To >headers from the dist(1) draft). Generally all web mail clients seem to >do the right thing with those messages (but they don't all display >the Resent-From header so it can be confusing). > >--Ken >
Re: Forwarding email
>Unfortunately, I am back again with the same issue. >[...] I went back and looked at your original email about this, which is here: https://lists.nongnu.org/archive/html/nmh-workers/2023-04/msg00083.html The original information you were given still holds true, in that doing this should work: forw -mime 42 [...] What now? mime What now? send Now you reported back then it "didn't work" to a Proton Email account. Drilling down into this, it seems that it made it to Proton but it wasn't viewable. Let's talk about what is going on here. When you run "forw -mime" it's inserting a mhbuild directive into the reply message. That's the line that begins with "#forw ...". The "mime" command runs mhbuild and you end up with a message that contains a message/rfc822 part. If you don't add anything before or after the "#forw" line, that's ALL the message contains. It looks like Proton Mail (I am presuming the web interface) doesn't quite deal with a message with a single message/rfc822 MIME part properly; it treats it as an "attachment" and you can't view the content. Which is unfortunate. You could try adding some text before the #forw line (this is before you run "mime"), and MAYBE that would work. But if you goal is to just forward a single message you COULD use dist(1); that will just pop up a draft where you can just enter the recipient's names and they will get an exact copy of the message (with the Resent-From and Resent-To headers from the dist(1) draft). Generally all web mail clients seem to do the right thing with those messages (but they don't all display the Resent-From header so it can be confusing). --Ken
Re: Forwarding email
Hi Arthur, > I have been advised, and have tried using: > > forw -mime 5 > > where 5 is the number of the email I am trying to forward. > > This gets me: > > From: aalin...@riseup.net > To: > cqc: > Fcc: +outbox > Subject: Welcome to your The New York Times Replica Edition (fwd) > > #forw [forwarded message] +/home/slaurel/Mail/nytimes 5 > > No draft to edit. What you've shown us above is the draft. If you wish, you may alter what's after the ‘’ to be the body text of your email as normal. Just leave the ‘#forw...’ line at the end. > Sending this gets me an email with that one line: > > #forw [forwarded message] +home/slaurel/Mail/nytimes 5 > > and nothing else. That's because the draft isn't being processed by mhbuild(1). I assume you're seeing the whatnow(1) prompt and are using that to send the email? Before you send it, enter ‘mime’ to have whatnow run mhbuild. This will alter the draft. (You can see the change by entering ‘edit’ at the same prompt to return to the editor. Exit the editor without making changes.) Send the email in the same way as before. -- Cheers, Ralph.
Forwarding email
Unfortunately, I am back again with the same issue. I have been advised, and have tried using: forw -mime 5 where 5 is the number of the email I am trying to forward. This gets me: From: aalin...@riseup.net To: cqc: Fcc: +outbox Subject: Welcome to your The New York Times Replica Edition (fwd) #forw [forwarded message] +/home/slaurel/Mail/nytimes 5 No draft to edit. Sending this gets me an email with that one line: #forw [forwarded message] +home/slaurel/Mail/nytimes 5 and nothing else. Thanks, Arthur
