How do I forward a message completely?

[William Unruh]

When I use forward in alpine, what is forwarded is not the message, but
some edited part of the message. I can either forward the original as a
series of nested attachments, or I get an "edited" version of the
message (eg, sometimes no attachments, or only the text version of the
message or only the html version).

What I would like F (forward) to do is to act as though I had put a
forwarding rule in .forward for the system to send on the message.
Since I only want to forward some messages, putting a line in .forward
is not what I want. I also do not want to put the message into
displaying all headers and then putting the message into an attachment.
I would like the message on the other machine to be just as if the
message had originally been sent to that second machine.

I can save the message into a mail folder file, transfer that file to the other
machine, and then open it by treating that transfered file as a mail
folder, but that is far too many steps for something the system should
be able to do on its own.

[Eduardo Chappa]

Post by William Unruh
[...]
What I would like F (forward) to do is to act as though I had put a
forwarding rule in .forward for the system to send on the message.
[...]

This is what the Bounce "B" command does. The latest version of Alpine
allows you to bounce using a role, but that might not be enough. It will
all depend on what your SMTP server or ISP allows you to do.

Another option is to use the forward command. Press "H" before forward,
and then you will be offered to forward the message as an attachment. This
will send the message and attachments in one message, and you will have
the opportunity to add text to your message. On the recipient side, save
the the attachment labeled message/rfc822 message to a folder, and you
will have the copy of the message in the other machine.

I hope this helps.

[William Unruh]

Post by Eduardo Chappa

Post by William Unruh
[...]
What I would like F (forward) to do is to act as though I had put a
forwarding rule in .forward for the system to send on the message.
[...]

This is what the Bounce "B" command does. The latest version of Alpine
allows you to bounce using a role, but that might not be enough. It will
all depend on what your SMTP server or ISP allows you to do.

OK, that does work. Thanks. I never saw that command, and also felt
that it was just some way of sending the message back to the sender.

Post by Eduardo Chappa
Another option is to use the forward command. Press "H" before forward,
and then you will be offered to forward the message as an attachment. This
will send the message and attachments in one message, and you will have
the opportunity to add text to your message. On the recipient side, save
the the attachment labeled message/rfc822 message to a folder, and you
will have the copy of the message in the other machine.

Yes, I knew about that.

Too often it did the wrong thing.

Post by Eduardo Chappa
I hope this helps.

Thanks, it does.

[Eduardo Chappa]

Post by William Unruh

Post by Eduardo Chappa
This is what the Bounce "B" command does. The latest version of Alpine
allows you to bounce using a role, but that might not be enough. It
will all depend on what your SMTP server or ISP allows you to do.

OK, that does work. Thanks. I never saw that command, and also felt
that it was just some way of sending the message back to the sender.

I see. I think the analogy here is that as the message travels through the
internet it hops from server to server, and upon delivery you can make it
hop (or bounce) one more time.

[Johann Beretta]

Post by Eduardo Chappa

Post by Eduardo Chappa
This is what the Bounce "B" command does. The latest version of
Alpine allows you to bounce using a role, but that might not be
enough. It will all depend on what your SMTP server or ISP allows you
to do.

OK, that does work. Thanks.  I never saw that command, and also felt
that it was just some way of sending the message back to the sender.

I see. I think the analogy here is that as the message travels through
the internet it hops from server to server, and upon delivery you can
make it hop (or bounce) one more time.

Logical thinking, but I'd argue that the term "bounce" has been used to
describe undeliverable emails for a long time.

https://en.wikipedia.org/wiki/Bounce_message

Of course, the PINE coders can do whatever they want, but when you
co-opt a term already in use, it's going to lead to confusion.

[Carlos E.R.]

Post by Johann Beretta

Post by Eduardo Chappa

Post by Eduardo Chappa
This is what the Bounce "B" command does. The latest version of
Alpine allows you to bounce using a role, but that might not be
enough. It will all depend on what your SMTP server or ISP allows you
to do.

OK, that does work. Thanks.  I never saw that command, and also felt
that it was just some way of sending the message back to the sender.

I see. I think the analogy here is that as the message travels through
the internet it hops from server to server, and upon delivery you can
make it hop (or bounce) one more time.

Logical thinking, but I'd argue that the term "bounce" has been used to
describe undeliverable emails for a long time.

Yep.

Post by Johann Beretta
https://en.wikipedia.org/wiki/Bounce_message
Of course, the PINE coders can do whatever they want, but when you
co-opt a term already in use, it's going to lead to confusion.

It is, I have never used the feature, I find it confusing.

[William Unruh]

Post by Carlos E.R.

Post by Johann Beretta

Post by Eduardo Chappa

Post by Eduardo Chappa
This is what the Bounce "B" command does. The latest version of
Alpine allows you to bounce using a role, but that might not be
enough. It will all depend on what your SMTP server or ISP allows you
to do.

OK, that does work. Thanks.  I never saw that command, and also felt
that it was just some way of sending the message back to the sender.

I see. I think the analogy here is that as the message travels through
the internet it hops from server to server, and upon delivery you can
make it hop (or bounce) one more time.

Logical thinking, but I'd argue that the term "bounce" has been used to
describe undeliverable emails for a long time.

Yep.

Post by Johann Beretta
https://en.wikipedia.org/wiki/Bounce_message
Of course, the PINE coders can do whatever they want, but when you
co-opt a term already in use, it's going to lead to confusion.

It is, I have never used the feature, I find it confusing.

The name or the concept? I have started using it, and it is extremely
handy. My main mail machine is my work machine. I do not want a .forward
since I do not want 100 messages ( 50 of them spam) cluttering up my
home machine. But occasionally I want to look at an attachment or a
link, and it is really awkward ( never mind not working due to a bug in
my Google Chrome) to be running X across an internet connection from
work (X is really really attrocious across the internet). I was saving
the message, then rsyncing it to my home machine then looking at it
there. Pretty awkward. B works exactly as intended. Whether it should be
called Bounce, I admit it confused me so I never realised its power
until Chappa explained it here.

[William Unruh]

On 2020-09-15, William Unruh <***@invalid.ca> wrote:

One minor bug in the bounce command. When the message is sent, alpine
keeps the information message
[Sending mail | 100% ]
at the bottom of the page. Usually the "Sending mail" message means that
it is in the process of sending it, and a different message (like
"Message sent") is displayed .
But here it seems to mean that it has actually sent successfully.
It confused me initially as I took it to mean that that it was still
wrapping up the sending process. but clearly not.