On Wed, May 14, 2025 at 11:47:25AM -0400, Sean McBride via Postfix-users wrote:
> On 13 May 2025, at 13:02, Bill Cole via Postfix-users wrote:
>
> > The simplest setup is to have the full chain in a single file
> > referred to by smtpd_tls_cert_file and NO smtpd_tls_chain_file.
There is no such
Dnia 14.05.2025 o godz. 15:55:22 Scott Techlist via Postfix-users pisze:
> Apologies in advance for the slightly OT question. I've used Postfix since
> the beginning on a relatively small server. I was thankful when Let's
> Encrypt made it possible for me to automate and have "real" certs vs the
>
It appears that Scott Techlist via Postfix-users said:
>Apologies in advance for the slightly OT question. I've used Postfix since
>the beginning on a relatively small server. I was thankful when Let's Encrypt
>made it possible for me to automate and have "real" certs vs the pain of
>having to
Apologies in advance for the slightly OT question. I've used Postfix since the
beginning on a relatively small server. I was thankful when Let's Encrypt made
it possible for me to automate and have "real" certs vs the pain of having to
deal with and renew self signed certs (if that will even w
On 14 May 2025, at 12:06, Bill Cole via Postfix-users wrote:
>> OTOH that setup doesn't seem so simple in that (AFAICT) neither certbot nor
>> acme.sh can generate such a combined file.
>
> Really?
>
> $ postconf smtpd_tls_eccert_file
> smtpd_tls_eccert_file = /var/root/.acme.sh/scconsult.com_ecc
On Wed, 14 May 2025 08:29:06 +0200
Gregory Kohring via Postfix-users wrote:
[snip]
>
> "All outgoing mail from our network is relayed through a spam
> filtering system that may affect how certain TLS negotiation
> stages (like 250-STARTTLS) are exposed during the
> SMTP handshake.
>
> That sa
On 2025-05-14 at 11:47:25 UTC-0400 (Wed, 14 May 2025 11:47:25 -0400)
Sean McBride via Postfix-users
is rumored to have said:
On 13 May 2025, at 13:02, Bill Cole via Postfix-users wrote:
The simplest setup is to have the full chain in a single file
referred to by smtpd_tls_cert_file and NO smt
On Wed, May 14, 2025 at 05:47:25PM CEST, Sean McBride via Postfix-users
said:
> On 13 May 2025, at 13:02, Bill Cole via Postfix-users wrote:
>
> > The simplest setup is to have the full chain in a single file referred to
> > by smtpd_tls_cert_file and NO smtpd_tls_chain_file.
>
> OTOH that set
On 13 May 2025, at 13:02, Bill Cole via Postfix-users wrote:
> The simplest setup is to have the full chain in a single file referred to by
> smtpd_tls_cert_file and NO smtpd_tls_chain_file.
OTOH that setup doesn't seem so simple in that (AFAICT) neither certbot nor
acme.sh can generate such a
On 14.05.25 10:37, vom513 via Postfix-users wrote:
I see docs on how to rate limit for certain networks / IPs - but can custom
rate limiting be applied to authenticated users ?
postfwd as policy filter can do that
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning:
Hello all,
I see docs on how to rate limit for certain networks / IPs - but can custom
rate limiting be applied to authenticated users ?
Thanks.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-l
Dnia 14.05.2025 o godz. 20:17:31 Viktor Dukhovni via Postfix-users pisze:
> Regardless, indeed it should be possible to find an ISP with a less
> invasive policy, though they'd still need to be responsive to spam
> complaints and close down SMTP access for customers who violate AUP,
> or else the I
Dnia 14.05.2025 o godz. 20:37:40 Matthew J Black via Postfix-users pisze:
> - as you are no doubt aware, I had an "interesting" situation where
> my email were being turned into html by a service I am no-longer
> using. Hopefully this email (which uses a different system/service)
> will be in plai
On Wed, May 14, 2025 at 10:16:50AM +0200, Jaroslaw Rafa via Postfix-users wrote:
> Dnia 14.05.2025 o godz. 08:29:06 Gregory Kohring via Postfix-users pisze:
> > Unfortunately, this is standard industry practice and cannot be
> > disabled."
>
> Utter bullshit. Doing a MiTM attack (because that's in
@Viktor: You're right - I should have posted the config with my first post. I didn't, and for that I apologise.I also apologise for taking a while to get back to you - as you are no doubt aware, I had an "interesting" situation where my email were being turned into html by a service I am no-longer
Dnia 14.05.2025 o godz. 08:29:06 Gregory Kohring via Postfix-users pisze:
> Unfortunately, this is standard industry practice and cannot be
> disabled."
Utter bullshit. Doing a MiTM attack (because that's in fact what they do) on
your server is a "standard industry practice"? What a bold statement
On Wed, May 14, 2025 at 08:29:06AM +0200, Gregory Kohring via Postfix-users
wrote:
> "All outgoing mail from our network is relayed through a spam
> filtering system that may affect how certain TLS negotiation stages
> (like 250-STARTTLS) are exposed during the SMTP handshake.
>
> That said, TLS
17 matches
Mail list logo
