Is it possible for two different servers to have a same long_queue_ids ?
Are the long queue ID's unique to the world or only unique to that postfix
instance?
Given 2040 Postfix mail servers that each have queued a mail at the exact same time, up to micro seconds, and a pool of 3 million
inodes
Is it possible for two different servers to have a same long_queue_ids ?
Are the long queue ID's unique to the world or only unique to that
postfix instance?
Just to let everyone know we are moving IRC chat support from Freenode
to Libera chat. If you'd like community support for postfix via IRC
please join us at irc.libera.chat #postfix:
https://libera.chat/guides/connect
For more info about why we have moved please see:
https://gist.github.com/
On 2021-05-27 at 11:31:15 UTC-0400 (Thu, 27 May 2021 11:31:15 -0400)
is rumored to have said:
enable_long_queue_ids = yes
New queue files are created with names such as 3Pt2mN2VXxznjll. These
are encoded in a 52-character alphabet that contains digits (0-9),
upper-case letters (B-Z) and lo
Damian:
> > Safe to assume the 11th character is always 'z'?
> Until July 2596.
The long queue ID format is: 6 or more characters for the time in
seconds, 4 characters for the time in microseconds, the 'z'; the
remainder is the file inode number encoded in the first 51 characters
of the 52-
On 05-27-2021 1:16 pm, Eric Germann wrote:
Is there a way in Postfix to force delivery for a particular host or
domain to deliver over v4 without playing parlor games with DNS (ala
the Netflix workaround for v6 on tunnels)
Isn't using main.cf:smtp_bind_address another way force postfix to
al
On 05-27-2021 1:16 pm, Eric Germann wrote:
Is there a way in Postfix to force delivery for a particular host or
domain to deliver over v4 without playing parlor games with DNS (ala
the Netflix workaround for v6 on tunnels)
Isn't using main.cf:smtp_bind_address another way force postfix to
On Thu, May 27, 2021 at 01:16:22PM -0400, Eric Germann wrote:
> I have a mailing list I’m trying to join to which is v4/v6 enabled.
> My v4 has a proper PTR record. My v6 does not currently and I’m going
> round and round with AWS to get it updated.
>
> Is there a way in Postfix to force deliver
I have a mailing list I’m trying to join to which is v4/v6 enabled. My v4 has
a proper PTR record. My v6 does not currently and I’m going round and round
with AWS to get it updated.
Is there a way in Postfix to force delivery for a particular host or domain to
deliver over v4 without playing
On Thu, May 27, 2021 at 05:42:34PM +0100, Matthew Richardson wrote:
> >I'm afraid that's not currently possible. You can mandate DANE via a
> >setting of "dane-only" or opportunistically use DANE via "dane", which
> >in the absence of TLSA records defaults to opportunistic TLS, which may
> >in tu
Dear Viktor,
Thank you for your (as usual!) most helpful response below, which was much
appreciated.
On Thu, 27 May 2021 11:57:41 -0400, Viktor Dukhovni wrote:-
>On Thu, May 27, 2021 at 04:48:15PM +0100, Matthew Richardson wrote:
>
>> I am trying to work out the correct incantation in order to s
On Thu, May 27, 2021 at 11:40:47AM -0400, post...@ptld.com wrote:
> > On 05-27-2021 11:37 am, Viktor Dukhovni wrote:
> >> On 27 May 2021, at 11:31 am, post...@ptld.com wrote:
> >>
> >> Any other tips for parsing logs for queue ID?
> >
> > They are non-empty strings of alphanumeric characters. Y
On Thu, May 27, 2021 at 04:48:15PM +0100, Matthew Richardson wrote:
> I am trying to work out the correct incantation in order to specify for a
> given outgoing domain that:-
>
> * TLS is mandatory, the message is not sent unencrypted; and
> * if DANE is present AND if it fails to match, the mess
Safe to assume the 11th character is always 'z'?
Until July 2596.
I am trying to work out the correct incantation in order to specify for a
given outgoing domain that:-
* TLS is mandatory, the message is not sent unencrypted; and
* if DANE is present AND if it fails to match, the message is not sent
The way to do this seems to be with "smtp_tls_policy_maps". T
On 05-27-2021 11:37 am, Viktor Dukhovni wrote:
On 27 May 2021, at 11:31 am, post...@ptld.com wrote:
Any other tips for parsing logs for queue ID?
They are non-empty strings of alphanumeric characters. You should
not match the implementation more precisely than that.
But on just that logic,
enable_long_queue_ids = yes
New queue files are created with names such as 3Pt2mN2VXxznjll. These
are encoded in a 52-character alphabet that contains digits (0-9),
upper-case letters (B-Z) and lower-case letters (b-z). For safety
reasons the vowels (AEIOUaeiou) are excluded from the alphabet
17 matches
Mail list logo
