Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

After Tbird 24, "reply to" picks up the primary account for the "from", not the actual "to" account for the "from," when reply is from a Local Folder.

  • 2 одговорa
  • 1 има овај проблем
  • 9 прегледа
  • Последњи одговор послао Track 21

more options

"Reply" still picks up the wrong address. Linux Ubuntu 18.04 (but this is the very same issue experienced after 24.6 on Mac OSX 10.6.8) Multiple email addresses. Filters use Local Folders. Incoming email filtered to Local Folder. Want to reply to sender. At this stage, in 24.6, the correct "from" address is picked up from the email's "to" address. At this stage, in versions later than 24.6, the incorrect "from" address is supplied by the primary email account (the first one set up in Tbird) rather than the actual "to" address from the email. Raised this issue a few years ago via Bugzilla. It's still a problem in 68.2.2. Still having to retrograde Tbird (24.6 is rock solid) to get correctly addressed replies out.

"Reply" still picks up the wrong address. Linux Ubuntu 18.04 (but this is the very same issue experienced after 24.6 on Mac OSX 10.6.8) Multiple email addresses. Filters use Local Folders. Incoming email filtered to Local Folder. Want to reply to sender. At this stage, in 24.6, the correct "from" address is picked up from the email's "to" address. At this stage, in versions later than 24.6, the incorrect "from" address is supplied by the primary email account (the first one set up in Tbird) rather than the actual "to" address from the email. Raised this issue a few years ago via Bugzilla. It's still a problem in 68.2.2. Still having to retrograde Tbird (24.6 is rock solid) to get correctly addressed replies out.

Сви одговори (2)

more options

I suggest you return to Bugzilla then. I have no Apple product to test your assertions on, but I certainly can not reproduce it on Windows 10.

As far as 24 is concerned it is not even in the rear vision mirror of supported product.

Standard diagnostics aside I doubt anyone here can help you.

To diagnose problems with Thunderbird, try one of the following:

  • Restart Thunderbird with add-ons disabled (Thunderbird Safe Mode). On the Help menu, click on "Restart with Add-ons Disabled". If Thunderbird works like normal, there is an Add-on or Theme interfering with normal operations. You will need to re-enable add-ons one at a time until you locate the offender.
  • Restart the operating system in safe mode with Networking. This loads only the very basics needed to start your computer while enabling an Internet connection. Click on your operating system for instructions on how to start in safe mode: Windows 10, Windows 8, Windows 7, Windows Vista, Windows XP, OSX
If safe mode for the operating system fixes the issue, there's other software in your computer that's causing problems. Possibilities include but not limited to: AV scanning, virus/malware, background downloads such as program updates.
more options

Matt, Thx greatly for having a minute. Really.

You know, these "by written word" only forums are kind of a hoot. What's "read" and what's "written" don't always match.

In the event this follow up helps, I'm presently in Linux 18.04 (Bionic). The mention about Mac is that the problem I'm experiencing has existed since 10.6.8 (Mac OS X), which intends to put a duration of the problem in context. And, this problem, of picking up the wrong "from" address to use in the reply note from a note received and then filtered to a Local Folder, has reoccurred, one more time, in the standard Linux Tbird version, downloaded/installed via apt-get install, which is presently 68.2.2. That's just to say that there's no issue/need for support for 24.6. It's rock solid. That's the version I still rely on. The problem has recurred, once again, in the latest version I've tried, and that's, in Linux, 68.2.2. (I think the most recent Win version is 68.3 something.) I'm back in 24.6, because that's the version that works. That one isn't the problem. The problem is in every version since then. Moreover, since it's now a confirmed as a cross-platform matter, I hoped raising it again would lead to a solution. Maybe it still will.

Down that path, I'll try the "without add-ons" per your suggestions, in the latest version, 68.2.2, where the problem has arisen, again, and see what benefit that may provide. I'll keep you posted.