On Fri, Nov 19, 2021 at 05:07:21PM -0800, Mel Pilgrim wrote:
> I read in transport(5), virtual(5), et al that Postfix will case-fold
> query strings, but for one specific project I need it to not do that.
> Are there any tunables for this? I didn't see anything in postconf -d
> output that
I read in transport(5), virtual(5), et al that Postfix will case-fold
query strings, but for one specific project I need it to not do that.
Are there any tunables for this? I didn't see anything in postconf -d
output that looked related.
The short explanation is that I need to be able to do
Hi Wietse,
On 19/11/2021 16:53, Wietse Venema wrote:
With hash and btree there is no guaranteed way to read a table after
it is updated, even when using locks. LMDB tables are better in
this respect, as long as you use the right locking procedure (man 5
lmdb_table) but you'd need to make the
"Matus" == Matus UHLAR <- fantomas > writes:
Matus> is it not. To be precise:
Matus> SRS is to be used when you accept mail for one address and re-send to
Matus> another address (in different domain/on different server).
Matus> this is not the case for backup MX.
On 18.11.21 18:28, Togan
Missed this one:
> message_size_limit = 52428800
> virtual_mailbox_limit = 524288
>
> message_size_limit needs to be less than or equal to
> virtual_mailbox_limit. Your virtual_mailbox_limit is
> 100 times message_size_limit.
Not intentional, definitely a typo. I think early on I saw
> "Viktor" == Viktor Dukhovni writes:
>> On 18 Nov 2021, at 12:28 pm, Togan Muftuoglu wrote:
>>
>> Thanks for the clarification. One more thing having the backup MX listed in
>> the SPF records of the domain and opendkim signing the relayed mails does
>> not break the validations in the
With hash and btree there is no guaranteed way to read a table after
it is updated, even when using locks. LMDB tables are better in
this respect, as long as you use the right locking procedure (man 5
lmdb_table) but you'd need to make the table group readable so that
your tool can lock and read
Dear Postfix users,
I have a fairly quiet Postfix server and so can just about get away with
having 'reject_unverified_sender set' as default. This does lose genuine
email from time to time so to mitigate, I have a SPAWN policy service
'policy-nv' which checks a global file for exceptions. In
