MacInTouch Amazon link...

Apple Mail and email alternatives

Channels
Apple, Troubleshooting, Products

Ric Ford

MacInTouch
I used webmail to move the two messages to two different mailboxes and rebuilt both. Everything looked OK in Mail. Then I moved the two messages back together, and poof! They combined together again as a broken message.
This sounds like a problem related to "threaded" viewing. You might want to experiment with settings in Mail > Preferences > Viewing > View Conversations.
 


I'm not familiar with Apple Mail, but I don't think it's terribly different from Thunderbird or Postbox, and these types of problems sound quite a bit like a "filtering" problem. In Postbox, this happens if you inadvertently have a search active without realizing it, or some filter attribute active without realizing it (e.g. "Unread" or "Has Attachments").
Nope, no search or filter is intentionally going on. The mail isn't lost. The text simply disappears and the message 'no mail selected' appears. The mail can be viewed again by clicking again on the message header. Annoying because I don't load remote content automatically, and I need to reclick 'load' each time the content disappears and then scroll down to find where I was reading. This happens seconds or minutes (or never) after opening a message. This can happen without touching anything. Also using Classic View and POP for all accounts. I don't recall if this happened in High Sierra. However, the attachments symbol stopped showing up in High Sierra. I liked that as a warning before opening any mail.
 


Nope, no search or filter is intentionally going on. The mail isn't lost. The text simply disappears and the message 'no mail selected' appears. The mail can be viewed again by clicking again on the message header. Annoying because I don't load remote content automatically, and I need to reclick 'load' each time the content disappears and then scroll down to find where I was reading. This happens seconds or minutes (or never) after opening a message. This can happen without touching anything. Also using Classic View and POP for all accounts. I don't recall if this happened in High Sierra. However, the attachments symbol stopped showing up in High Sierra. I liked that as a warning before opening any mail.
I see this, too, in a slightly simpler setup: MacBook Pro 11,3, macOS 10.12.6, Apple Mail 10.3, IMAP only, lots of filtering going on.

It seems to often happen on Mail launch when it first searches the server for new mail. Seldom, but still annoying, it happens when reading, with my hands nowhere near the mouse or keyboard. Click on the sidebar message, and all is well. It's as if it loses the idea of what has been selected.
 


I've been having trouble with Apple Mail going back to Sierra. I've been using classic layout, with conversation threading turned off, because I find this to be by far the most efficient, having used this kind of setup since the early 90's.

First, if you click on a message in the inbox, you have to wait a fraction of a second (~0.75s) before hitting reply (whether using the keyboard or button), otherwise Mail composes a reply to the wrong message. Sometimes it's the message previously highlighted, and other times it's the message above or below the newly-selected message. (There seems to be a lag between the selection in the NSTableController and the underlying array controller.) This is intermittent but frequent with as few as 1,000-2,000 messages in the inbox on a Mac Pro with 64GB memory, and a retina iMac with 32 GB.

Secondly, I prefer seeing newest email at the bottom. When switching between accounts, or coming back out from a search into the mailbox viewer window, Mail always resets the selection to the top email -- i.e. the oldest. The End key does not move the visible area down unless you first select a message in the inbox view... I assume the developers put their newest mail at the top (or have fewer than a screen's worth of emails in their inbox) and don't do a simple sanity check for people who do it differently.

Thirdly, if Mail is open on more than one Mac simultaneously, one open instance will randomly crash with an off-by-1 error once or twice daily — I've traced it to when the dedicated junk-mail filtering Mac filters out spam and moves an email out of the relevant account's inbox view. (The crashed Mail instance tries to access the message at offset n, when the underlying 0-based array only has n elements, meaning there is an out of bounds error by a single entry since the max entry is at n-1. I'm not sure why a remote change can cause a local array index error if the local array is properly updated to reflect a remote change, but it does.)

I've opened RADARs on all three errors. All three were closed as duplicates, long (years+) ago. None has ever been solved. I've rebuilt the various inboxes, emptied and refilled them, etc, without result.

So show-stopper bugs in a key work app (for me) have existed unfixed for years. Yet we get animated face emojis....
 


Secondly, I prefer seeing newest email at the bottom. When switching between accounts, or coming back out from a search into the mailbox viewer window, Mail always resets the selection to the top email -- i.e. the oldest. The End key does not move the visible area down unless you first select a message in the inbox view... I assume the developers put their newest mail at the top (or have fewer than a screen's worth of emails in their inbox) and don't do a simple sanity check for people who do it differently.
I have seen something similar in Mail in Mojave (currently at 10.14.5 but the issue is present in earlier versions). I use the classic view with the newest email at the bottom of the list. If I select an email and then sort by sender, the list will sort accordingly but the focus will shift to be at the top (i.e. senders with “a” or a number as the first character in their email). My selection is there somewhere, but it is a long list. So I re-sort by date, select the email again, sort again by sender, and this time the emails from the selected sender are in focus. This is repeatable, but I have not traced all of the details. It will happen more than once with the same launch of Mail.

Oh, yes, and for some reason, Mail will surreptitiously open a new message without a sender, behind my back. I only notice when I access the Windows menu. Also, no clue as to what triggers this action.
 


I see the reverting-to-new-at-the-top-when-switching-accounts thing on all our computers, some of which are running macOS 10.12, some 10.13, and one 10.14. It is obviously scripted into Mail, though as others have noticed, I don't see why it couldn't be fixed to stay at what the user chooses.

The other bugs mentioned in this thread are unfamiliar to me, but I have found that if I accidentally move an email to the wrong mailbox and then hit Command-z, the email will move back to the Inbox with the first two lines showing (I don't use Classic layout, and I have List Preview set at two lines), but if I open the email, the body is blank. I seem to remember that if I don't open the email right away, but wait some time (several minutes at least; it may take longer, I can't really remember), the body of the email shows up. However, if, instead of undoing, I go to the mailbox to which I sent the email and move it back to the Inbox, everything is fine.

One weird thing is that if I have chosen Undo and see the blank body of the email, if I leave it in the inbox and go to the mailbox to which it was moved, it is still there, body intact, and if I then move it manually to the Inbox, I don't receive any message about duplicating an item – the email now shows up in the Inbox, body intact.
 


First, if you click on a message in the inbox, you have to wait a fraction of a second (~0.75s) before hitting reply (whether using the keyboard or button), otherwise Mail composes a reply to the wrong message. Sometimes it's the message previously highlighted, and other times it's the message above or below the newly-selected message. (There seems to be a lag between the selection in the NSTableController and the underlying array controller.) This is intermittent but frequent with as few as 1,000-2,000 messages in the inbox on a Mac Pro with 64GB memory, and a retina iMac with 32 GB.
I used to see a similar delay in response with AppleMail on a 2010 Mac Mini running on a spinning external drive. As a fast touch typist, I could get ahead of the machine. I have not noted it with my new 2018 Mac Mini running on a solid-state drive, so I suspect what made the latency long enough to cause noticeable mistakes was the slow response of the spinning drive. It also means Apple Mail runs relatively slowly.
 


If you are having trouble sending email with Apple Mail when sending only Bcc: it may be because of a change in Apple’s protocol.

I noticed this morning that suddenly when I tried to send email with all names in the Bcc: space and no names in the To: space the emails would not send. The same problem existed on my wife's Mac with a different OS as well as on the iPhone when on cellular only, so I knew it was not my network. Up to now a name in the To: space has not been required by Apple Mail although in the past I have encountered at least one other email program that required it.

I had a long workout with an escalated Apple tech who ultimately tried it on his Mac and had the same problem. He’s not sure if it’s a glitch or if it’s a change in protocol. He is sending the case to engineering and will call me back.

For now, always put one name in the To: box. I’ll post when I hear from the tech.
 



If you are having trouble sending email with Apple Mail when sending only Bcc: it may be because of a change in Apple’s protocol. I noticed this morning that suddenly when I tried to send email with all names in the Bcc: space and no names in the To: space the emails would not send. The same problem existed on my wife's Mac with a different OS as well as on the iPhone when on cellular only, so I knew it was not my network. Up to now a name in the To: space has not been required by Apple Mail although in the past I have encountered at least one other email program that required it.

I had a long workout with an escalated Apple tech who ultimately tried it on his Mac and had the same problem. He’s not sure if it’s a glitch or if it’s a change in protocol. He is sending the case to engineering and will call me back.

For now, always put one name in the To: box. I’ll post when I hear from the tech.
I had exactly the same experience for the first time yesterday, in Mail on my iPhone. Adding myself in the "To:” field worked.
 


If you are having trouble sending email with Apple Mail when sending only Bcc: it may be because of a change in Apple’s protocol.
Did they fix it already? I just tried three cases: sending from an Exchange account, a mac.com account, and a Gmail account. All worked with only an address in the BCC field (to me at various other accounts).

This is macOS 10.14.6 with Apple Mail.
 


The original e-mail message standard (RFC 822) requires that at least one destination (To, Cc or Bcc) appear in the message header. If a mail server strips Bcc and the other destinations (To and Cc) are not present, then one of them must be populated with something.

For this reason, many (at one time, all) mail servers would insert an "Apparently-To" header in any message where To and Cc are not present, populating it with data from the SMTP "envelope" (the out-of-band data that the protocol uses to determine how to forward the message).

In 2001, the standard was upgraded (RFC 2822) and this requirement was relaxed. Destination headers are now optional, but there are probably many mail servers and clients that treat them as mandatory, maybe for backward compatibility (although one would hope that nobody is still running a server based on a standard that was obsoleted 18 years ago) and maybe because there's no desire to "fix" something that is working.

Either way, you should always include a To: header, even if your mail client doesn't require one. Due to the fact that many mail servers will insert an Apparently-To header, you run the risk of accidentally leaking one or more of the addresses on your Bcc list if you don't. Depending on your circumstances, this could be a bad thing.
 


Did they fix it already? I just tried three cases: sending from an Exchange account, a mac.com account, and a Gmail account. All worked with only an address in the BCC field (to me at various other accounts). This is macOS 10.14.6 with Apple Mail.
Just tried it, and it hasn't been fixed. David, thank you for the input.
 


Ric Ford

MacInTouch
Just tried it, and it hasn't been fixed. David, thank you for the input.
Ken, are you using iCloud for email? This seems like something that's on the server side, rather than an app or OS update, if I'm understanding correctly.
 


Ken, are you using iCloud for email? This seems like something that's on the server side, rather than an app or OS update, if I'm understanding correctly.
I've tried it with Yahoo, iCloud, AOL and Verizon accounts. (Verizon uses AOL servers). The Verizon account is a POP account, not that it matters for sending. The result is the same with all of them. This is on a 2015 iMac running macOS 10.14.6. It also occurs on a 2015 iMac running El Capitan, as well as my iPhone with Wi-Fi turned off.

I agree with you that it's on the server side.
 


If you are having trouble sending email with Apple Mail when sending only Bcc: it may be because of a change in Apple’s protocol.
... Viewing the actual SMTP transaction logs is the fastest and most accurate way to diagnose and resolve what is happening here.

Anyone with this problem should go to the Window menu in Apple Mail, and choose Connection Doctor. Enable "Log Connection Activity", and then view the logs for when there is a failed delivery attempt and provide the log information here.
 


Ric Ford

MacInTouch
I can't correlate these reports of "BCC:" problems directly to recent changes required to major email server software to patch critical vulnerabilities, but I do wonder if there might be similar server updates involved here.
ZDNet said:
Millions of Exim servers vulnerable to root-granting exploit
Millions of Exim servers are vulnerable to a security bug that when exploited can grant attackers the ability to run malicious code with root privileges. All Exim servers running version 4.92.1 and before are vulnerable, the Exim team said in an advisory this week. Version 4.92.2 was released on Friday, September 6, to address the issue.
Bleeping Computer said:
Critical Exim TLS Flaw Lets Attackers Remotely Execute Commands as Root
The Exim mail transfer agent (MTA) software is impacted by a critical severity vulnerability present in versions 4.80 up to and including 4.92.1. The bug allows local or unauthenticated remote attackers to execute programs with root privileges on servers that accept TLS connections.

... In July, a similar vulnerability tracked as CVE-2019-13917 and impacting Exim 4.85 up to and including 4.92 was patched with the release of 4.92.1, a flaw enabling local or remote attackers to execute programs with root privileges for servers with unusual configurations.

Previously, in early June, yet another critical security issue tracked as CVE-2019-10149 allowed hackers to remotely exploit MX servers running Exim 4.87 to 4.91 for certain non-default configurations, while local attackers would be able to exploit all servers regardless of their configurations.

One week later, on June 13, attackers started targeting vulnerable Exim servers gaining permanent root access via SSH, right after roughly 70% of all Exim mail servers installed the patched 4.92 version against the CVE-2019-10149 flaw, as found by RiskIQ Leading Threat Researcher Yonathan Klijnsma.

On June 17, Microsoft issued a warning regarding a Linux worm that was actively targeting Azure Linux VMs running vulnerable Exim versions.
 


A new OS, and this developer is missing in action, again: Looking for a Catalina release for Mailhub by Dervish Software. For the last two OS releases, the method has been to stealth-release the update on Twitter a short while after the OS is available. Despite numerous attempts to reach Dervish, there are no replies, and discussion threads on their website are blank. The company is still in business in the UK.

All this aside, it is a brilliantly useful program, and I've not found its functionality elsewhere. Any news, or suggestions for this kind of message autofiler?
 


I have a problem that I cannot seem to solve. I have a bunch of signatures that I have created in Apple Mail. I don't need most of them any more. I cannot seem to delete them. I disassociate them from all accounts, then delete them. I get the confirmatory 'are you sure you want to delete, can't be undone, yadda yadda' dialog box, and click OK. But then when I relaunch Mail, they are back like the proverbial booger you just can't seem to flick off your finger. Any suggestions?
 


I have a bunch of signatures that I have created in Apple Mail. I don't need most of them any more. I cannot seem to delete them.
On each and every Mac that is signed into the same iCloud account (since iCloud is probably responsible for this issue), please navigate to:

/Users/username/Library/Mail v#/MailData/Signatures

Remove all files within the Signatures folder and empty the Trash. Then reboot. Hopefully that'll kill off every signature in Apple Mail.

After rebooting, you can carefully create a fresh signature in Mail, which likely will sync across all your Macs.
 


On each and every Mac that is signed into the same iCloud account (since iCloud is probably responsible for this issue), please navigate to:

/Users/username/Library/Mail v#/MailData/Signatures

Remove all files within the Signatures folder and empty the Trash. Then reboot. Hopefully that'll kill off every signature in Apple Mail.

After rebooting, you can carefully create a fresh signature in Mail, which likely will sync across all your Macs.
Unfortunately, no dice. By the way, my signatures have always been different on my two computers. They have never sync'ed across iCloud. I deleted everything in the folder, rebooted, created new signatures, quit Mail, relaunched Mail, and, voila — nothing that I created stuck, and there are no signatures at all now. Frustrating. It seems almost as if Mail doesn't have permissions to write to that folder.

My work laptop has the correct signatures that I want. So I copied all the .mailsignature files along with the AllSignatures.plist file from that computer to my home computer and it worked. Unfortunately I still cannot add or remove signatures on my home computer until I figure this out.
 


Save the text of any signatures you want to keep in a Note.

Go to
~/Library/Containers/com.apple.mail
and create a new folder containing all the existing files and folders in that directory....

Restart Mail and you can re-set all your preferences and signatures.
 


I am looking for an alternative to Apple Mail. I'm currently using Thunderbird but find that I like Postbox better. Thus far, I've only used up to version 5 because I like the idea of SpamSieve compatibility.

However, it has one problem that's driving me absolutely nuts: the address book autocomplete is strictly alphabetical. Unlike Thunderbird, Postbox 5 does not take frequency of usage into account. This necessitates more typing.

My question for Postbox users: SpamSieve compatibility aside, has version 7 improved this aspect of message composition compared to version 5?

I'd try it myself (since I have a lifetime license) but I don't want to cause any problems with data incompatibility in the event I want to go back to version 5. The account in question is IMAP, so at least mail importation is not a concern.
 


...has [Postbox] version 7 improved this aspect of message composition compared to version 5?
It seems I have inadvertently answered my own question. The answer, sadly (unless version 7 is inordinately slow in learning, which seems unlikely) is "no."

But the story of how I found out is interesting: A friend forwarded me an HTML-formatted email that Comcast had sent him, to which I replied using version 5. As soon as I pressed Command-R, I was surprised to be confronted by an alert message which began:

emails.xfinity.com:443 uses an invalid security certificate.
The certificate is not valid because the issuer certificate is not trusted.

I was curious enough to view the Comodo-issued certificate, the date of which was still valid. But at the top of that screen, there was bold print:

Could not verify this certificate for unknown reasons.

That struck me as a bit ominous. Most likely, it was revoked for some reason, but [Postbox] version 5 did not know the reason for the error. I would have expected it to be able to communicate a simple revocation.

I replied to the same message in Thunderbird, and no such error appeared. Clearly, this, then, is a side effect of version 5 not having been updated in quite some time. Despite my love of SpamSieve, it was time to upgrade [Postbox]. Although doing so did not fix my pet peeve, the user interface is much cleaner and just nicer overall.
 


A new OS, and this developer is missing in action, again: Looking for a Catalina release for Mailhub by Dervish Software. For the last two OS releases, the method has been to stealth-release the update on Twitter a short while after the OS is available. Despite numerous attempts to reach Dervish, there are no replies, and discussion threads on their website are blank. The company is still in business in the UK.
All this aside, it is a brilliantly useful program, and I've not found its functionality elsewhere. Any news, or suggestions for this kind of message autofiler?
Happy to report that there is going to a new release of Mailhub for Catalina. The developer has made a beta available, and you can find details here in their forum discussion:

 


Has anyone else experienced this: Before Catalina, using the normal (?) Mail column view with Mailboxes, header digests, and a message pane, deleting a selected message by clicking on the header digest and then hitting Delete could be undone with a Command-Z (as still indicated in the Edit menu) — but under Mail 13.0 in Catalina, Command-Z after deleting a message does nothing at all. I have Preferences -> Viewing -> Move discarded messages into: set to Trash, as I am certain I did pre-Catalina.
 


Has anyone else experienced this: Before Catalina, using the normal (?) Mail column view with Mailboxes, header digests, and a message pane, deleting a selected message by clicking on the header digest and then hitting Delete could be undone with a Command-Z (as still indicated in the Edit menu) — but under Mail 13.0 in Catalina, Command-Z after deleting a message does nothing at all. I have Preferences -> Viewing -> Move discarded messages into: set to Trash, as I am certain I did pre-Catalina.
I have the same problem in Mojave. Typing Command-Z after deleting a message appears to undo the deletion, but the message that reappears in the Inbox is blank. The actual message remains in the Trash, and the only way to undo the deletion is to select the message in the Trash and move it from the Trash back into the Inbox.
 


I have the same problem in Mojave. Typing Command-Z after deleting a message appears to undo the deletion, but the message that reappears in the Inbox is blank. The actual message remains in the Trash, and the only way to undo the deletion is to select the message in the Trash and move it from the Trash back into the Inbox.
Bizarre - I have a different, and still incorrect, behavior on fully-updated Mojave. Command-Z restores two versions of the deleted message to the current mailbox. (On-my-Mac mailbox, in "classic" view.) One of the messages is good, the other is blank. The blank message line has a slightly-greyed font. Mail has been doing this for a while, perhaps since the Mojave upgrade, and it is just one of the huge pile of stinking bugs that is Apple Mail. I have gotten used to them, and just work around them.
 


I have the same problem in Mojave. Typing Command-Z after deleting a message appears to undo the deletion, but the message that reappears in the Inbox is blank. The actual message remains in the Trash, and the only way to undo the deletion is to select the message in the Trash and move it from the Trash back into the Inbox.
It works as expected on my system. I tried several ways of deleting messages and was always able to recover them with the undo command. However, this is on a 10.15.1 Beta version. Perhaps you can expect to have this bug fixed by the time the next update comes out.

Thinking back on how this behaved in Mojave, I cannot recall exactly any instance when I had to undo a message deletion in macOS 10.14. Sorry.
 


I have the same problem in Mojave. Typing Command-Z after deleting a message appears to undo the deletion, but the message that reappears in the Inbox is blank. The actual message remains in the Trash, and the only way to undo the deletion is to select the message in the Trash and move it from the Trash back into the Inbox.
Hmm. Not quite the same, and I recall having it occur occasionally before Mojave. But by and large, it was not an issue for me. Are you referring to an IMAP account, a POP3 one, or both?
 


After updating to Catalina, Apple Mail crashes several times per day. I am forwarding the dump information to Apple. Perhaps they can sort it out.
 


Hmm. Not quite the same, and I recall having it occur occasionally before Mojave. But by and large, it was not an issue for me. Are you referring to an IMAP account, a POP3 one, or both?
I'm having the same problem in Mojave as Cathleen M.: Delete a message (from an IMAP account), undo the delete, and the message shows as being back in the Inbox, along with the preview of the first 2 lines of text (an option I chose in preferences). But if I open that message, the body is blank; and if I check the Trash folder, the message is still there – when I drag it to the Inbox, there is only one message in the Inbox, and it opens normally.

I seem to remember that if I wait a period of time, the message will eventually be readable in the Inbox. But once I figured out I could just drag it back from the Trash, I do that, so I don't need to dip into my meagre cache of patience.
 


Hmm. Not quite the same, and I recall having it occur occasionally before Mojave. But by and large, it was not an issue for me. Are you referring to an IMAP account, a POP3 one, or both?
This particular account is a POP3 account. I have an IMAP account that works normally in Mojave (Command-Z functions as it should). Interestingly, I just discovered that if I delete an email in POP3, undo the delete (generating a blank message in the Inbox), select a different mailbox, and then go back to the Inbox, the mail is now intact in the Inbox, though there is a second copy of that email in the Trash.
FWIW, on my husband's computer (running High Sierra) Command-Z works for both IMAP and POP3, except that it leaves an extra copy of the email in the trash.
 


I have the same problem in Mojave. Typing Command-Z after deleting a message appears to undo the deletion, but the message that reappears in the Inbox is blank. The actual message remains in the Trash, and the only way to undo the deletion is to select the message in the Trash and move it from the Trash back into the Inbox.
I see this, too. However, opening any other mailbox (I use the VIP one) magically restores the content of the un-deleted message.
 


I see this, too. However, opening any other mailbox (I use the VIP one) magically restores the content of the un-deleted message.
I have seen such behavior several times, but when I tried to reproduce it today in what I think is the current Mojave, I was able to get the emails back by typing Command-Z. My recollection is that it was only for POP email, not for IMAP accounts.
 


I have the same problem in Mojave. Typing Command-Z after deleting a message appears to undo the deletion, but the message that reappears in the Inbox is blank. The actual message remains in the Trash, and the only way to undo the deletion is to select the message in the Trash and move it from the Trash back into the Inbox.
You can also restart Mail, and the actual email shows up as it's supposed to. This may be an ongoing bug, in my opinion.
 


This particular account is a POP3 account. I have an IMAP account that works normally in Mojave (Command-Z functions as it should). Interestingly, I just discovered that if I delete an email in POP3, undo the delete (generating a blank message in the Inbox), select a different mailbox, and then go back to the Inbox, the mail is now intact in the Inbox, though there is a second copy of that email in the Trash.
FWIW, on my husband's computer (running High Sierra) Command-Z works for both IMAP and POP3, except that it leaves an extra copy of the email in the trash.
I have a couple of POP3 accounts, and their mail can be trashed, and then recovered ok, using Command-Z. They are readable immediately after recovering, and the only odd thing is a copy of the mail remaining in the trash.

Looking at Mail prefs, under Mailbox Behaviors, I have it set to auto-delete trashed items after 1 day. Sometimes that works after a day, and sometimes after a few days. IMAP (Gmail) accounts are odd. Trashing mail with the delete button works, and Command-Z recovers it ok. A copy does not remain in the trash. However, if I trash a mail, then look in the trash folder, the mail simply can no longer be recovered using Command-Z (dragging works though). The Mailbox Behavior shows that I have selected the (Gmail)/Trash mailbox and 1 month before auto-erasing. This is on a current version of Mojave, 2017 iMac, 27". Perhaps try rebooting your machine to see if anything changes.
 


It seems I have inadvertently answered my own question. The answer, sadly (unless version 7 is inordinately slow in learning, which seems unlikely) is "no."
I am extremely pleased to report that, in actuality, the answer to my above question as to whether Postbox 7 does a better job with autocomplete (as compared to version 5) has changed to yes, as I have discovered today!

It seems that it just took the program a while to learn my patterns. But what took three keystrokes last night takes only one as of today.
 


Ric Ford

MacInTouch
Here's a problem with iOS 13 Apple Mail – I haven't tested it in older, unsupported iOS versions and I don't use Apple Mail on my Mac, but it's something to beware of.

The scenario is this: you need to follow up on an email you sent, so you choose Reply All to a BCC copy in your Inbox. This seems to work fine, selecting the other recipient's email address and letting you compose and send the follow-up reply.

Except... it sends not from your original email address (which is also the one BCC'd back to yourself) but from a completely random different email address!

Not cool.

#applequality
 


I have had to stop using Postbox (as of version 7.0.8) because of weird problems with regard to spontaneous font formatting changes that can happen when I try to reply inline to a received message.

It hasn't been worth my time to try to figure out why the font suddenly changed just because I started a new paragraph. Hopefully future versions will fix this but, for now, I'm done with it.

The latest version of Thunderbird has its own problems (of which the text color picker, which hasn't worked since before version 68.x, is a shining example) but it exhibits none of the font-changing weirdness of Postbox.
 


Amazon disclaimer:
As an Amazon Associate I earn from qualifying purchases.

Latest posts