I used to run postfix chrooted but no longer do so.
|find /var/spool/postfix -type f -ls|
shows a list of files in /var/spool/postfix/pid/ with names inet.* and
unix.*, all very old and zero-length. Is this a hangover from running
postfix chrooted? Can I remove them all?
It also shows a few
On 22/02/2021 08:19, Dominic Raferd wrote:
I used to run postfix chrooted but no longer do so.
|find /var/spool/postfix -type f -ls|
shows a list of files in /var/spool/postfix/pid/ with names inet.* and
unix.*, all very old and zero-length. Is this a hangover from running
postfix chrooted? C
Dominic Raferd:
> I used to run postfix chrooted but no longer do so.
>
> |find /var/spool/postfix -type f -ls|
>
> shows a list of files in /var/spool/postfix/pid/ with names inet.* and
> unix.*, all very old and zero-length. Is this a hangover from running
> postfix chrooted? Can I remove the
On 22/02/2021 14:07, Wietse Venema wrote:
Dominic Raferd:
I used to run postfix chrooted but no longer do so.
|find /var/spool/postfix -type f -ls|
shows a list of files in /var/spool/postfix/pid/ with names inet.* and
unix.*, all very old and zero-length. Is this a hangover from running
postf
Hi!
i have this in my main.cf:
address_verify_transport_maps = hash:/etc/postfix/transport_para_vrfy
It works ok when i add a new domain, but when i modify an exsiting one and do
the corresponding postmap and postfix restart, randomlysome Postfix smtpd
processes (not all of them!!!) keeps trying
Pedro David Marco:
> Hi!
> i have this in my main.cf:
> address_verify_transport_maps = hash:/etc/postfix/transport_para_vrfy
> It works ok when i add a new domain, but when i modify an exsiting one and do
> the corresponding postmap and postfix restart, randomlysome Postfix smtpd
> processes (no
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?
Thanks,
Pedreter.
On Monday, February 22, 2021, 04:54:38 PM GMT+1, Wietse Venema
wrote:
Pedro David Marco:
>
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
> 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
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
>
I ran into the sqlite locked database problem discussed in these threads:
https://marc.info/?l=postfix-users&m=160096626120296&w=2
https://marc.info/?l=postfix-users&m=151561295721906&w=2
The problem occurs (AFAICT) because the database file was shared with a spam
filter which was writing to th
Viktor Dukhovni wrote:
> Actually, to expedite the visibility configuration changes, it is generally
> sufficient to do a "graceful" reconfiguration via "postfix reload". Or
> just do nothing, and let the change take place incrementally as processes
> "age out" (subject to $max_use and $max_idle)
On Mon, Feb 22, 2021 at 02:32:59PM -0700, Bob Proulx wrote:
> Viktor Dukhovni wrote:
> > If it is not an emergency, and it was working fine before the change,
> > generally
> > best to let the change take place incrementally. You can reduce the latency
> > by reducing $max_idle to ~5s and perhap
Post fix version 3.4.7. with Spamassassin. While adding virus scanning
(clamav) noticed during testing
that any mail send from the postfix host does not get processed by spamassassin.
Postfix does accept it and passes it right thorough without any indication it
was passed through
spamd or clamd
Ron Garret:
[ Charset windows-1252 converted... ]
> I ran into the sqlite locked database problem discussed in these threads:
>
> https://marc.info/?l=postfix-users&m=160096626120296&w=2
>
> https://marc.info/?l=postfix-users&m=151561295721906&w=2
>
> The problem occurs (AFAICT) because the data
Joe Acquisto-j4:
> Post fix version 3.4.7. with Spamassassin. While adding virus scanning
> (clamav) noticed during testing
> that any mail send from the postfix host does not get processed by
> spamassassin.
>
> Postfix does accept it and passes it right thorough without any indication it
> w
On 22 Feb 2021, at 17:27, Joe Acquisto-j4 wrote:
Post fix version 3.4.7. with Spamassassin. While adding virus
scanning (clamav) noticed during testing
that any mail send from the postfix host does not get processed by
spamassassin.
Postfix does accept it and passes it right thorough without
> On 22 Feb 2021, at 17:27, Joe Acquisto-j4 wrote:
>
>> Post fix version 3.4.7. with Spamassassin. While adding virus
>> scanning (clamav) noticed during testing
>> that any mail send from the postfix host does not get processed by
>> spamassassin.
>>
>> Postfix does accept it and passes it r
On 22 Feb 2021, at 18:40, Joe Acquisto-j4 wrote:
On 22 Feb 2021, at 17:27, Joe Acquisto-j4 wrote:
Post fix version 3.4.7. with Spamassassin. While adding virus
scanning (clamav) noticed during testing
that any mail send from the postfix host does not get processed by
spamassassin.
Postfix do
19 matches
Mail list logo
