Thank you for downloading SpamSieve for Mac from our software portalThe package you are about to download is authentic and was not repacked or modified in any way by us. The software is periodically scanned by our antivirus system. We also encourage you to check the files with your own antivirus before launching the installation.
The download version of SpamSieve for Mac is 2.9.38. The license type of the downloaded application is shareware. This license type may impose certain restrictions on functionality or only provide an evaluation period. SpamSieve antivirus reportThis download is virus-free.This file was last analysed by Free Download Manager Lib 7 days ago.
I am running into increasing problems with spam filters blocking email I send from my personal domain. I checked and see no sign that my domain has been blacklisted. This happens with both new and regularly correspondents, including some I have been working with on writing projects for years. It can happen with gmail or corporate servers, among others. I include a signature with the outgoing mail that includes a link to my personal domain, which is standard procedure for many businesses.Is anybody else seeing this? One theory is that some spam filters may be programmed to block or assign a higher spam rating to emails that include links. Could some spam filters assign a higher spam rating to 'unknown' servers?
This is getting increasingly annoying in trying to run my business as a freelance writer. I use Cablevision/Optimum/Altice, and have found that my mail to AT&T users (including many Bells) bounces. The reason I dug up is that I am using my own server, not Optimum, to send mail, and that makes it bounce, but only with the one company crazy enough to do it that way.
Apr 30, 2018 SpamSieve 2.9.31 For Mac Torrent Crack Download SpamSieve 2.9.31 Cracked is a robust spam filter for major email clients for Mac OSX that gives you back your inbox by bringing powerful Bayesian spam filtering to popular e-mail clients.
I have an alternate account for them with Fastmail, but I don't know why that works. Maybe I have an issue on my own server, which is locked down with DKIM, SPF, and DMARC, but I’m more willing to blame AT&T.I’ve had this issue on ALL IP addresses for years and years. Multiple servers.
No idea how Fastmail gets it through. All you need is one little quirk to make one Email server incompatible with another, and spam filtering offers many opportunities. I used to have a small firm host my web site that offered great personal service, but did something that was incompatible with the practices of a handful of other servers, so I could not receive email from one friend with whom I collaborated on a book. I had to use gmail for him and for some mailing lists which had their own quirks. WIth the new hosting firm, I don't see any obvious patterns - sometimes people receive my mail, sometimes it gets caught in the spam filter.
Some of the issues with outgoing mail can be addressed by having your SMTP server use your ISP's SMTP server as a relay - then people 'out there' see the mail being delivered by a 'legitimate' source rather than as coming from some IP address that may not seem like it should have an SMTP server.I have also had some positive results in configuring proper SPF records for the domains in question - though I once saw a statistic that junk mail actually had a higher rate of properly configured SPF records than non-junk mail. Proper SPF records may limit the use of your domains by bad actors as return addresses for their junk email. I'm sure that there must be some really really good security considerations that the Thunderbird/Mozilla team saw when they decided to pull support for plug-ins. (Not being sarcastic here—I understand how scary it can be to allow literally anyone to distribute plug-ins for an open source platform.)But accepting a Postbox 6 update means losing a number of useful utilities that sets this app apart from other email clients. Losing SpamSieve filtering, in particular, means going back to constant weeding of my inbox and loss of a filtering system that is currently 99.8% accurate in discerning junk from good messages. The kludgy 'Apple Mail drone setup' is a definite 'no, thank you' for me as well.
A quick look shows that Eudora was developed in CodeWarrior 6. There are many.rsrc ResEdit files.I randomly opened two source files and saw many goto and return statements used instead of the more logical if-then-else construct. If the rest of the code has such poor programming practices it's easy to understand why Qualcomm didn't want to upgrade Eudora. I certainly wouldn't want to be burdened with reading and fixing such poor code.I do sparingly use goto, return, and exit. There are times when they make the code more readable than using a proper logical structure. In my opinion neither file's statements were one of those cases. I don't know if anyone else is experiencing this, but I have been finding more and more that friends with Gmail addresses don't get my mail, and then later find that it has been sent to their spam folder.This only happens with email sent to Gmail addresses.
It also happens with my replies to friends with Gmail addresses, which should never happen, and seems to me to break a fundamental rule of spam labelling. In non-Gmail land, if person A sends an email to person B, and person B hits reply and sends a response, person A should be confident of receiving that reply.There are instances of this happening even after a friend has rescued an email from spam and marked it as 'not spam' – Google says Gmail learns from this sort of behavior. Apparently not.Is anyone else experiencing this?
I have some aliases on my Apple account, and it happens with all of them. I refuse to use a Gmail account. I've experienced a slightly different problem, where I get an email from a relative, whose ISP is TDS Telecom, and I reply, only to have TDS reject my reply as spam ( 'blocked due to spam content in the message.
(in reply to end of DATA'), which was patently absurd and infuriating. They opened a trouble ticket with TDS, and we jumped through some hoops, and then the same thing happened again weeks later. Gmail wasn't involved at any point, and I've heard from several relatives about other TDS customers having problems with their email.Today, however, sending and receiving worked with no changes on my end or my relative's.
As it should! Indeed, I have my own DKIM and SPF set up, so that any emails sent from alternate servers are automatically deleted, because my email addresses have been used by spammers.However, AT&T-affiliated sites always reject my email, because Cablevision/Optimum/Altice doesn’t want anyone to use their own SMTP servers with their email service.
Only AT&T sites do this. As far as I can tell, there's nothing I can do about it but have a Fastmail account for those folks; for whatever reason, Fastmail is able to bypass that. I don't know if anyone else is experiencing this, but I have been finding more and more that friends with Gmail addresses don't get my mail, and then later find that it has been sent to their spam folder.This only happens with email sent to Gmail addresses. It also happens with my replies to friends with Gmail addresses, which should never happen, and seems to me to break a fundamental rule of spam labelling.
In non-Gmail land, if person A sends an email to person B, and person B hits reply and sends a response, person A should be confident of receiving that reply.There are instances of this happening even after a friend has rescued an email from spam and marked it as 'not spam' – Google says Gmail learns from this sort of behavior. Apparently not.Is anyone else experiencing this? I have some aliases on my Apple account, and it happens with all of them. I refuse to use a Gmail account. Wow.other people also have problems with mail sent from the Mail app not getting delivered??I have two hughes.net email addresses that are never delivered to relatives with frontier.com and taosnet.com email addresses. They are usually just returned as 'undeliverable' after a couple of days. The returned emails just have undecipherable gibberish on why they are returned.Seems like those email servers may have some type of block set up for hughes.net mail.I had to get an outlook.com email account to send to those relatives.
I discovered why Gmail is sending my iCloud mail to spam.Several years ago I found that my iCloud account’s SMTP server would consistently fail to send mail and continually alternate between asking me to choose another server and asking for my iCloud password, upon which it would tell me my password was incorrect.I tried all kinds of recommended things (deleting preference files, disabling and re-enabling iCloud, etc.) – short of a clean installation of the OS – and finally gave up, using my Earthlink SMTP server, which has always been rock-solid. On macOS starting with whichever release came after iCloud, if the account in Mail is setup as a true iCloud account, the SMTP server is automatic. Under Mail Preferences Accounts Server Settings, there is no place to pick incoming (IMAP) or outgoing (SMTP) servers.
This should work.If the account in Mail is sending or receiving from iCloud but is not actually set up as an iCloud account, then you have to set up the SMTP server yourself. Currently it is smtp.mail.me.com, and if you have 2-factor authentication set up (of any flavor), then you must create an app password. Your regular iCloud password will not be accepted. Also note that when you change the type of two-factor authentication, it wipes out all your app passwords, so you have to regenerate them.For example: my mail account is IMAP to FastMail, but I often send from my @mac.com address. To pass DKIM/SPF etc. I need to send using iCloud's SMTP server, even though in Mail this isn't an iCloud account.
There are two ways to accomplish this: 1) manually configure the iCloud SMTP server and set the account to use it, or 2) Set up the @mac.com address as an Identity in FastMail, configured to use the iCloud SMTP server (with the app-specific password).What's magic is that with the second solution, I can send all my mail to the FastMail SMTP server, and FastMail will automatically reroute the mail through iCloud when needed. That is, the mail sent from @mac.com arrives at FastMail's SMTP, but then FastMail sends it to iCloud's SMTP. So everything works, all the time. I don't think you can purchase macOS Server with any version of macOS you currently use.You can purchase it if you are running macOS 10.14 Mojave, but if you're running an earlier version of macOS, it is not compatible for the initial purchase.However, once you have purchased macOS Server using macOS 10.14 Mojave, you can then use an older OS, go to the Purchased area in the App Store, and it will allow you to download the older version that is compatible with your OS.The steps for someone using OS X 10.11 El Capitan (as per RickCricow's ) are outlined in my MacStrategy article: '.' If you can just purchase the older version straight up in an older OS directly using the App Store, that would be useful to know, but I don't think you can, because I'm sure I've tried to do that in testing some time ago. Perhaps I don't understand your particular use case, but in general you don't absolutely need a static IP address to have your own mail server. I have a registered domain name which gets updated automatically whenever my ISP (cable company) decides to change my IP address.Granted, there is a chance that a few incoming emails could be missed during the short time between when my IP address is changed and the new address is picked up by any clients, but if they try to use the old address during that period the email will fail and be retried later using the new address.
If you're thinking about using the server version of El Capitan as an email server, I suggest considering updating to something newer, since El Cap doesn't seem to be getting security updates any more. I realize that you've been using EIMS, which has not been updated in a long time, but since EIMS is a relatively rare beast on the Internet, it probably isn't a big target for hacking attempts.
In contrast, OS X Server relies on very common open source tools to send and receive mail, so it has a very different risk profile. For example, it uses a legacy version of Postfix (2.1.x) that is no longer supported. If you want to stay on El Cap, I suggest either using a commercial mail server that is kept up to date or using a platform like Hombrew to help keep a traditional, manually configured open source mail stack up to date. Our server constantly has alphabet attacks, trying to find an active email account. In 20-some years, nothing has gotten through EIMS.
We are low profile, and not on anyone's radar.I realize it's old and outdated, but based on what JoseHill says about Mac Server and OS X 10.11, I'm almost wondering if I'm better off running EIMS.Is the day of a non tech professional, an average person (businessperson in my case) running my own mail server over? I have always liked the cost and control I have with my own, vs a service like FastMail or Google. I ran EIMS for many, many years (in the later years on a wonderful Mac Mini G4 that worked perfectly 24x7 for year after year).
I remember those alphabetical dictionary attacks well.With the lack of TLS/SSL encryption (so your communications and passwords are open to capture/snooping), and the misery of trying to configure SPF/DKIM (even with years of serious DNS experience), I finally decided it no longer made sense to spend so much time doing those things and dealing with those problems and switched myself and some associates to FastMail, which has been great. I also evaluated Gmail hosting for one of my friends.
And it really didn't cut it in my assessment. He and another friend now have been running their businesses on FastMail for a few years with excellent success. (They're graphics pros, not techies, and only have a few email addresses, though I have more for my domains.). I was speculating that if the choice were limited to EIMS and El Cap Server, perhaps EIMS wouldn't be as poor of a choice as it might seem at first glance, but the bottom line is that I can't recommend using either EIMS or El Cap Server, especially if the mail server supports an organization or multiple users.If you already were using El Cap Server, I might suggest updating to Sierra Server or High Sierra Server to buy yourself some time, but the clock is ticking on those.
Eventually, you'd need to find another alternative, since Mojave Server drops the mail server admin app. Since you're not already using macOS Server for mail, I wouldn't recommend investing the time in learning a deprecated solution.Of course, current versions of macOS still include open source mail tools, even if the Server app no longer includes a graphical front end to those tools. Unfortunately, unless you already have expertise configuring an open source mail stack, it can be a daunting task to learn how to do it, even though there are some decent Linux/BSD-oriented tutorials on the net. There are some open source attempts to put web/GUI interfaces on top of these tools, but I don't have firsthand experience with them. There is a reason why so many businesses that have dedicated IT staff have found Office 365, FastMail, or G Suite to be attractive solutions.If you don't want to pay the $4+ per user per month that most of the commercial cloud email platforms charge, an often overlooked option is the email service commonly bundled with web hosting plans. For example, a lot of hosting companies include unlimited POP/IMAP/Webmail email accounts as part of their $5/month hosting plans. If I recall correctly, most plans also include CardDAV/CalDAV contact and calendar services.
They're perhaps not quite as reliable as Microsft/Google/FastMail, and their functions are fairly basic, but especially for small organizations with simple needs, they may be adequate.The bottom line, however, is that in the vast majority of business cases, a solution like Microsoft, Google, or FastMail is the easiest, most full-featured approach.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |