On 16/11/24 17:12, Viktor Dukhovni via Postfix-users wrote:
On Sat, Nov 16, 2024 at 05:04:32PM +1100, Phil via Postfix-users wrote:
On 16/11/24 16:58, Viktor Dukhovni via Postfix-users wrote:
On Sat, Nov 16, 2024 at 01:38:25PM +0800, Hua Y via Postfix-users wrote:
default_destination_rate_
On Sat, Nov 16, 2024 at 05:17:39PM +1100, Phil via Postfix-users wrote:
> > > Is default_extra_recipient_limit not limiting the number of recipients in
> > > a
> > > given message ?
> >
> > No. And, what did you have in mind anyway?
> >
> > - Limiting the recipient count of incoming SMTP m
On Sat, Nov 16, 2024 at 05:04:32PM +1100, Phil via Postfix-users wrote:
> On 16/11/24 16:58, Viktor Dukhovni via Postfix-users wrote:
> > On Sat, Nov 16, 2024 at 01:38:25PM +0800, Hua Y via Postfix-users wrote:
> >
> > > > default_destination_rate_delay = 3
> > > > default_extra_recipient_limit =
On 16/11/24 17:00, Viktor Dukhovni via Postfix-users wrote:
On Sat, Nov 16, 2024 at 04:52:24PM +1100, Phil via Postfix-users wrote:
Yes - default_destination_rate_delay sets how many seconds between sending
messages,
Even for non-SMTP transports or internal relaying, ... not a good idea.
On 16/11/24 16:58, Viktor Dukhovni via Postfix-users wrote:
On Sat, Nov 16, 2024 at 01:38:25PM +0800, Hua Y via Postfix-users wrote:
default_destination_rate_delay = 3
default_extra_recipient_limit = 50
works for small setups . . .
Can you please explain the two options a bit more?
For the
On Sat, Nov 16, 2024 at 04:52:24PM +1100, Phil via Postfix-users wrote:
> Yes - default_destination_rate_delay sets how many seconds between sending
> messages,
Even for non-SMTP transports or internal relaying, ... not a good idea.
> the server could have a 1000 messages in the queue and it wi
On 16/11/24 16:52, Phil via Postfix-users wrote:
On 16/11/24 16:38, Hua Y via Postfix-users wrote:
On 2024-11-16 13:05, Phil via Postfix-users wrote:
On 16/11/24 11:31, Phil via Postfix-users wrote:
On 16/11/24 11:25, jeff--- via Postfix-users wrote:
How can I setup recipient rate limit in
On Sat, Nov 16, 2024 at 01:38:25PM +0800, Hua Y via Postfix-users wrote:
> > default_destination_rate_delay = 3
> > default_extra_recipient_limit = 50
> >
> > works for small setups . . .
>
> Can you please explain the two options a bit more?
For the first, see
https://www.postfix.org/postconf
On 16/11/24 16:38, Hua Y via Postfix-users wrote:
On 2024-11-16 13:05, Phil via Postfix-users wrote:
On 16/11/24 11:31, Phil via Postfix-users wrote:
On 16/11/24 11:25, jeff--- via Postfix-users wrote:
How can I setup recipient rate limit in postfix? or via a milter?
This setting should be ag
On 2024-11-16 13:05, Phil via Postfix-users wrote:
On 16/11/24 11:31, Phil via Postfix-users wrote:
On 16/11/24 11:25, jeff--- via Postfix-users wrote:
How can I setup recipient rate limit in postfix? or via a milter?
This setting should be against local users in our system.
Thank you.
you
On 16/11/24 11:31, Phil via Postfix-users wrote:
On 16/11/24 11:25, jeff--- via Postfix-users wrote:
How can I setup recipient rate limit in postfix? or via a milter?
This setting should be against local users in our system.
Thank you.
you can put
default_extra_recipient_limit = 50
in ma
Hello,
The postfix SMTP client can offload TLS to the tlsproxy by setting
"smtp_tls_connection_reuse = yes"
But in this mode, some logging occur always twice:
Nov 15 22:04:29 mta postfix/tlsproxy[27148]: Trusted TLS connection established
to nexthop.example[2001:db8::25]:587: TLSv1.3 with ciph
A. Schulze via Postfix-users:
> Hello,
>
> The postfix SMTP client can offload TLS to the tlsproxy by setting
> "smtp_tls_connection_reuse = yes"
> But in this mode, some logging occur always twice:
>
> Nov 15 22:04:29 mta postfix/tlsproxy[27148]: Trusted TLS connection
> established to nexthop
jeff--- via Postfix-users:
> How can I setup recipient rate limit in postfix? or via a milter?
> This setting should be against local users in our system.
>
See https://www.postfwd.org
It supports rate limits on sender, recipient, etc.
wietse
On 16/11/24 11:25, jeff--- via Postfix-users wrote:
How can I setup recipient rate limit in postfix? or via a milter?
This setting should be against local users in our system.
Thank you.
you can put
default_extra_recipient_limit = 50
in main.cf & postfix reload__
How can I setup recipient rate limit in postfix? or via a milter?
This setting should be against local users in our system.
Thank you.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postf
postfix--- via Postfix-users wrote in
:
|>> Is it worth it?
|>
|> It's easy to do, but I recommend ... have the web server return a \
|> redirect
|> (302 status)
|
|If running Apache it's even easier. Point the DNS. Add the non-www name in
(I thought he just tried that renault.de stuff
That is what I thought. Just wanted to be sure.
Thank you.
> On Nov 15, 2024, at 4:00 PM, postfix--- via Postfix-users
> wrote:
>
>
>>
>> I was wondering if there is anyway to use the maillog with the SSL
>> messages to determine who was trying to send messages during that
>> window.
>
>
I was wondering if there is anyway to use the maillog with the SSL
messages to determine who was trying to send messages during that
window.
You have the IP/Hostname of the servers connecting to your server.
If you are asking who as in the person, as in what the From: email address
was going
Hello all,
I am unsure if this is possible as it would probably be a security risk,
but I wanted to ask anyway.
A few days ago I made a mistake when configuring a new SSL cerfiticate
for my Postfix install. This resulted in about 10 days of downtime while
we sorted out what the actual problem was
On Fri, Nov 15, 2024 at 09:21:45PM +0800, Hua Y via Postfix-users wrote:
>
> Hi list
>
> can you help check if my options for smtps/submission are correct?
>
> in master.cf:
>
> ascleanup unix n - y - 0 cleanup
> -o header_checks=pcre:/etc/postfix/header_check
On Fri, Nov 15, 2024 at 02:25:14PM +0100, Florian Piekert via Postfix-users
wrote:
> the problem surely is on my end. But where and why. Maybe someone has an idea.
What problem exactly?
> -all three have in master.cf for tlsproxy the -D parameter at the end
Why?
> -all three have same debugge
Hello Viktor, all,
OK, so the "normal exit" isn't a problem then at all?
That is indeed good news, as I thought it was pointing to an issue I have on
these machines. Core dump might have been wrong terminology, process logging
then as you explained.
...
-all three have in master.cf for tlsp
Hello again on this topic,
the problem surely is on my end. But where and why. Maybe someone has an idea.
Situation:
-3 cloud machines with ubuntu 24.04.1 LTS (2 dist upgraded from 22.04.1 LTS, 1
plain 24.04.1 LTS out of the box)
-all three have postfix 3.10-20241113 snapshot
-2 out of 3 use tl
Hi list
can you help check if my options for smtps/submission are correct?
in master.cf:
ascleanup unix n - y - 0 cleanup
-o header_checks=pcre:/etc/postfix/header_checks_submission
smtps inet n - y - - smtpd
-o syslog_n
25 matches
Mail list logo
