Jason Hirsh:
> OK. I went to the manual. Saw this
>
> address_verify_map = hash:/var/lib/postfix/verify
>
> I added that to my main.cf and got the following error
>
> triggerfish postfix/verify[22738]: warning: hash:/var/lib/postfix/verify is
> unavailable. open d
a_directory}/smtp_scache
That is smtpd_tls_session_cache_database and smtp_tls_session_cache_database.
> I have reloaded Postfix even rebooted the server but the postfix/verify
> database keeps giving the old reference
>
> postfix/verify[19776]: warning: btree:/var/db/postfix/verify_cache is
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
to.
smtpd_tls_session_cache_database = lmdb:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = lmdb:${data_directory}/smtp_scache
I have reloaded Postfix even rebooted the server but the postfix/verify
database keeps
Hi
Wietse yes you right - problem solved
W dniu 06.10.2021 o 17:27, Wietse Venema pisze:
> natan:
>> postconf -P | grep smtp_
>>
>> smtp/unix/smtp_connect_timeout = 5
>> smtp/unix/smtp_helo_timeout = 5
> Well there is your problem. 5 seconds is too short for reliable operation.
>
> Wietse
>
On 2021-10-06 at 10:38:23 UTC-0400 (Wed, 6 Oct 2021 16:38:23 +0200)
natan
is rumored to have said:
postconf -P | grep smtp_
smtp/unix/smtp_connect_timeout = 5
smtp/unix/smtp_helo_timeout = 5
Fix those in master.cf. Scold whoever set them. Shortening SMTP client
timeouts is never safe.
s
natan:
> postconf -P | grep smtp_
>
> smtp/unix/smtp_connect_timeout = 5
> smtp/unix/smtp_helo_timeout = 5
Well there is your problem. 5 seconds is too short for reliable operation.
Wietse
Hi
Wietse
postconf -d | grep 'smtp_.*timeout'
smtp_connect_timeout = 30s
smtp_data_done_timeout = 600s
smtp_data_init_timeout = 120s
smtp_data_xfer_timeout = 180s
smtp_helo_timeout = 300s
smtp_mail_timeout = 300s
smtp_quit_timeout = 300s
smtp_rcpt_timeout = 300s
smtp_rset_timeout = 20s
smtp_start
natan:
> Hi
> Wietse this log is wgen I push up via postqueue -i ID (I push up some times)
>
> smtp_connection_reuse_time_limit = 400s
> smtp_data_done_timeout = 1600s
> smtp_rcpt_timeout = 900s
> smtp_tls_loglevel = 1
> smtp_tls_note_starttls_offer = yes
> smtp_tls_security_level = may
> smtp_tls
Hi
Wietse this log is wgen I push up via postqueue -i ID (I push up some times)
smtp_connection_reuse_time_limit = 400s
smtp_data_done_timeout = 1600s
smtp_rcpt_timeout = 900s
smtp_tls_loglevel = 1
smtp_tls_note_starttls_offer = yes
smtp_tls_security_level = may
smtp_tls_session_cache_database = b
natan:
> Hi
> I have some problem in send
>
> My working environment is:
>
> ---postfix1-(MX)lmtp-dovecot-director---dovecot1-6
> In dovecot1-6 i have exim whose smarthost is postfix2 name (P5)
>
> all works fine but sometimes I get in log:
>
> Oct? 6 14:14:25 P5 postfix/smtp[52
Hi
postconf |grep "smtp_helo_timeout"
smtp_helo_timeout = 300s
W dniu 06.10.2021 o 14:34, natan pisze:
> Hi
> For clarity of configuration
>
> ---postfix1-(MX)lmtp-dovecot-director---dovecot1-6
>
> In dovecot1-6 I have storage in Maildir and sieve filters
> Dovecot1-6 have exim who
Hi
For clarity of configuration
---postfix1-(MX)lmtp-dovecot-director---dovecot1-6
In dovecot1-6 I have storage in Maildir and sieve filters
Dovecot1-6 have exim whose smarthost is postfix2 name(P5) and this is use when
user have sieve filter (for redirect etc)
W dniu 06.10.202
Hi
I have some problem in send
My working environment is:
---postfix1-(MX)lmtp-dovecot-director---dovecot1-6
In dovecot1-6 i have exim whose smarthost is postfix2 name (P5)
all works fine but sometimes I get in log:
Oct 6 14:14:25 P5 postfix/smtp[52636]: 4HPY3L22S1z3mgPD: conve
On Tue, Jul 29, 2014 at 04:05:51PM +0200, Atze Zitman wrote:
My final response in this thread:
> It is true that I have "smtpd_delay_reject = no". I have done this, so
> the sender restrictions would not be evaluated for each recipient address,
> but for the sender address only (tested long time
hat it only influences
Regards,
Atze Zitman
-Oorspronkelijk bericht-
Van: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
Namens Viktor Dukhovni
Verzonden: dinsdag 29 juli 2014 14:56
Aan: postfix-users@postfix.org
Onderwerp: Re: Can Postfix verify client certifica
On Tue, Jul 29, 2014 at 11:42:01AM +0200, Atze Zitman wrote:
> According to the Postfix TLS Readme there are 3 ways to configure the
> server-side to support access control:
>
> * permit_tls_clientcerts
> * permit_tls_all_clientcerts
> * check_ccert_access type:table
>
> But these three options
Why don't you use client (certificate or public-key) fingerprints?
Wietse
.
Regards,
Atze Zitman
-Oorspronkelijk bericht-
Van: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
Namens Wietse Venema
Verzonden: dinsdag 29 juli 2014 13:17
Aan: Postfix users
Onderwerp: Re: Can Postfix verify client certificate fingerprint when
supporting
Atze Zitman:
> Hello everyone,
>
> I hope I have the correct mailing list for my question. Initially I asked
> this question at:
> http://stackoverflow.com/questions/24999580/can-postfix-verify-client-certificate-fingerprint-when-supporting-starttls
>
> According to t
Hello everyone,
I hope I have the correct mailing list for my question. Initially I asked this
question at:
http://stackoverflow.com/questions/24999580/can-postfix-verify-client-certificate-fingerprint-when-supporting-starttls
According to the Postfix TLS Readme there are 3 ways to configure
20 matches
Mail list logo
