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/