Nice to meet you. My name is Morikawa.
Regarding Postfix relay settings, with the following configuration
All outgoing emails must be virus checked.
I'm pointing the relay destination to a higher level virus check on the SMTP
server.
With this, mail addressed to local domain will be sent from the
Joe Acquisto-j4:
> Added Virus scanning to a SOHO stetup. clamav-milter is directing
> (?) "infected" mail to postfix HOLD queue.
>
> That's fine.
>
> First thought is to process the queue'd mail, alter the subject
> line, based on the added descriptive header line, and deliver it
> to the intend
Added Virus scanning to a SOHO stetup. clamav-milter is directing (?)
"infected" mail to postfix HOLD queue.
That's fine.
First thought is to process the queue'd mail, alter the subject line, based on
the added descriptive header line, and
deliver it to the intended user(s). I don't cons
Ron Garret:
> WAL mode was previously discussed here:
>
> https://marc.info/?l=postfix-users&m=160096626120296&w=2
In other words the reader requires database write permission. I
fully agree that is not desirable.
> The upshot appears to be this, at least as things currently stand:
>
> > DO NOT
On Feb 23, 2021, at 11:41 AM, Richard Damon wrote:
> On 2/23/21 2:18 PM, Wietse Venema wrote:
>> Ron Garret:
If we take this route, then there needs to be a new field in the
Postfix sqlite config file that controls the time limit.
>>> Not necessarily. You could just hard-code a reaso
On 2/23/21 2:18 PM, Wietse Venema wrote:
> Ron Garret:
>>> If we take this route, then there needs to be a new field in the
>>> Postfix sqlite config file that controls the time limit.
>> Not necessarily. You could just hard-code a reasonable value (like
>> 1 second), or make it a #define so you n
Ron Garret:
> > If we take this route, then there needs to be a new field in the
> > Postfix sqlite config file that controls the time limit.
>
> Not necessarily. You could just hard-code a reasonable value (like
> 1 second), or make it a #define so you need a recompile to change
> it. That?s su
On Feb 23, 2021, at 10:19 AM, Wietse Venema wrote:
> Ron Garret:
Isn't SQLite supposed to deal with concurrent access?
https://sqlite.org/lockingv3.html
>>>
>>> Yes, it does, but the way it ?deals? with it is to throw an error
>> if one connection tried to read while another is writi
On Tue, Feb 23, 2021 at 01:19:24PM -0500, Wietse Venema wrote:
> > > Yes, it does, but the way it ?deals? with it is to throw an error
> > if one connection tried to read while another is writing. The net
>
> Bleh, it does not retry the operation?
Only if you specify a retry timeout. SQLite is
Ron Garret:
> >> Isn't SQLite supposed to deal with concurrent access?
> >> https://sqlite.org/lockingv3.html
> >
> > Yes, it does, but the way it ?deals? with it is to throw an error
> if one connection tried to read while another is writing. The net
Bleh, it does not retry the operation?
What
On Feb 22, 2021, at 4:56 PM, Ron Garret (gmail) wrote:
>
> On Feb 22, 2021, at 2:57 PM, Wietse Venema wrote:
>
>> 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=160
I understand that minimal_backoff_time in postfix greater than
2.4 is 300s so I deduce that if the postgrey is with default
parameters it is the correct value
El 23/02/2021 a las 15:20, IL Ka
escribió:
On Tue, Feb 23, 2021 at 4:5
On Tue, Feb 23, 2021 at 4:58 PM Francesc Peñalvez
wrote:
> I was looking in the postfix manual for the waiting parameter by which
> an email is tried to send after receiving a 4xx code. I am interested in
Hi.
I think you need to configure qmgr: http://www.postfix.org/qmgr.8.html
Look at "backof
I was looking in the postfix manual for the waiting parameter by which
an email is tried to send after receiving a 4xx code. I am interested in
adapting it correctly for the servers that use postgrey,but i dont find
it or i dont understand it
--
smime.p7s
Description: Firma criptográfica S
On Monday, February 22, 2021, 10:55:04 PM GMT+1, Viktor Dukhovni
wrote: >- For *SQL and LDAP, change is immediate.
>- For indexed tables, when switching to a new client connection.
>- For flat files (CIDR, PCRE, ..., main.cf), worst case $max_idle
> times $max_use, but typically of course
15 matches
Mail list logo
