[...]
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.
On Sat, 5 Sep 2020, William Unruh wrote:
[...]
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.
On Sat, 5 Sep 2020, William Unruh wrote:
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.
On 9/5/20 3:38 PM, Eduardo Chappa wrote:
On Sat, 5 Sep 2020, William Unruh wrote:
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.
On 15/09/2020 07.34, Johann Beretta wrote:
On 9/5/20 3:38 PM, Eduardo Chappa wrote:
On Sat, 5 Sep 2020, William Unruh wrote:
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.
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 285 |
Nodes: | 16 (2 / 14) |
Uptime: | 77:59:25 |
Calls: | 6,489 |
Files: | 12,096 |
Messages: | 5,276,459 |