mastouille.fr est l'un des nombreux serveurs Mastodon indépendants que vous pouvez utiliser pour participer au fédiverse.
Mastouille est une instance Mastodon durable, ouverte, et hébergée en France.

Administré par :

Statistiques du serveur :

616
comptes actifs

#postfix

3 messages3 participants0 message aujourd’hui

New #blog post: "Signing sieve vacation auto-reply messages with dkim using postfix for deliverability"

I start my holiday, during which I intend to do less computer-touching, but doing some holiday-related computer-touching with my mailserver.

neilzone.co.uk/2025/07/signing

Photo of me, a white man with a short dark beard, and dark hair, smiling at the camera, while sitting in front of a vintage terminal with green text on the screen.
neilzone.co.ukSigning sieve vacation auto-reply messages with dkim using postfix for deliverability
Plus via Neil Brown
#Linux#FOSS#postfix
A répondu dans un fil de discussion

@marcuwekling Großartige Idee! Ich bin (eh schon) dabei! 🙃 #dutgemacht #ididit

Hier was ich derzeit schon so nutze:

- Eigener Mailserver #postfix #clamav #rspamd #roundcubemail #dovecot
- Notebooks auf #Linux
- #pfsense Firewall
- #thunderbird

Selber gehostete freie Dienste/Software derzeit:
- #Nextcloud
- #PaperlessNGX
- #Peertube
- #HomeAssistant
- #Mastodon
- #Matrix
- #Wordpress

Fremdgehostete freie Dienste:
- #pixelfed
- #bigbluebutton
- #letsencrypt

Leider kann ich meinen Windowsrechner noch nicht loswerden #gamer - aber das kommt bestimmt auch noch irgendwann... 🤞

Sending newsletters in bulk

Full post here. https://rene.seindal.dk/2025/06/17/sending-newsletters-in-bulk/

I have a newsletter — Venetian Stories about the history of Venice — with a couple of hundred recipients.

For some time, I have managed that with a free WordPress plugin. One of those with a PRO version, and every update shifted some functionality over to the paid version.

When I wanted to move the newsletter from my History Walks Venice site to a dedicated domain, there was no way of migrating the plugin data without moving to the PRO version. Several functions I had used for a long time, were no only available for payment.

Confronted with these futile complications, I decided to return to basics.

The newsletters would be sent from my mail application of choice, as HTML emails, with all the recipients in the BCC field.

#NerdSpeak Some mail senders are exposing internal, non-resolving host names in the EHLO/HELO phase when sending mails, causing my mail server to (correctly) refuse them. However, in some cases I have to begrudgingly accept their broken config as the mails they send are actually legitimate and important. Looking at you, Drillisch Online. Fix your shit. Anyway, here's how I did it on my #postfix server: codeberg.org/jwildeboer/gists/

1/3

Codeberg.orggists/2025/20250615HELOAllowlistPostfix.md sur maingists - A collection of short notes on specific little things that are good to store and share but not enough for a blog entry. Mostly geeky stuff.

Any #postfix users know how to configure smtp_tls_wrappermode = yes for sending via a single relay, but not use it for others? I have things set up to relay via my outbound SMTP server to a few mail servers that all want STARTTLS over port 587, but now I want to add one that wants SMTPS over port 465. If I don't set smtp_tls_wrappermode = yes, it refuses to connect to the new server. If I do set it, it refuses to connect to the existing ones. There are some hints in the documentation that you can use transport_maps in some way, but I can't figure out how.

Y-en-a-t-il parmi vous qui ont mis en place dans #postfix un système de liste blanche de correspondants par utilisateur.

On a des clients qui utilisent Mailinblack et qui apprécient le système de captcha envoyé automatiquement en réponse aux expéditeurs inconnus.

Il doit y avoir moyen de faire quelque chose de similaire avec milter et/ou sieve

Nos boites mails sont administrées avec ISPConfig

Just going through the logs of my own mail server (Thanks, @mwl !) to extend my #postfix #fail2ban #regexp to ban hosts with too many unsuccesful login attempts. Knowing the user name pattern (example.com only letters, others with at least one dot) I came up with

'warning: .*\[<HOST>\]: SASL LOGIN authentication failed: .*sasl_username=<F-USER>(?:[^.]*@(?!example\.com)|[^.]*\.[^.]*@(?:example\.com))</F-USER>'

This works great.