Postfix snapshot 20131218 comes after a hiatus of three weeks of
overhauling the postconf command and TLSA support (TLS public-key
distribution through secure DNS instead of PKI).
There are no visible changes in TLSA support.
The postconf command was polished and completed further. Below is
a
Postfix has supported forward secrecy for TLS since version 2.2
when the TLS patch was adopted into Postfix. Things have changed a
lot since then, both in TLS and in the real world.
Viktor wrote up a FORWARD_SECRECY_README that summarizes the Postfix
side of things all in one place.
Available now
Alberto Mariani -Ad Glamor:
> Hi there,
> how can I chenge transport maps dynamically based on some rules via
> script (like PHP)
1) Use a MySQL or SQLite database.
http://www.postfix.org/mysql_table.5.html
http://www.postfix.org/sqlite_table.5.html
2) Update a textfile, then update the dat
Hi there,
how can I chenge transport maps dynamically based on some rules via
script (like PHP)
Thank you
Alberto Mariani
Ad Glamor s.r.l.
Homer Wilson Smith:
>
> The percent hack is way cool and simple, but depends on the target
> relay host supporting the percent hack. Our postfix machines do, but
> our sendmail does not out of the box, and who knows about other mailers
> or windows machines.
In that case, try Noel's sugges
I've tryig to use after-queue content filter as described in FILTER_README.
How could I pass the authentication information (i.e. was initial
message sent by authenticated user or not) when re-injecting message
using sendmail? The problem is that further I'd like to skip some checks
in amavis
Greetings,
As a Postfix user I could use some advice (official or unofficial)
regarding a mail accounting schema - a problem which increasingly annoys me.
I am running two different instances of Postfix and also some instances
of Sendmail. All Sendmail instances are running inside of FreeBSD
