I cannot duplicate that. If I compose while offline, the 'send' message says 'send later' - and if I start Thunderbird later, I am immediately prompted to go online and send messages, as attached screenshot shows. That is, if you specify you want to work offline, and then compose a message, Thunderbird is retaining your request to stay offline. On restarting, however, TB prompts to confirm whether you wish to continue offline, or to go online.

Thanks. My procedure is a bit different: - Open TB in offline mode - Write an e-mail and click "Send Later" - Right-click on Outbox folder and select "Send unsent messages" Result: nothing happens. Desirable behavior: either notify the user that his messages have not been sent because TB is offline, or [preferred] request confirmation to go online.

Well, since you click 'send later', there is no need to tell you that the message has not been sent. The solution is to click file>offline and untick 'work offline.' If you would like the changed, you can go to connect.mozilla.org and submit the idea.

I've tested this and compared and you are correct. In 102* if Offline and you click on 'Sent unsent mesasges' you would get a pop up prompt which said: " You are currently offline. Do you want to go online to send unsent messages?"

This is not occurring in my beta 122.0b2 - latest beta version.

Currently, you have to assume you are aware of the Offline/Online' status. and Go into 'Online' mode first before you do the right click to 'send unsent mesages'. I'll check out to see if there's a bug report on this.

Worth checking your settings to make sure they are set up as desired, so when you do go to Online mode you get a prompt asking if you want to send at that moment or not.

• Settings > General
• Scroll to 'Network & Disk Space' section
• Click on the 'Offline...' button

• For 'Send unsent messages when going online?'
• Choose your prefered option - I have selected 'Ask me'
• click on 'OK'

Many Thanks for bringing this to our attention. As I can replicate this problem and have two versions for comparison, then it needs to be reported. I've created a bug report for this issue. https://bugzilla.mozilla.org/show_bug.cgi?id=1873487

Thanks, Toad-Hall, much appreciated. Looking forward to the fix.

The developers are onto this and the bug has been marked as fixed. But, I'm not sure whether it will be in the next release or shortly thereafter.