Since certain MUAs such as MS Outlook allow the user to label messages as
"confidential" which according to http://www.faqs.org/rfcs/rfc1327.html gets
translated into MIME header "Sensitivity=Company-Confidential", quite some
secure mail gateways ensure higher transmission secrecy (e.g.
"smtp_enfor
When I want to add a different banner with -o in master.cf for a secondary
smtpd, this fails
with
<>
http://www.postfix.org/postconf.5.html#smtpd_banner says <<
smtpd_banner (default: $myhostname ESMTP $mail_name)
The text that follows the 220 status code in the SMTP greeting banner. Some
peopl
Hi,
Fortunately, more and more smtp servers offer STARTTLS.
I would like to analyze the certificates used when employing STARTTLS
"opportunistically".
Is there a way to have postfix e.g. insert into a mysql table for every
message sent over TLS the following record:
1) recipient domain name
2) ho
> Sent: Sonntag, 16. März 2014 17:11
> To: Postfix users
> Subject: Re: Statistics on TLS certificates used when sending with
> opportunistic TLS
>
> Ralf Hauser:
> > Hi,
> >
> > Fortunately, more and more smtp servers offer STARTTLS.
> > I would like to
Hi,
Messages with a certain content type should be bcc'd to an additional
address for my use-case at hand.
I guess I could do this in two rounds:
1) with header_checks relay to itself on a different port (FILTER)
2) on that secondary smtpd, I could use the
http://www.postfix.org/postconf.5.html#
Hi,
The following rule has served us well for a long time:
/^Subject:.*.*/ FILTER relay...
Today, it missed the following
<_TestABC_XYZ?= from mail01>>
It seems that outlook after approx. 55 characters terminates the encoding
and immediately restarts it. In the above sample it breaks the k
Hi,
In our postfix server, we see
SSL_accept error from hgrs-mail01.hgrs.tld.dom[161.x.y.z]: 0
Nov 16 08:54:52 postfix2cc/smtpd[18662]: warning: TLS library problem:
18662:error:140943E8:SSL
routines:SSL3_READ_BYTES:reason(1000):s3_pkt.c:1053:SSL alert number 0:
This error message apparently m
Hi,
http://www.postfix.org/postconf.5.html#smtpd_tls_fingerprint_digest is a
great feature.
Is there a plan to offer stronger digest algorithms such as sha256 ?
There appear to be some regulators who prefer to go beyond sha1 - see e.g.
chapt 2 (p 3) of
http://www.bundesnetzagentur.de/cln_1931/D
