| 1 |
On 11/10/2016 06:59 AM, Stroller wrote: |
| 2 |
> |
| 3 |
> I appreciate mine may be a very naive view of the problems of mail |
| 4 |
> hosting, but someone who wants to host mail for themselves is coming |
| 5 |
> at things from a very different position than you are. |
| 6 |
> |
| 7 |
|
| 8 |
As long as you don't have customers, running a mail server can even be |
| 9 |
fun, but the initial learning curve is bonkers. Before you can do |
| 10 |
anything, you need to get your IP address whitelisted or added to a |
| 11 |
feedback loop with all of the major providers. You'll need reverse DNS |
| 12 |
to match your 'A' record, and you should make sure (use mxtoolbox.com or |
| 13 |
something like that) that your IP isn't blacklisted anywhere. |
| 14 |
|
| 15 |
After that, all you have to do is set up postfix, dovecot, and amavisd. |
| 16 |
Which ultimately comes down to about 100 lines of configuration... but |
| 17 |
before you can do it, you need to understand the 25,000 lines of |
| 18 |
configuration that you don't need and why. All of the HOWTOs are bad, |
| 19 |
and you need to know how all of the pieces interact if you want to have |
| 20 |
a chance in hell of debugging delivery issues. That can take weeks. |
| 21 |
|
| 22 |
If you want to give it a shot, try to do it one step at a time. Start |
| 23 |
with postfix delivering to local (system account) mailboxes with no spam |
| 24 |
filtering. Then add the spam filtering (postscreen, amavis). Then add |
| 25 |
the virtual accounts. Then add dovecot. Then make postfix talk to |
| 26 |
dovecot. Then add sieve support. Etc. Your postfix configuration will be |
| 27 |
tiny at the start (you still need to read through man 5 postconf, |
| 28 |
though) and that way you'll only need to learn the parts that you're |
| 29 |
adding. And if it stops working, you know what broke it. |
Archives