On 11/16/2015 04:54 PM, Wietse Venema wrote:
> With Postfix 3.0 or later:
>
>... check_client_access static:{warn text...} ...
>
> Older Postfix releases require that the lookup result is stored
> outside main.cf.
>
> (Postfix 3.0 also introduces inline: tables whose keys and values
> are
Hey postfix-users,
I am afraid I have a hopefully simple configuration style question:
I set up a restriction class. Every connection/sending attempt that goes
into this somewhat trapping class via an access-map, naturally.
Now I would love to log a warn or info message to the log file whenever
On 06/16/2015 03:44 PM, Viktor Dukhovni wrote:
the individually set
process limits work fine, but they add up quickly. Even IPv4 and IPv6
create two listeners for the same job already making it difficult to
pick sensible individual limits.
IIRC you can halve the number of listeners by
Hello postfix-users,
when running multiple smtpd services on different IPs and with different
SSL-certifices (I believe there still is no SNI support in postfix? -
http://www.postfix.org/TLS_README.html - There are no plans to
implement SNI in the Postfix SMTP server. ) the individually set
Hey again postfix-users,
On 13.03.2013 09:47, Christian Rohmann wrote:
1) Use the XCLIENT attribute LOGIN and have postfix send that to the
scanner. But I don't know if postfix even does send XCLIENT data to
another SMTP server (content filter in this case). I quick test showed
that postfix
Hello Wietse, postfix-users,
On 18.03.2013 12:01, Wietse Venema wrote:
Are there any plans to implement XCLIENT forwarding into postfix.
Please read the XFORWARD document.
I read the XFORWARD_README and I believe XFORWARD is what I want and
should use to get variables from postfix MTA to my
Hello postfix-users,
I'd like to somehow get/forward the SASL username of an authenticated
user to a before-queue SMTP content filter that is connected via
smtpd_proxy_filter.
I know I can use smtpd_sasl_authenticated_header = yes, but that is
not quite what I want or need as the scanner can only
Hey postfix-users and -abusers,
is there a postfix way to make use of a map (domain based) for the
selection of a (before-queue) smtpd_proxy_filter? The idea is to send
some domains through a certain smtpd_proxy_filter and maybe skip the
filter for others alltogether.
I do understand that
Hello postfix-users,
I'm looking for a way to limit the time or the number of messages an
established smtp authenticated session can be used for. I already have
rate limiting (anvil for anti-dos and policy delegation for maintaining
a quota per hour) in place.
But if I lock a (hacked) user
established and authenticed connections using an
automated solution as well.
On 27.07.2012 13:55, Christian Rohmann wrote: I could think of a few
techniques to find and tear down such unwanted
connections. But I hope that maybe I did miss some global setting in
postfix [...]
Before I create some
Hallo,
sorry for the late update ... but here it is ...
On 10/29/2010 10:35 PM, Wietse Venema wrote:
If I don't see a credible report about warnings etc. in Postfix
logfiles, then that means that you are flying blind, and that needs
to be addressed first.
Agreed. I did read the document
Hey postfix-users,
we are currently analyzing very strange postfix behavior which I can
only describe as lockup or freeze.
Honestly we reached our abilities to gather more info and to find the
root cause of this issue.
You are my last hope obi wan ... eh Wietse
--- Setup / Configuration
Hey Wietse,
thanks for the quick reply. Sorry for the delay, was a few GBs of logs
to grep through ;-)
On 10/29/2010 05:49 PM, Wietse Venema wrote:
I will assume that this is a bug in OS software or in emulated hardware.
Possible, but we are not really having a special setup ... just VMware +
Hey again,
On 10/29/2010 07:23 PM, Wietse Venema wrote:
The main loop in the master is as follows:
forever {
set an alarm for 1000s
do an EPOLL_WAIT for up to 500s and handle any child process
events, or short-term timer requests that are implemented
around the
14 matches
Mail list logo
