#SPAMSIEVE SPAM FOLDER SERVER SOFTWARE#
#SPAMSIEVE SPAM FOLDER SERVER TRIAL#
#SPAMSIEVE SPAM FOLDER SERVER MAC#
#SPAMSIEVE SPAM FOLDER SERVER WINDOWS#

You can use Time Machine to get at previous versions of the folders in Mail’s data store, and then use the File ‣ Import Mailboxes… command to selectively import them into Catalina Mail. This didn’t make sense to me, and I’ve verified that it’s not the case. Of course, it’s good to make backups anyway.Īpple advisors are apparently telling customers that if Mail data gets lost on Catalina, it can’t be recovered from a Time Machine backup that was made using Mojave. There is no straightforward way to merge restored data in with messages received since the last backup, and also with the live data on the server.

Restoring a backup is difficult because Mail data is constantly changing.

I’m happy to have most of my mail archived outside of Mail.) (See EagleFiler’s Importing Attachments instructions for more about this. So the backup of the local data will necessarily be incomplete. Making a backup is difficult because, even if you set the preference, Mail no longer automatically fully downloads all messages. You may not notice that anything is wrong unless you are looking at the particular mailbox or messages that are affected.īecause the data is synced to the server, problems can propagate to other Macs and iOS devices. These sorts of issues are pernicious because: But my advice is to hold off on updating to Catalina for now.

#SPAMSIEVE SPAM FOLDER SERVER MAC#

I don’t know whether these are due to Mail bugs or to other factors such as problems on the Mac or with the mail server. And eventually this syncs back to the first Mac, where the message disappears as well. If the message was moved to a server mailbox, other devices see the message as deleted. Moving messages between mailboxes, both via drag-and-drop and AppleScript, can result in a blank message (only headers) on the Mac. Updating Mail’s data store from Mojave to Catalina sometimes says that it succeeded, but large numbers of messages turn out to be missing or incomplete.

#SPAMSIEVE SPAM FOLDER SERVER SOFTWARE#

Nevertheless, people contact me because it’s not unreasonable to wonder if third-party software is to blame, and I also hear from people who want a second opinion because what Apple support told them didn’t make sense. (Ironically, one of the bugs I’ve encountered is the inability to delete messages via AppleScript.) And, in fact, most of the damage has occurred without my Mail plug-in even being installed. Thankfully, none seem to be caused by my apps. I’ve heard a bunch of reports of data loss in Apple Mail. You'll be glad you did.I’m working on more posts about the Catalina release, but I wanted to start with a short warning. So if you're going to be using SpamSieve, keep a collection of spam in a separate folder for training before you begin. The instructions suggest fishing these out of your trash, but the problem is that if your spam is in the trash it's almost certainly mixed in with a lot of good messages and now you have to manually tease them apart.

DON'T DO THIS! The training process requires about 600 representative spam messages. The instructions say to delete the messages in your current spam folder before setting up SpamSieve. I do have one complaint: the instructions for the initial training process are a little unclear, and in one place downright misleading. My spam problem is (I almost dare not say this for fear of tempting fate) effectively solved. I've had one false positive during the training process, and the false negatives have rapidly dwindled to 1-2 a day. I've only been using (which is to say training) it for three days, but the situation is already dramatically better than it was before.

#SPAMSIEVE SPAM FOLDER SERVER TRIAL#

I was a little skeptical that it would work much better than Apple's built-in filter, but there's a 30-day free trial so I didn't have much to lose. I was about to throw up my hands in despair and set up a second mail server for Microsoft users, when I decided instead to try SpamSieve. One man's spam is another man's hot deal of the week from his favorite on-line vendor, and the training process can get really annoying if it's not integrated into the client. I could have installed a content-based spam filter on the server, but the problem is that spam is personal. I have clients using this server who use outlook, so I had to disable the FQDN requirement.

#SPAMSIEVE SPAM FOLDER SERVER WINDOWS#

As far as I have been able to determine, it is not possible to configure Microsoft Outlook on Windows to send an FQDN. Unfortunately, it works a little too well. This will prevent many botnet machines from connecting because they tend to not be configured to send a FQDN. One of the ways an SMTP server can cut down on spam is to require clients to connect with a fully qualified domain name (FQDN). I've recently started running my own mail server, so I started tweaking the settings to try to cut down on the processed breakfast meat, and discovered that Microsoft Outlook has a serious bug (what a surprise). I get a ton of spam, and it was starting to overwhelm the filter built in to the OS X mail client.

Spamsieve spam folder server