On Thu, Oct 13, 2022 at 05:16:56PM +0200, Jack Raats wrote:
> I'm using postfix 3.7.2_1,1 on a FreeBSD 13.2-p2 server. Everything is OK.
>
> After updating to version 3.7.3,1 mail is n't delivered to another
> server due to zen.spamhaus blocking by postscreen.
>
> Unstalling 3.7.3,1 and replaci
Jack Raats:
> Hi,
>
> I'm using postfix 3.7.2_1,1 on a FreeBSD 13.2-p2 server. Everything is OK.
>
> After updating to version 3.7.3,1 mail is n't delivered to another
> server due to zen.spamhaus blocking by postscreen.
>
> Unstalling 3.7.3,1 and replacing is by 3.7.2_1,1 everything is OK agai
Hi,
I'm using postfix 3.7.2_1,1 on a FreeBSD 13.2-p2 server. Everything is OK.
After updating to version 3.7.3,1 mail is n't delivered to another
server due to zen.spamhaus blocking by postscreen.
Unstalling 3.7.3,1 and replacing is by 3.7.2_1,1 everything is OK again.
Is something in the co
Thanks Viktor and Wietse... i will keep digging it out!!
My understading was what you said, so probably the problem is anywhere else...
thanks again!
Pedreter.
On Monday, February 22, 2021, 05:23:04 PM GMT+1, Viktor Dukhovni
wrote:
> On Feb 22, 2021, at 2:07 PM, Pedro David Marco
>
> On Feb 22, 2021, at 2:07 PM, Pedro David Marco wrote:
>
> postfix restart means 'postfix stop ; postfix start'
>
> maybe it would be a good idea to introduce some delay between stop and start?
Actually, to expedite the visibility configuration changes, it is generally
sufficient to do a "gra
Pedro David Marco:
> Ops, forgot to mention that, thanks Wietse...
> postfix restart means? 'postfix stop ; postfix start'
> maybe it would be a good idea to introduce some delay between stop and start?
With "postfix stop", ALL Postfix processes are terminated, so they
cannot remember old databas
; processes (not all of them!!!) keeps trying the old data instead of actual
> one!!! (as stated, this only happens withmodificacions; no problem with new
> entries)
> To my knowledge, a postmap on transport_para_vrfy and Postfix restart is
> enough... but...??It looks like not all post
ll postfix processes are aware of the
> config changes.
There is no "postfix restart" in Postfix as released by me.
What does YOUR "postfix restart" do?
a) Issue "postfix stop', which terminates all deliveries that are in progress?
b) Issue "postfix reload" which does not stop deliveries that are in progress?
Wietse
the old data instead of actual
one!!! (as stated, this only happens withmodificacions; no problem with new
entries)
To my knowledge, a postmap on transport_para_vrfy and Postfix restart is
enough... but... It looks like not all postfix processes are aware of the
config changes.
Any idea
Jim Garrison:
[ Charset ISO-8859-1 unsupported, converting... ]
> I maintain an old Fedora Core 5 system that I'm going to be
> updating to Fedora 9 -- I'll be rebuilding from scratch and
> copying over the config. The FC5 system has Postfix 2.2.8,
> and the new system will have 2.5.1.
>
> Can an
> I maintain an old Fedora Core 5 system that I'm going to be
> updating to Fedora 9 -- I'll be rebuilding from scratch and
> copying over the config. The FC5 system has Postfix 2.2.8,
> and the new system will have 2.5.1.
>
> Can anyone tell me if there are any major config file
> differences or
J.P. Trosclair wrote:
Hi Jim,
I did something similar with fedora core 6 last week. The way I did it
was take the last postfix security update (source rpm) from fedora core
6 extracted it and used it's spec file to build a new rpm with the
latest postfix stable release. I left our config file
I maintain an old Fedora Core 5 system that I'm going to be
updating to Fedora 9 -- I'll be rebuilding from scratch and
copying over the config. The FC5 system has Postfix 2.2.8,
and the new system will have 2.5.1.
Can anyone tell me if there are any major config file
differences or incompatibil
13 matches
Mail list logo
