• How do I forward a message completely?

    From William Unruh@21:1/5 to All on Sat Sep 5 17:54:23 2020
    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.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Eduardo Chappa@21:1/5 to William Unruh on Sat Sep 5 12:42:50 2020
    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.

    --
    Eduardo
    https://tinyurl.com/yc377wlh (web)
    http://repo.or.cz/alpine.git (Git)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Eduardo Chappa@21:1/5 to William Unruh on Sat Sep 5 16:38:21 2020
    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.

    --
    Eduardo
    https://tinyurl.com/yc377wlh (web)
    http://repo.or.cz/alpine.git (Git)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From William Unruh@21:1/5 to Eduardo Chappa on Sat Sep 5 22:30:15 2020
    On 2020-09-05, Eduardo Chappa <chappa@washington.edu> wrote:
    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.

    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.

    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.

    I hope this helps.

    Thanks, it does.


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Johann Beretta@21:1/5 to Eduardo Chappa on Mon Sep 14 22:34:12 2020
    This is a multi-part message in MIME format.
    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.


    -----BEGIN PGP PUBLIC KEY BLOCK-----

    mQGNBF64/IEBDACVrdj4Yfr7PC/t7tBofnMWWDoWiRxl+Oo64YjsamZGiy0hJHfP ZhI/pnOgqhy6pzsF/8c9Dx9A9SSAJOvC96wMTHgdh4GbffekCwoIXcKZeg9bjXjV Nth5CYOSBTQ9C/pl/j0CwjBQ9mdyK7FoHMlBEmQ4ButtBJgPNjyruiFkBt2r/99u w+hZEt+tO3D69v2MBMVF8pjZWzDDoIsbCUQGtaDD4uAIMqdDl28yw5FeYFg7PKLJ DXft8pNm/4bWv7BizTEVwSkcpPMR/6v/gXUhUsqCoqaWT9oSALmO5l9JfuNk2mpP bjue5joPlpOzaH+ZC0et/eynzyTxOpIAL97g1SVQLqqKRMu3atFda53ZyMNAcH3G R1gV5kX1rM3Ajyw1d7hp1rAYINdB/O/Y8VkNn0j6NZmEi8E1AwK3hu4ZJPIr9FQF bsWmAtjIgO1VXHxvxB7nYF5o7M350hW9SZlkbDf9NWBUHJlc5j4WVEYCjw1C3y8h OwFl1RfDFETqmdUAEQEAAbQrSm9oYW5uIEJlcmV0dGEgPGJlcmV0dGFAbnVuLXlh LWJpem5lc3MuY29tPokB1AQTAQgAPhYhBJx2orrQOL31I0cnEBM/4/Zk8Q8TBQJe uP0PAhsDBQkB4TOABQsJCAcCBhUKCQgLAgQWAgMBAh4BAheAAAoJEBM/4/Zk8Q8T 0KYL/jL1DoQWCMil5EPlLSDG3iByV711VChSpWGbE4m2KrMjMdG0gQBNpg3IChKi tP5/5YdxHGKGjuDxvF/laTq/5KXosNmfdaJr9pmztOWT7tvmlwM+zUR782EQJeeU rGfv6TwYng7TUEaBH86Rg8m6fMKNqSt9MLly+p48Lv8TNj1RofvMv5Ng5xJWkGJ2 +yJ6k61h6Xg8OFY/AEs98OMejDKPq2PTZyH1BQKmyDk82wOGUdSkQoA41aZSckki aXFXIG97NhXY+dcZbOVCjXez0Iujo4vSCbM+x63fX7FyyNsG4f2vPfqhrqNGgrwD KQxYzWgVfvCqKpW6S75l0DfelMFAjM5GcpKs65vRyjRDuMlj6/jSN0O6Os8EOlhr lHBoY1PrBwTX+pBgb1esF2KLbFjfxGLzvbfR85TbYaZi/hohwD/rm+s5QWe03pO/ n85mdVxYAhAhvXsO6s7wfTm0qc/SK7Xp82aYOKVArarNgRIMul7UBo2786ZFhmZY wQGPQ7kBjQReuPzOAQwAoWku3K9ipwwiuH/9C8uUqY1kZy9VW/K7b5uXKww43Dl5 SAFTd+TC8nySqSacHohTQSnd8r3eZgX6az3SR30Y0F6Ftprbx0dkRABKtVzEcxCJ Y2+lqfT6aPIQh+tp/mmWVzrmeYlQNFVLNbu0Tk62K0sedfnhDGgqN4DEWQqgGfG5 Zsj1VcYoXYkt1V/U16GPs75aqWdt+OQmlDb2FQbo/HcsB1bdrE9A7fM39WQpod/k tkAZRJM6RX1f2hJAFwgBEKYieK4ZGfMtgxpIMnvBDwB1FuLw2sGshRtaPO8t0F+w jR/i6PEwCWZSaENhik+oAxDgaKPkxZHpzYS3RM67HoRie1ewuqAw77xeAI4WLbxo +FNg8W+kdPgdRkGeMaYot4hoVGpgF0q0cBPm97wAysxbAu/TDlX/ev4XEkRnZg7k ScCVTrkk9bSVIXs0uB8qkudcudrzokZJ+6v+X5JKgwOMBBSY7sk11T3azog6wxJN BuqS1wB/H4Kht9OMLoTVABEBAAGJAbwEGAEIACYWIQScdqK60Di99SNHJxATP+P2 ZPEPEwUCXrj8zgIbDAUJAeEzgAAKCRATP+P2ZPEPE1UNC/sFAMZnLH8OdDwflfhr iyESWHhRJb1xC4tlJzZ/ufbWY8SbVqO5HbA7EALwW3Ony8SNRRN/OUBw7bM12VPX 0ya6RTQHtPzweL98AnGu0YbyHtKwJrNlGQS0LKWDv4FWQ6f8HxZQt0EzhgRaudGE MHNACuKbxWFpvNAM95LNpLDjRE+DJYGnsDOCRRC4fFRTG0+vqIqgniQzHmn8ddr6 5NazPg07TJzqLjsNBcTCGvRivoRDRP75PnQS8VppnyWubbXJjffmuIG2iqHnY5as ibsSo+TJ+7UEhbNx+uQBKO5KXvG/u9eWgyJz/Uf47zUbG9v9vocbOSbylPHjC3uO ONw91nUHLmGzi3ZmeyPeCu6pyjz/dzUcqYS3iw1/q+UWyS+SOIaz9sAMd1q8QQwW CKubXtlM6DKdnxxNVV4NkwFIeOF6d1pFiIgojqbsNnkPVaFQDc+u9UkkpevBymwr a0HThxeNkYA6MDWSbxJjPvyy1OO2yERbo9RG2jzOx85j29o=
    =d5t3
    -----END PGP PUBLIC KEY BLOCK-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to Johann Beretta on Tue Sep 15 13:22:41 2020
    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.

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From William Unruh@21:1/5 to Carlos E.R. on Tue Sep 15 22:27:09 2020
    On 2020-09-15, Carlos E.R. <robin_listas@es.invalid> wrote:
    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.

    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.


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From William Unruh@21:1/5 to All on Wed Sep 16 19:05:09 2020
    On 2020-09-15, William Unruh <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.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)