1. Forum
  2. Fidonet
  3. WINPOINT

  • [Bug] Netmail reply to echomail

    From Martin Foster@2:280/464.27 to Tim Schattkowsky on Sat Jan 22 11:14:00 2022
    Hello Tim!

    I needed to send a netmail reply to an echomail message, so I pressed <Ctrl+N> expecting to be taken into the message editor but I got the following popup: "No compatible uplink for the message!". I'm assuming that this is a bug?

    However, I got around it for now by pressing <Ctrl+R> and then clicking the "Netmail" button in the message editor but actually, I rather like that way of doing it :-)

    Regards,
    Martin

    --- WinPoint 394.0
    * Origin: WinPoint Test Rig - UK - (2:280/464.27)
  • From Tim Schattkowsky@2:240/1120.29 to Martin Foster on Sat Jan 22 21:03:07 2022
    //Hello Martin,//

    on *22.01.22* at *11:14:00* You wrote in rea *WINPOINT*
    to *Tim Schattkowsky* about *"[Bug] Netmail reply to echomail"*.

    I needed to send a netmail reply to an echomail message, so I pressed <Ctrl+N> expecting to be taken into the message editor but I got the following popup: "No compatible uplink for the message!". I'm assuming that this is a bug?

    What was the original sender address of the netmail?

    However, I got around it for now by pressing <Ctrl+R> and then clicking the "Netmail" button in the message editor but actually, I rather like that way of doing it :-)

    That't the "new" way. I actually considered removing Ctrl-N ... but its a classic :)

    Regards,
    Tim
    --- WinPoint 395.0
    * Origin: Original WinPoint Origin! (2:240/1120.29)
  • From Tim Schattkowsky@2:240/1120.29 to Martin Foster on Sun Jan 23 02:03:26 2022
    //Hello Martin,//

    on *22.01.22* at *11:14:00* You wrote in rea *WINPOINT*
    to *Tim Schattkowsky* about *"[Bug] Netmail reply to echomail"*.

    Hello Tim!

    I needed to send a netmail reply to an echomail message, so I pressed <Ctrl+N> expecting to be taken into the message editor but I got the following popup: "No compatible uplink for the message!". I'm assuming that this is a bug?

    I think this happend because the receiver was in a different Zone than all of your uplinks. In this case, the default uplink is supposed to be used (first active uplink in list), but that broke recently. Fixed it just now.

    Regards,
    Tim
    --- WinPoint 395.0
    * Origin: Original WinPoint Origin! (2:240/1120.29)
  • From Martin Foster@2:280/464.27 to Tim Schattkowsky on Sun Jan 23 08:28:08 2022
    Hello Tim!

    *** Saturday 22.01.22 at 20:03:07, Tim Schattkowsky wrote to Martin Foster:

    I needed to send a netmail reply to an echomail message, so I pressed
    <Ctrl+N> expecting to be taken into the message editor but I got the
    following popup: "No compatible uplink for the message!". I'm assuming
    that this is a bug?

    What was the original sender address of the netmail?

    I wasn't replying to a netmail, I was netmail-replying to an echomail.

    However, I got around it for now by pressing <Ctrl+R> and then clicking
    the "Netmail" button in the message editor but actually, I rather like
    that way of doing it :-)

    That't the "new" way.

    Like it! :-)

    I actually considered removing Ctrl-N ... but its a classic :)

    Depends which software you're using ;-))

    Regards,
    Martin

    --- WinPoint 394.0
    * Origin: WinPoint Test Rig - UK - (2:280/464.27)
  • From Martin Foster@2:280/464.27 to Tim Schattkowsky on Sun Jan 23 08:35:03 2022
    Hello Tim!

    *** Sunday 23.01.22 at 1:03:26, Tim Schattkowsky wrote to Martin Foster:

    I needed to send a netmail reply to an echomail message, so I pressed
    <Ctrl+N> expecting to be taken into the message editor but I got the
    following popup: "No compatible uplink for the message!". I'm assuming
    that this is a bug?

    I think this happend because the receiver was in a different Zone than
    all of your uplinks.

    Yes, the recipient was in Z1 whereas all my uplinks are in Z2.

    In this case, the default uplink is supposed to be used (first active uplink in list), but that broke recently. Fixed it just now.

    OK.

    Regards,
    Martin

    --- WinPoint 394.0
    * Origin: WinPoint Test Rig - UK - (2:280/464.27)