- WLUG - wlug.mailman3.com

Meeting this Thursday! July 9th, 2026 @7PM, Topic: Rust!

by Tim Keller

Hey Everybody, We've got a meeting this week! Date / Time: Thursday July 9th @7PM Location: Technocopia, 44 Portland St. Worcester MA. Virtual Location: https://meet.jit.si/WlugMA Topic: Rust Programming Language! Long time WLUGer Evan White will be giving a talk on the Rust programming language. Rust recently became a first class citizen in the linux kernel. Designed from the ground up to be type and memory safe it's the new cool kid on the block. Evan will be showing off what he's been doing with rust to wildly extend the functionality of the kobo e-reader. This talk will be oriented towards people who've never used rust before so he'll be getting into the brass tacks and showing us all why we should all abandon our crappy unsafe languages and go all in on rust! As usual after the meeting we'll head out for dinner and keep up the conversation. I hope to see you all there! Tim. -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

July 7, 2026

Reminder! WLUG Meeting June 11th @ 7PM Location: Techncopia

by Tim Keller

Hey Everybody, We've got a meeting this Thursday, June 11th @7PM. Topic: TBD (Hit me up here or on Signal) Location: Technocopia Virtual Location: https://meet.jit.si/WlugMA We'll definitely be talking about the continuing spate of Linux kernel vulnerabilities. Supply chain attacks on npm / pypi / etc. As usual, we'll head out for dinner and keep the conversation going. Thanks, Tim. -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

June 9, 2026

Re: Keith's mail issue

by Keith Wright

Thank you much for your incredibly prompt and detailed reply. Dick Goodman via WLUG <wlug(a)lists.wlug.org> writes: > This is all analogous to what I use successfully for my wife. I can successfully send a message to one or two gmail (or yahoo, hotmail...) addresses, the problem comes with the mailing list, which has about 50 @gmail.com. That sets them off. > To your points: > 1) I forward her incoming stuff (successfully) to Gmail with Procmail I don't know Procmail. Will look into it (ironically by google). > 2) I appreciate that everything worked for 20 years. When I get too nostalgic I think about my long lost draft card. -- Keith

May 31, 2026

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 31, 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 6, 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