71–80 of 314 posts
Earlier quoted context omitted.
This is probably no help to you, but since you're doing this already, you may know. Is it feasible to self host your own email server but then use something like Mailgun for SMTP?
For what purpose?
It's gonna be really hard. I work at a hosting company and our staff has to work constantly to make sure people's servers get taken off of spam blacklists, or IP blocks of ours need to get removed, etc. There's a lot of stuff to navigate out there, basically kludges that have been put in place because email is just such a terrible, insecure system. I'm sure if you're willing to put in the effort you can do it. But fr…
Are the IPs being added to blocklists without ever having sent spam?
Or sometimes your IP will just get caught when a spam company decides to spam flag an entire block of IPs.
I think if OP keeps at it, they will find that it's not worth the hassle and for a very reasonable amount of money they could have just had a personal email server where someone else deals with the headaches.
Of course, again, I work for a hosting company so I may be biased here but I'd probably be saying the same thing even if I didn't.
I did almost exactly what you describe and it works flawlessly, but I only send a small volume of mail (my own). Digital ocean droplet $10 a month, but it would run on a $5 one if you don't also have caldav/sftp/kerberos/vpn/etc there like me. Fun Fact: Microsoft Exchange has no native support for DKIM and tons of business run that in house, often on 'business class' connections without correct reverse IP records.
I don't know whether OP uses a home connection, but that makes a big difference. It has some pros and cons:
A VPS (with its dedicated IP address):
- Usually has a good reputation, though you might have bad luck. Switch early on when you notice this. Doing it later just nullifies any trouble you had building its reputation.
- Is hosted somewhere in the cloud. (I used to hate the term "the cloud" but it's actually pretty apt and funny if you start seeing it as "they have no idea where their shit is and who has access to it, both physically and network traffic".)
Hosting at home:
- Might be trouble with your ISP if you don't live in a country with net neutrality and port 25 is closed.
- Gets you a lower reputation score by default, so it takes slightly longer to build.
- Gives you full access control over your email.
Earlier quoted context omitted.
Why would other MTAs have a buff against Qmail? I'm using maradns for DNS but I respect djb's software a lot. I'm using his publicfile as an httpd. I have already added my domains in google's postmaster tools. So far it hasn't helped much
One thing I learned from my spam filter's logs is that sending email in a slightly weird way is great way to marked as spam. I used to receive a few thousand emails a month that didn't have a Date header - all spam - which is strictly required by RFC2822 but sometimes allowed to be absent. amavis-new easily and correctly detected them.
It's absolutely possible to run an email server in 2016 and I encourage anyone capable to do so! Email is one of the bastions of the decentralised Internet and we should hang on to it. Every day more and more people are moving to Gmail/Hotmail/Outlook and while I do understand the reasons, it also puts more and more power into the hands of these providers and the little guy (us) gets more screwed (like marked as junk…
Burn how do you ensure your mails aren't tossed in the spam box of the big ones?
No, not really. It's a constant battle to get delisted from spam blacklists and your site keeps popping back up. Even most companies don't bother with it anymore.
This is a little bit like "correlation is not causation". Companies are moving a lot of stuff to the 'cloud', and email is just one of the services that goes with it. It's simply cost-saving to not have dedicated IT personnel. Even if hosting your own mail server is easy, you need someone who takes care of it every now and then (disk full, adding users, blacklist incident once a year, etc.).