"Keith" == Keith Wright via WLUG <wlug@lists.wlug.org> writes:
Sorry for the delay Keith, new job, life and such all got in the way.
John Stoffel via WLUG <wlug@lists.wlug.org> writes:
> "Keith" == Keith Wright via WLUG <wlug@lists.wlug.org> writes:
My big project for the past few weeks was begun in a hurry when the company that hosts the VPS that runs both mail and web servers sent me a message saying they are going out of business.
I got another; am sending this mail throught it.
The old SVP ran PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" while the new one "Debian GNU/Linux 13 (trixie)"
Do you run dovecot for IMAP(s) access to your mail? Or do you just deliver it locally and read it using some other mail program?
I log into the VPS and use emacs (rmail-get-new-mail ... ...), which is bound to a single keystroke, to copy mbox file from /var/... to RMAIL in /home/kwright. Diane uses thunderbird on Windows which (I think) uses imap to interact with dovecot on VPS.
Nice! I haven't used rmail is years and years but I have fond memories.
From time to time I use rsync to copy RMAIL@VPS to RMAIL@laptop where I can read it again, write this reply, maybe copy it to thumb drive or web page.
I ask because with Trixie, dovecot was upgraded to v2.4.x and it's a big problem because the configuration language has been changed, and it's not as stable as the old 2.3.x version is, and some features have been pulled.
But that part seems to be working. Whatever Hostinger put in the Debian boot image together with a few "apt install"s of my own, just does it.
Great, I'm happy to hear this. I assume you're wife also has a login on your VPS and she's using that username/password to access her email.
So I'd be careful upgrading. I've been thinking about deployin "Mail-in-box" instead, just to get more spam filtering, and more integration with DNS, DKIM, SPF, rspam, etc.
Doing mail well is a pain.
My current pain is fail2ban, which seems like a good idea but seems to be having a fight with systemd.
I'm using fail2ban and it works great.
I get error messages that seem to indicate I need to install nft (nftables), otherwise fail2ban can put an IPaddr in jail, but that has no effect.
Yes, you need to install a firewall tool so that fail2ban can insert rules to drop packets/connections matching rules. I have both 'nftables' and 'iptables' installed.
There were several web pages that said that Debian 13 could not run fail2ban without special configuration. Either they were just wrong or it was fixed in some 13.N release. (Does anyone know how to see N?) It seemed to install just fine.
I now think there is no N. Debian 13 is one thing, after that the problem is to apt install (and configure) the right versions of postfix, dovecot, fail2ban, and ... ... ...
But now I have learned enough to reach a higher plane of confusion.
LOL! I understand, it's all so complicated. So for fail2ban, I would just do: sudo apt install nftables iptables and then check the logs and see if you still get the same warning. Can you also share your configuration? for example, I have the following: $ sudo fail2ban-client status Status |- Number of jail: 1 `- Jail list: sshd which shows that I have one jail setup for 'ssh' connections. To get more details I do: $ sudo fail2ban-client status sshd Status for the jail: sshd |- Filter | |- Currently failed: 2 | |- Total failed: 276156 | `- File list: /var/log/auth.log `- Actions |- Currently banned: 2 |- Total banned: 43350 `- Banned IP list: 87.251.64.144 80.66.66.70 But if you post the output of your exact log message, I'd be happy to help. Also post your fail2ban config info as well.