1 |
On Tuesday, 25 December 2018 17:49:36 GMT Grant Taylor wrote: |
2 |
|
3 |
[Big snip...] |
4 |
|
5 |
> I think there may be more subtle things than you might be aware of. |
6 |
> I say that based on the context of your email. You are asking very |
7 |
> reasonable questions. But they seem fairly new to the process. As |
8 |
> such, I think some of the things along the way are going to surprise you. |
9 |
> |
10 |
> With that in mind, please allow me to make some recommendations: |
11 |
> |
12 |
> 1) Use a (sub)domain that is globally registered. |
13 |
> 2) Use a Let's Encrypt SSL certificate on the globally recognized FQDN. |
14 |
> 3) Use split DNS for internal / external resolution. |
15 |
> 4) I think forwarding might be the slightly lesser of the evils to get |
16 |
> email from your ISP to your server. But that requires external |
17 |
> accessibility to your email server. - I say this because fetchmail (et |
18 |
> al) functionally retrieves email and re-injects it as SMTP to your local |
19 |
> server. Thus forwarding at least doesn't switch protocols. |
20 |
> |
21 |
> Finally, postfix / dovecot / et al, make little difference in my |
22 |
> opinion. I think you could easily substitute different daemons in their |
23 |
> place. IMHO there is quite a bit more to think about than which of the |
24 |
> specific daemons you will run or how to configure them. Rather the |
25 |
> specific daemons fall in line after you have the answers to all the |
26 |
> other questions and a plan of action. |
27 |
|
28 |
That's been my difficulty all along: understanding what I need to do, before |
29 |
trying to set it up. Your recommendations are a great help in that, together |
30 |
with the considerable detail you offered. |
31 |
|
32 |
Many thanks for all the time and trouble you put into your reply, Grant. I am |
33 |
grateful, and you can be sure I'll act on it. |
34 |
|
35 |
Thanks again. |
36 |
|
37 |
-- |
38 |
Regards, |
39 |
Peter. |