incoming works tho. i've ran mail behind dynamic ip for decades. in is ok. out is a hassle to plug the input, i chose no filter but multi alias setup, so far it holds. or, i can know exactly where the spammers get sources. apparently don't really scour the internet like mailing lists, despite many of them don't mangle the from's. one would question if it even helps. maybe i'm calling devil out here since i'm pretty sure some spammers read my mail here too funnily many big players ban v4 dyn permanently but somehow allow v6 after my mta retries on v6 after v4 fail. i guess spammers haven't yet found that absolute gold mine to spam via v6. can't block that either. have to ban /64, /48 or more! where mails go through, i feel like some end up in wrong place, rarely that said, i while ip is dynamic, it still has all the spf, dkim, dmarc configured so maybe that's why most of systems still accept it maybe i blame ripe too much for that but i still wonder what's best, know source like ripe sending it from own servers and ip ranges or random company sending it via servers they use for all and it's only e-mail marketing with performance metrics if you are sender and work in company marketing department no receiver whatsoever perceives this, especially in 2025, as nothing more than a spam that tracks too. especially if same provider also distributes strange optout newsletters and other deceptions that nobody really wants i don't know, maybe ripe is right to outsource mail but then i wonder how do those mass mail companies could even guarantee absolute best deliverability if they go against users and sysadmins and rbl providers and other companies that do the best to not allow mass mailings so that's why i was surprised that ripe decided to dilute their legitimate important mails into strange pool of all others, with html and pixels i don't actively hate html myself but i know html mail is often used for malicious purposes and text is much harder to abuse, unless you try to coerce people into buying your grand piano (probably most wtf spam i've ever got in my 26 years of internet usage time) html is useful too, and that's the problem here, on what to choose i think most of notices ripe send out don't need to be design masterpieces of megabytes of inline svg but quick important reminders. maybe i'm not aware of all ripe work but i assume this. assume = make ass out of u and me? after all i don't send mails a lot personally or professionally, so no idea? so maybe i was unfair for ripe here... On September 1, 2025 9:19:04 PM GMT+03:00, Steven Miller <ripe@idrathernotsay.com> wrote:
I tend to keep a low profile, but I must say that requiring that emails be in text format in case someone wants to build some fragile text parsing thing around them - that will break with the slightest change to wording or organization - seems suboptimal. If there is a need for machine parsing RIPE emails, that should be handled with an attachment in a structured format such as yaml or json.
Though I would also argue that that sort of info should just be grabbed with an API call of some sort and left out of the email entirely.
Maybe things are different in Europe, but speaking of decades, I ran my own mail servers at home in the US for decades. The antispammers have made that effectively impossible, or at least so difficult that the effort far outweighs the benefits. If you send mail directly, you’re typically coming from an address range that isn’t among the blessed, so your mail is treated as spam, and there you are, trying to convince obscure antispam provider #36 that you aren’t a spammer. Personally, I hate that it’s come to this, but it is what it is. I gave in and now I have a Google Workspace account for my household.
I can’t do anything but applaud anyone’s decision to get out of the email-delivery rat-race and just outsource it.
-Steve
------ Original Message ------
From "James R Cutler via ripe-atlas" <ripe-atlas@ripe.net> To "Gert Doering" <gert@space.net> Cc "Carsten Schiefner" <carsten@schiefner.de>; ripe-atlas@ripe.net Date 9/1/2025 11:31:23 AM Subject [atlas] Re: Notification on removal of system-ipv4-works && system-ipv6-works tags while connected
Comments in line
On Sep 1, 2025, at 5:20 AM, Gert Doering <gert@space.net> wrote:
Hi,
On Mon, Sep 01, 2025 at 11:13:19AM +0200, Carsten Schiefner wrote:
On 01.09.2025 09:20, Gert Doering wrote:
On Tue, Aug 26, 2025 at 04:33:48PM +0200, Johan ter Beest wrote:
As I am working on emails lately, I will add this notification to my list.
Please undo the change that makes the "monthly status mails" now arrive in HTML format. This is not adding useful information but makes it more annoying for people that do not use a GUI mail client (because, you know, efficiency).
how about: /-> "Content-Type: text/plain" "Content-Type: multipart/alternative"-| \-> "Content-Type: text/html" - would this scratch your itch?
No. This is, in practice, one of the worst things that happen - multipart mails that have differing content in both bodies (and it happens quite more often that one would assume).
If there is *benefit* in HTML, like "nice advertising with pictures and tracking pixels and all that", go for it. If you want to send information, go for plain text (only).
Emphasis on information: Data intended as information, as in an email, should be Human readable Easily parsed by eye Easily parsed by code
In the Monthly probe report, the tables of keys and values do not meet criterion 2 as the variable width font messes with the vertical alignment. Plain text and fixed field sizes could remedy that for both GUI and TextUI users.
James R Cutler - 🦉 No AI content james.cutler@consultant.com
Gert Doering -- NetMaster -- have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard, Karin Schuler, Sebastian Cler Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/