- WLUG - wlug.mailman3.com

Re: Keith's mail issue

by Dick Goodman

This is all analogous to what I use successfully for my wife. To your points: 1) skip the include if you like. My wife has aliased her mail on several domains to Google so she can mail from her phone I only provide her POP not IMAP. I forward her incoming stuff (successfully) to Gmail with Procmail 2) I appreciate that everything worked for 20 years. It did here also, until the last 2 years when Google and Yahoo (who now also does mail for AOL and Verizon) started changing the rules for what they would accept. Took me months. Still issues with Yahoo. Have read they don't follow the standards. 3) You must have an "a:" section in your spf record, it is the only way to tell Google what your valid server(s) is/are. It doesn't matter what you have done with GoDaddy. Also, despite what most documentation says, Google will NOT accept an "ipv4:" section instead of "a:' 4) Can't comment further without seeing what Google's bounce messages look like At 10:27 PM 5/30/2026, Keith Wright via WLUG wrote: >Dick Goodman via WLUG <wlug(a)lists.wlug.org> writes: > > > >> I already have an SPF record which says: v=spf1 mx ~all, what's > > >> wrong with that? > > > > LOTS. It doesn't specify a valid server. try this > > > > "v=spf1 a:fcx2.keithdiane.us include:_spf.google.com ~all" > >I don't like to copy stuff I don't understand, so I have been reading >RFC's and log files. I don't see why "a:fcx2.keithdiane.us" would >help, since I already told the (godaddy) namesever > > mx @ fcx2.keithdiane.us. (Priority: 10) 1 Hour > >but it seemed harmless, so I put it in. No visible change. > >On the other hand "include:_spf.google.com" seems just wrong. I am >not trying to get gmail.com to send my mail, I want them to accept it. > >I am thinking that all those many various messages that say "gmail.com >requires DKIM, SPF, TLS, DMARC, etc. are a pile of crimson herring. >What they really mean is "gmail.com" does not want anyone else relaying >mail from gmail, no matter how. > >I notice that WLUG uses GNU Mailman, and that mail is modified, both >body and headers, and that seems to work. I have, for 20 years, just >been relaying mail unchanged. Maybe that simply does not work with the >corporate monopoly internet. Maybe I need to use Mailman or something >similar, so that the envelope MAIL FROM is rewritten to <mymail.org>. > >GNU Mailman seems rather complex for that one thing. Is the wizard who >set that up here on the WLUG list, or did you just delegate that? Is >there a simpler way? > > > If anybody cares what I have been working on, part of it is on this page: > > > > http://www.nerflings.org/none/fcs/vpsmove.html#gmail > > > > If you can answer any of the quesions at the end of that page you may be > > eligible to apply to be my hero. > > -- Keith >_______________________________________________ >WLUG mailing list -- wlug(a)lists.wlug.org >To unsubscribe send an email to wlug-leave(a)lists.wlug.org >Create Account: https://wlug.mailman3.com/accounts/signup/ >Change Settings: >https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ >Web Forum/Archive: >https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/message/5MQSY…

May 31, 2026

Re: Keith's mail issue

by Keith Wright

Dick Goodman via WLUG <wlug(a)lists.wlug.org> writes: > >> I already have an SPF record which says: v=spf1 mx ~all, what's > >> wrong with that? > > LOTS. It doesn't specify a valid server. try this > > "v=spf1 a:fcx2.keithdiane.us include:_spf.google.com ~all" I don't like to copy stuff I don't understand, so I have been reading RFC's and log files. I don't see why "a:fcx2.keithdiane.us" would help, since I already told the (godaddy) namesever mx @ fcx2.keithdiane.us. (Priority: 10) 1 Hour but it seemed harmless, so I put it in. No visible change. On the other hand "include:_spf.google.com" seems just wrong. I am not trying to get gmail.com to send my mail, I want them to accept it. I am thinking that all those many various messages that say "gmail.com requires DKIM, SPF, TLS, DMARC, etc. are a pile of crimson herring. What they really mean is "gmail.com" does not want anyone else relaying mail from gmail, no matter how. I notice that WLUG uses GNU Mailman, and that mail is modified, both body and headers, and that seems to work. I have, for 20 years, just been relaying mail unchanged. Maybe that simply does not work with the corporate monopoly internet. Maybe I need to use Mailman or something similar, so that the envelope MAIL FROM is rewritten to <mymail.org>. GNU Mailman seems rather complex for that one thing. Is the wizard who set that up here on the WLUG list, or did you just delegate that? Is there a simpler way? > If anybody cares what I have been working on, part of it is on this page: > > http://www.nerflings.org/none/fcs/vpsmove.html#gmail > > If you can answer any of the quesions at the end of that page you may be > eligible to apply to be my hero. -- Keith

May 30, 2026

Keith's mail issue

by Dick Goodman

>>I already have an SPF record which says: v=spf1 mx ~all, what's wrong with that? LOTS. It doesn't specify a valid server. try this "v=spf1 a:fcx2.keithdiane.us include:_spf.google.com ~all" Dick

May 21, 2026

Meeting Tomorrow!! May 21st. Topic: why does gmail hate me?

by Keith Wright

Tim Keller via WLUG <wlug(a)lists.wlug.org> writes: > Hey Everybody! > > We've got a meeting tomorrow! > Time: 7pm > Location: Technocopia, 44 Portland St. Worcester MA. > Virtual Location: https://meet.jit.si/WlugMA I hope to page in from my own virtual location. > Topic(s): > > I suspect we'll also talk about copy.fail and the other serious LPE's that have been > discovered lately using AI tools. I didn't know what that is, so I googled. I am glad the AI has finally passed its Language Proficiency Exam and joined Lambda Pi Epsilon. (Just joking. I know you are referring to CVE-2026-31431, which is easier to remember since it is so close to $\pi$.) Too damn many TLAs! Google also turned up this minority report: https://www.helpnetsecurity.com/2026/05/18/problems-with-ai-assisted-vulner… If anybody cares what I have been working on, part of it is on this page: http://www.nerflings.org/none/fcs/vpsmove.html#gmail If you can answer any of the quesions at the end of that page you may be eligible to apply to be my hero. -- Keith

May 20, 2026

Meeting Tomorrow!! May 21st. Topic: Cisco hardware hacking / Claude

by Tim Keller

Hey Everybody! We've got a meeting tomorrow! Time: 7pm Location: Technocopia, 44 Portland St. Worcester MA. Virtual Location: https://meet.jit.si/WlugMA Topic(s): Alex will talk about hacking Cisco hardware. Jenson will then talk about how he's using Claude in his workflow these days. I suspect we'll also talk about copy.fail and the other serious LPE's that have been discovered lately using AI tools. As usual it'll be a ruckus affair and lots of fun! After the meeting we'll head off for dinner amd keep the conversation going. Later, Tim.

May 20, 2026

May meeting moved to 21st.

by Tim Keller

Hey Everybody, I've got a scheduling conflict for the 14th, so this month's meeting will be on the 21st. Thanks, Tim.

May 5, 2026

Re: email imap fail2ban --- was Reminder!!!

by John Stoffel

>>>>> "Keith" == Keith Wright <kwright(a)keithdiane.us> writes: > John Stoffel via WLUG <wlug(a)lists.wlug.org> writes: >>>>>>> "Keith" == Keith Wright via WLUG <wlug(a)lists.wlug.org> writes: >> >> Sorry for the delay Keith, new job, life and such all got in the way. > I'm OK without a job, but it would be nice to have a life. Hahahahah! Touche' Keith! >> 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. > Yes. I did that last week. Great, are you seeing the errors still? > See you in a few hours, jit.si gods willing. Hope to see you there!

April 9, 2026

Re: email imap fail2ban --- was Reminder!!!

by Keith Wright

John Stoffel via WLUG <wlug(a)lists.wlug.org> writes: >>>>>> "Keith" == Keith Wright via WLUG <wlug(a)lists.wlug.org> writes: > > Sorry for the delay Keith, new job, life and such all got in the way. I'm OK without a job, but it would be nice to have a life. > 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. Yes. I did that last week. See you in a few hours, jit.si gods willing. -- Keith

April 9, 2026

Re: email imap fail2ban --- was Reminder!!!

by John Stoffel

>>>>> "Keith" == Keith Wright via WLUG <wlug(a)lists.wlug.org> writes: Sorry for the delay Keith, new job, life and such all got in the way. > John Stoffel via WLUG <wlug(a)lists.wlug.org> writes: >>>>>>> "Keith" == Keith Wright via WLUG <wlug(a)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.

April 9, 2026

WLUG Meeting Tomorrow Thursday (4/9/2026) Topic: Ubuntu FIPS for you!

by Tim Keller

We've got a meeting Tomorrow! (4/9/2026) Date & Time: 4/9/2026 @ 7PM Location: Techncopia, 44 Portland St. Worcester MA 01453 Virtual Location: https://meet.jit.si/WlugMA Topic: Ubuntu FIPS for you! Speaker: Alex Wlug member Alex will be showing off his Ubuntu laptop running in full FIPS mode . What it does, how it does it and how you can do it too! We'll also be talking about the new website, merch and other fun stuff I'm sure! As usual, we'll head off for dinner afterwards and keep the conversation going. I hope to see you there! Tim. -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

April 8, 2026