51–60 of 70 posts
I found it relatively quick to setup and get working. And compared to Google-apps for business, it is free for X amount of users per domain.
Not affiliated to them in any way, just thought I'd share what I've been using recently alongside my main gmail user account.
Why does everyone make these with PHP? Serious question. Maybe it "just works" but all of these projects feel ancient to me because of their stack despite being brand new. Sure as a user it doesn't matter but as the maintainer/administrator I just don't want to deal with it. Modphp? Yuck. We don't always need to use the new new thing all the time but I can't shake the feeling that the same person who runs this is als…
As an example, I run one of the applications mentioned here for several customers in chrooted read-only no-exec environments without fuss. The platform gives me good tools for instrumentation and logging in order to work proactively withever operations issues that arise.
Even if your (or mine) favourite language had a community large enough to develop great webmail tools, very few has a deployment story to match.
They failed to include ProtonMail https://protonmail.ch/ which is actually hosted and secure and probably the closest thing.
Unfortunately this article neglects one of Gmail's strongest features: superb turnkey spam filtering. Anyone with an email address older than 5 years is going to be buried in spam thus will need spam filtering with a super low false positive rate.
I've had my current domain for 10 years, don't run any spam filtering ( just fail2ban ) and I've had fewer pieces of spam than I have fingers.
So whatever you're doing... Stop doing it.
Earlier quoted context omitted.
This is true of any spam filter. You either have it set as too aggressive or you don't. You either put up with spam that gets through or you check your spam box more often. Google's is better than most.
How do I set the google spam filter to be less aggressive?
Earlier quoted context omitted.
How do those affect the amount of spam you receive? I thought they were just to make it less likely your outgoing mail would be marked as spam by someone else.
> I thought they were just to make it less likely your outgoing mail would be marked as spam by someone else. Setting it up can mean that you check these things on the receiving end. Big difference between self-hosting and accepting all e-mails and self-hosting and checking the sender's SPF and DKIM.
That said, it will reduce bounce-back from spam that forges your domain.
Why does everyone make these with PHP? Serious question. Maybe it "just works" but all of these projects feel ancient to me because of their stack despite being brand new. Sure as a user it doesn't matter but as the maintainer/administrator I just don't want to deal with it. Modphp? Yuck. We don't always need to use the new new thing all the time but I can't shake the feeling that the same person who runs this is als…
Projects like this were often started many years ago, back when PHP was the language of choice.
Why almost all of them look like they were made in the 90's?
[0] https://www.indiegogo.com/projects/roundcube-next--2#/story