| 1 |
On 17/08/20 12:33, Ashley Dixon wrote: |
| 2 |
> On Mon, Aug 17, 2020 at 04:50:43AM +0000, Caveman Al Toraboran wrote: |
| 3 |
>> thoughts on how to maximally satisfy these |
| 4 |
>> requirements? |
| 5 |
> |
| 6 |
> How many concurrent users will be connected to the mail server? How much traffic |
| 7 |
> will the S.M.T.P. server receive (read: how many e-mails arrive on a daily |
| 8 |
> basis)? If you really don't trust your V.P.S. provider, and your mail server is |
| 9 |
> small-ish, you could just skip all the trust issues and buy a cheap Raspberry Pi |
| 10 |
> for £20 or so. |
| 11 |
|
| 12 |
Yup. If you've got mail DNS records pointing at your home server, |
| 13 |
incoming mail shouldn't be a problem and your vps admin can't snoop :-) |
| 14 |
> |
| 15 |
> Running a mail server over a domestic connection presents some issues, such as |
| 16 |
> dynamic I.P. ranges appearing in the Spamhaus blocklist, or some tyrannicalesque |
| 17 |
> I.S.P.s blocking outbound port 25 (S.M.T.P. submission port), but it is possible |
| 18 |
> to have a smooth, self-administered mail server, providing you can put in the |
| 19 |
> time and effort. I have been doing it myself for a few years with Courier and |
| 20 |
> Postfix (although I wouldn't recommend Courier; Dovecot is far superior). |
| 21 |
> |
| 22 |
Can't you tell your server to forward all outgoing mail to your ISP's |
| 23 |
SMTP server? That way, you don't have to worry about all the spam |
| 24 |
issues, and it *should* just pass through. |
| 25 |
|
| 26 |
The main worry for snooping is inbound mail waiting for collection - |
| 27 |
outbound requires a dedicated eavesdropping solution and if they're |
| 28 |
going to do that they can always snoop ANY outgoing SMTP. |
| 29 |
|
| 30 |
Cheers, |
| 31 |
Wol |
Archives