> On 23 Feb 2022, at 2:50 pm, Wietse Venema wrote:
>
>>>
>>> TWO settings to enable UTF8? Bah.
>>
>> No, because the second one would be *ON* by default.
>
> And that would be an incompatible change from LATIN1?
Only if also "smtputf8_enable = yes". That is, with "smtputf8_enable = yes"
we'd
Viktor Dukhovni:
> > On 23 Feb 2022, at 6:38 am, Wietse Venema wrote:
> >
> > TWO settings to enable UTF8? Bah.
>
> No, because the second one would be *ON* by default.
And that would be an incompatible change from LATIN1?
> It would probably be better named "utf8_disable" and then
> be "off"
> On 23 Feb 2022, at 6:38 am, Wietse Venema wrote:
>
> TWO settings to enable UTF8? Bah.
No, because the second one would be *ON* by default.
It would probably be better named "utf8_disable" and then
be "off" by default.
--
Viktor.
Russell Jones:
> > perhaps changing the delay to 0... why did you change it at all?
>
> Is setting it to 0 not allowing it to send out as quickly as possible with
> no delay at all?
>
> I set it to 1s because I was attempting to configure 10 messages per second
> (default_destination_concurrency_
Phil Stracchino:
> On 2/23/22 06:38, Wietse Venema wrote:
> > TWO settings to enable UTF8? Bah.
>
> I have to admit that my feeling on this is "Let LATIN1 die". The future
> is encoded in UTF8/UTF16.
Agreed, for the longer term. But the patch was for the stable release.
Wietse
> perhaps changing the delay to 0... why did you change it at all?
Is setting it to 0 not allowing it to send out as quickly as possible with
no delay at all?
I set it to 1s because I was attempting to configure 10 messages per second
(default_destination_concurrency_limit (10) *
default_destinat
On 23.02.22 10:21, Russell Jones wrote:
That configuration option only takes whole seconds - How can I achieve 10
messages per second with it?
default_destination_rate_delay (default: 0s)
perhaps changing the delay to 0... why did you change it at all?
On Wed, Feb 23, 2022 at 10:12 AM Yves-
Thanks!
That configuration option only takes whole seconds - How can I achieve 10
messages per second with it?
On Wed, Feb 23, 2022 at 10:12 AM Yves-Marie Le Pors Chauvel <
ym.leporschau...@ccmbenchmark.com> wrote:
> Hi Russel,
>
> You have to change your default_destination_rate_delay, as said
Hi Russel,
You have to change your default_destination_rate_delay, as said in the
documentation :
*The default amount of delay that is inserted between individual message
deliveries to the same destination and over the same message delivery
transport.*
So, in your case, it sends only 1 message e
On 2/23/22 06:38, Wietse Venema wrote:
TWO settings to enable UTF8? Bah.
I have to admit that my feeling on this is "Let LATIN1 die". The future
is encoded in UTF8/UTF16.
--
Phil Stracchino
Babylon Communications
ph...@caerllewys.net
p...@co.ordinate.org
Landline: +1.603.293.848
Hi all,
I am struggling to understand why my postfix configuration is not allowing
me to send 10 messages per second through my configured relayhost. When
watching the logs, it is sending 1 message per second.
initial_destination_concurrency = 10
default_destination_concurrency_limit = 10
default
Wietse Venema:
> Charles Sprickman:
> > Oops, sorry, "sender_dependent_relayhost_maps" should be
> > "sender_dependent_default_transport_maps" below...
>
> In both cases the lookup is by sender email address, not SASL login.
> And that is the documented behavior.
>
> There is a different appoach,
Charles Sprickman:
> Oops, sorry, "sender_dependent_relayhost_maps" should be
> "sender_dependent_default_transport_maps" below...
In both cases the lookup is by sender email address, not SASL login.
And that is the documented behavior.
There is a different appoach, and that is to use the "filter
Hi Viktor,
On Thu, 3 Feb 2022 at 14:07, Viktor Dukhovni
wrote:
> On Thu, Feb 03, 2022 at 01:39:44PM -0500, Martin Hicks wrote:
>
> > The only configuration change I made in response to this discussion was
> > to disable smtpd_tls_ask_ccert - I'm not sure why this was ever enabled.
> >
> > I'll u
TWO settings to enable UTF8? Bah.
Wietse
15 matches
Mail list logo