Thank you very much for the guidance we will persue that path.
--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
On 5/22/2019 4:02 PM, VB wrote:
Hello Community
we were tasked at routing all outbound email from our mail relay postfix
server through an Anti-SPAM gateway and this introduces a requirement to
insert a custom header with a unique value ( shared by the Anti-SPAM vendor
) to let email relay thor
Hello Community
we were tasked at routing all outbound email from our mail relay postfix
server through an Anti-SPAM gateway and this introduces a requirement to
insert a custom header with a unique value ( shared by the Anti-SPAM vendor
) to let email relay thorough them.
so we want to insert
On 5/22/19 3:40 PM, Wietse Venema wrote:
> Phil Stracchino:
>> I don't know if this is Gentoo specific. Is anyone else running into a
>> configure failure on 5.x kernels because Postfix's configure doesn't
>> believe in 5.x kernels yet?
>
> Postfix 3.4 explicitly supports 5.x kernels; therefore e
Viktor Dukhovni:
> > On May 22, 2019, at 1:50 PM, MRob wrote:
> >
> > Thank you for pointing it out. Why is default for the setting same as
> > header_checks? I don't understand the common need for smtp server to run
> > the same header checks on attachment headers, can someone explain?
>
> Th
Phil Stracchino:
> I don't know if this is Gentoo specific. Is anyone else running into a
> configure failure on 5.x kernels because Postfix's configure doesn't
> believe in 5.x kernels yet?
Postfix 3.4 explicitly supports 5.x kernels; therefore earlier
Postfix version should work too, but I usua
On 5/22/19 1:30 PM, Ralph Seichter wrote:
> * Phil Stracchino:
>
>> I don't know if this is Gentoo specific. Is anyone else running into
>> a configure failure on 5.x kernels because Postfix's configure doesn't
>> believe in 5.x kernels yet?
>
> I run Postfix 3.4.5 on Gentoo Linux with kernel 5.1
> On May 22, 2019, at 1:50 PM, MRob wrote:
>
> Thank you for pointing it out. Why is default for the setting same as
> header_checks? I don't understand the common need for smtp server to run the
> same header checks on attachment headers, can someone explain?
This is backwards-compatibility.
On 2019-05-22 08:35, Dominic Raferd wrote:
On Wed, 22 May 2019 at 09:11, MRob wrote:
If I send a message as attachment, header_checks are applied to the
headers of the attachment also. Why does it happen? Can I turn it
off?
Try:
nested_header_checks =
Thank you for pointing it out. Why is
On 22 May 2019, at 11:10, Phil Stracchino wrote:
I don't know if this is Gentoo specific.
It seems likely...
Is anyone else running into a
configure failure on 5.x kernels because Postfix's configure doesn't
believe in 5.x kernels yet?
Not if they are running the current stable release ver
* Phil Stracchino:
> I don't know if this is Gentoo specific. Is anyone else running into
> a configure failure on 5.x kernels because Postfix's configure doesn't
> believe in 5.x kernels yet?
I run Postfix 3.4.5 on Gentoo Linux with kernel 5.1.3. No trouble at
all. Version 5.0.x did not cause an
I don't know if this is Gentoo specific. Is anyone else running into a
configure failure on 5.x kernels because Postfix's configure doesn't
believe in 5.x kernels yet?
make -j16 makefiles shared=yes dynamicmaps=no pie=yes
shlib_directory=/usr/lib64/postfix/MAIL_VERSION DEBUG=
CC=x86_64-pc-linux-
Jos Chrispijn:
> Dear team,
>
> I get this error messages in my logfile more frequently:
>
> May 21 21:23:51 kernel: May 21 21:23:51
> postfix/postscreen[77391]: fatal: btree:/var/db/postfix/postscreen_cache:
> unable to get exclusive lock: Resource temporarily unavailable
postscreen n
Dear team,
I get this error messages in my logfile more frequently:
May 21 21:23:51 kernel: May 21 21:23:51 postfix/postscreen[77391]:
fatal: btree:/var/db/postfix/postscreen_cache: unable to get exclusive lock:
Resource temporarily unavailable
Can you tell me what exactly goes wron
On Wed, 22 May 2019 at 09:11, MRob wrote:
> If I send a message as attachment, header_checks are applied to the
> headers of the attachment also. Why does it happen? Can I turn it off?
>
Try:
nested_header_checks =
If I send a message as attachment, header_checks are applied to the
headers of the attachment also. Why does it happen? Can I turn it off?
On 2019-05-22 07:58, Matus UHLAR - fantomas wrote:
MRob:
For some time it is possible to make postfix virtual tell a LDA who
is
the original recipient, add x-original-to header. But not LMTP.
I don't understand. The LMTP receivee DOES know who is the recipient,
doesn't it?
Not if any addres
MRob:
For some time it is possible to make postfix virtual tell a LDA who is
the original recipient, add x-original-to header. But not LMTP.
I don't understand. The LMTP receivee DOES know who is the recipient,
doesn't it?
This
create problems in final delivery, one example is autoreply vacat
18 matches
Mail list logo
