(2/2) So there now is a new mapping for transport policies in my /etc/postfix/main.cf file like this:
# transport policies for specific recipients/domains
transport_maps = hash:/etc/postfix/transport
A new service in /etc/postfix/master.cf like this:
smtp-ipv4 unix .. .. .. .. .. smtp
-o inet_protocols=ipv4
And a new entry in /etc/postfix/transport like this:
gmail.com smtp-ipv4
That should do the job!
(1/2) Gmail now refuses to accept messages from my Postfix mail server if the PTR record is not set. Unfortunately I haven't been able to persuade my colo provider to set these records for my IPv6 addresses (or delegate rDNS to me).
The only way to "fix" this is by creating a mapping for the gmail.com domain that explicitly uses IPv4 for outgoing messages.
🚀 Deploy #Virtualmin on #AlmaLinux #VPS (5 Minute Quick-Start Guide)
This article provides a how-to guide to deploy Virtualmin on AlmaLinux VPS.
What is Virtualmin?
Virtualmin is a powerful open-source web hosting control panel built on top of Webmin.
It supports:
Multi-domain virtual hosting
Apache or Nginx
PHP ...
Continued 👉 https://blog.radwebhosting.com/deploy-virtualmin-on-almalinux-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #controlpanel #bind #phpfpm #spamassassin #dovecot #selfhosted #certbot #mariadb #postfix #clamav #selfhosting #letsencrypt
#thunderbird 146 and also befor makes some problems with #ipv6.
e.g. sending a mail, sends the mail immediately and the bcc shows up immediately too, but hangs on copying to sent folder. one 2nd or 3rd try it copies the file. its #postfix and #dovecot .
already searched, but nothing found on the net. my IPv6 net is pretty fast and everything else works as expected.
Postfix - Blocking Japanese Keywords in Email Body and Headers - Working with Gmail but Not Proofpoint Relay #server #email #postfix #mail
Problem - We need to block incoming emails from all sources containing specific Japanese keywords the message body. Our implementation successfully blocks these keywords when emails come directly f...
Your Email, Your Rules: Self-Hosting Simplified
Happy to see that #Postfix has now got REQUIRETLS support (SMTP Require TLS Option- RFC 8689), written by @jimfenton and published in december 2019.
Simply said: this standard enables end users to flag a specific email to be sensitive so that it should only be passed on if the server(s) in question all support encrypted transport of the email.
A big step forward imho, and I hope to see more client & server support for REQUIRETLS in 2026!
The SMTP STARTTLS option, used in negotiating transport-level encryption of SMTP connections, is not as useful from a security standpoint as it might be because of its opportunistic nature; message delivery is, by default, prioritized over security. This document describes an SMTP service extension, REQUIRETLS, and a message header field, TLS-Required. If the REQUIRETLS option or TLS-Required message header field is used when sending a message, it asserts a request on the part of the message sender to override the default negotiation of TLS, either by requiring that TLS be negotiated when the message is relayed or by requesting that recipient-side policy mechanisms such as MTA-STS and DNS-Based Authentication of Named Entities (DANE) be ignored when relaying a message for which security is unimportant.
Adrian Offerman
Rad Web Hosting
Zeitgeisty Aphorisms
Khürt Williams
KMJ 🇦🇹
Greg Harvey 🌍
AskUbuntu
oemb1905
Per Thorsheim