On Sun, Dec 08, 2019 at 12:43:36AM +0100, ouafn...@shivaserv.fr wrote:
> I tried differents ways on the sni file, but every time I try with
> openssl to test the configuration I got on postfix logs:
>
> Dec 8 00:34:28 shiva2 postfix/smtpd[7290]: warning: key at index 1 in
> SNI data for
Hi all,
I'm trying to make work the SNI feature from postfix >3.4.
I've declared a "smtpd_tls_chain_files" using letsencrypt certificates
(privkey and fullchain), and a "tls_server_sni_maps" using hash file,
according the documentation online.
The doc says
"The chain files MUST start with
TOP-POST:
This thread no longer has any relevance to Postfix, and has
descended into ad-hominem. Before we have to start booting
miscreants from the list, let's stop here. Thanks.
> On Dec 7, 2019, at 11:06 AM, Jos Chrispijn wrote:
>
>> Apparently you also don't speak English properly. Do
On 21-11-19 6:42, Reto wrote:
Apparently you also don't speak English properly. Do you want people
to spam block the full .de domain because of that?
Idiot
-- With both feet on the ground you can't make any step forward
On 07.12.19 15:08, spaceman wrote:
I have a destination and a relay postfix. Both have the following (with
a few extra for the destination):
smtpd_sender_restrictions = reject_non_fqdn_sender,
reject_unknown_sender_domain, permit
The destination rejects emails as it is supposed to, however
spaceman:
> Hi,
>
> I have a destination and a relay postfix. Both have the following
> (with a few extra for the destination):
>
> smtpd_sender_restrictions = reject_non_fqdn_sender,
> reject_unknown_sender_domain, permit
>
> The destination rejects emails as it is supposed to, however the
Hi,
I have a destination and a relay postfix. Both have the following (with
a few extra for the destination):
smtpd_sender_restrictions = reject_non_fqdn_sender,
reject_unknown_sender_domain, permit
The destination rejects emails as it is supposed to, however the relay does
not. This means
