On Thu, Sep 25, 2014 at 09:59:44PM -0700, Will Yardley wrote:
> I will try running strace on an smtpd process and see if that helps
> identify anything.
Notice the nanosleep() call here, and the jump from 23:17:21.642640 to
23:17:22.642808 -- exactly a second.
23:17:21.608881 read(9, "RCPT TO:\r\
Am Do, 25.09.2014, 23:16 schrieb Wietse Venema:
>> In the RELEASE_NOTES:
>>
>> - Milter clients and policy clients with non-default settings:
>> smtpd_milters = {inet:host:port, timeout=xxx, default_action=yyy}, ...
>
> This is now implemented for Milters.
Also from me: Thank you.
this is the de
On Fri, Sep 26, 2014 at 12:59:58AM +, Viktor Dukhovni wrote:
> On Thu, Sep 25, 2014 at 05:34:46PM -0700, Will Yardley wrote:
>
> > The new systems are faster hardware, and faster disks, however, I notice
> > a very slight delay (maybe 1s) on the newer system after RCPT TO (it's
> > perceptible
On Thu, Sep 25, 2014 at 05:34:46PM -0700, Will Yardley wrote:
> We upgraded recently from 2.3.3 (RHEL5 stock Postfix) to 2.6.6 (RHEL6
> stock Postfix). The settings, including $smtpd_sender_restrictions,
> $smtpd_recipient_restrictions, and the ldap lookup maps (as well as the
> backend LDAP serv
We upgraded recently from 2.3.3 (RHEL5 stock Postfix) to 2.6.6 (RHEL6
stock Postfix). The settings, including $smtpd_sender_restrictions,
$smtpd_recipient_restrictions, and the ldap lookup maps (as well as the
backend LDAP servers) are the same.
The new systems are faster hardware, and faster dis
* Wietse Venema :
> Christian R??ner:
> > In the RELEASE_NOTES:
> >
> > - Milter clients and policy clients with non-default settings:
> > smtpd_milters = {inet:host:port, timeout=xxx, default_action=yyy}, ...
>
> This is now implemented for Milters. The supported attributes are
> command_timeo
Christian R??ner:
> In the RELEASE_NOTES:
>
> - Milter clients and policy clients with non-default settings:
> smtpd_milters = {inet:host:port, timeout=xxx, default_action=yyy}, ...
This is now implemented for Milters. The supported attributes are
command_timeout, connect_timeout, content_timeo
* on the Thu, Sep 25, 2014 at 03:46:12PM +, Viktor Dukhovni wrote:
>> Is it possible to use different TLS certificates for different ports?
>> I'd like to use one for SMTP on port 25, and a different one for
>> submission on ports 587 and 465...
>
> Yes.
>
> main.cf:
> submission_t
On Thu, Sep 25, 2014 at 03:15:19PM +0100, Mike Cardwell wrote:
> Hi,
>
> Is it possible to use different TLS certificates for different ports?
> I'd like to use one for SMTP on port 25, and a different one for
> submission on ports 587 and 465...
Yes.
main.cf:
submission_tls_cert_fil
Hi,
Is it possible to use different TLS certificates for different ports?
I'd like to use one for SMTP on port 25, and a different one for
submission on ports 587 and 465...
I am very new to Postfix. I'm currently trying to port my Exim config
over and this is one of the things I was previously a
On 09/18/2014 05:40 PM, Wietse Venema wrote:
Giuseppe De Nicolo':
136.233724 212.19.117.109 217.72.32.234 SMTP131 S:
250 2.1.0 Ok | 250 2.1.5 Ok | 354 End data with .
136.441076 212.19.117.109 217.72.32.234 SMTP131 [TCP
Retransmission] S: 250 2.1.
Yes, now working with the 'i' flag. Thanks very much!
MD
On 2014.09.25 16:34:51 +1000, Dr Michael Daly wrote:
> /(^Subject: [^a-z]+$)/ REJECT <--not working
To give an idea: /^Subject: [^a-z]+$)/i REJECT
i (default: on)
Toggles the case sensitivity flag. By default, matching is case
ins
On 2014.09.25 16:34:51 +1000, Dr Michael Daly wrote:
> /(^Subject: [^a-z]+$)/ REJECT <--not working
To give an idea: /^Subject: [^a-z]+$)/i REJECT
i (default: on)
Toggles the case sensitivity flag. By default, matching is case
insensitive.
> Online PCRE regex checkers seem to indicate th
13 matches
Mail list logo
