On 4/8/2012 1:25 πμ, Morten Stevens wrote:
If you want to try it:
http://download.imt-systems.com/postfix/2.9.4/
Thanks Morten,
I tried it and initially it did not work (same problem). I guess
something might have been broken in this system.
I then did a system upgrade and after that I
I have configured postfix with multiple instance (around 10) on my centos 6.2
server with postfix 2.6.6 .It's working fine but when server get blacklisted
or down I need to configure other server which takes a lot of time that's
why i want to create a script for multiple postfix instance creation
Naval saini:
I have configured postfix with multiple instance (around 10) on my centos 6.2
server with postfix 2.6.6 .It's working fine but when server get blacklisted
or down I need to configure other server which takes a lot of time that's
why i want to create a script for multiple postfix
On 4/8/2012 11:11 πμ, Nikolaos Milas wrote:
I guess something might have been broken in this system.
In /var/log/messages I found large number of errors like:
Aug 3 14:41:13 dc kernel: smtp[13853]: segfault at 1 ip
7f9522e38596 sp 7fff633a5fc0 error 6 in
On 04.08.2012 15:50, Nikolaos Milas wrote:
On 4/8/2012 11:11 πμ, Nikolaos Milas wrote:
I guess something might have been broken in this system.
In /var/log/messages I found large number of errors like:
Aug 3 14:41:13 dc kernel: smtp[13853]: segfault at 1 ip
7f9522e38596 sp
Would someone kindly point me to the docs that describe the behavior of
smtpd socket open time in relation to clients that do connection caching?
I've been assisting in a troubleshooting effort. A sendmail/mailman
based list server is opening more than 4 concurrent connections to my MX
even when
Stan Hoeppner:
Would someone kindly point me to the docs that describe the behavior of
smtpd socket open time in relation to clients that do connection caching?
http://www.postfix.org/postconf.5.html#smtpd_timeout
It's stress-dependent.
I've been assisting in a troubleshooting effort. A
I'm not addressing the subject of the post, but just picking over the
configuration snippet.
On Wed, Aug 01, 2012 at 09:48:45PM -0500, Chad M Stewart wrote:
[root@mta01 /usr/local/etc/postfix]# postconf -n|grep postscreen
[snip]
postscreen_client_connection_count_limit = 10
I'm not sure why
On Sat, Aug 04, 2012 at 09:11:07AM -0500, Stan Hoeppner wrote:
Would someone kindly point me to the docs that describe the behavior of
smtpd socket open time in relation to clients that do connection caching?
$ postconf -d smtpd_timeout
smtpd_timeout =
On 8/4/2012 9:19 AM, Wietse Venema wrote:
Stan Hoeppner:
Would someone kindly point me to the docs that describe the behavior of
smtpd socket open time in relation to clients that do connection caching?
http://www.postfix.org/postconf.5.html#smtpd_timeout
It's stress-dependent.
Thanks
On 4/8/2012 4:58 μμ, Morten Stevens wrote:
Do you have an IPv6 address in your /etc/resolv.conf?
Thanks Morten for the feedback,
Yes, I had IPv6 address(es) in /etc/resolv.conf !
Things are clearer now!
I had:
Jul 13 12:10:30 Updated: glibc-2.12-1.80.el6.x86_64
Jul 13 12:11:43 Updated:
On Aug 4, 2012, at 10:08 AM, /dev/rob0 wrote:
I'm not addressing the subject of the post, but just picking over the
configuration snippet.
On Wed, Aug 01, 2012 at 09:48:45PM -0500, Chad M Stewart wrote:
[root@mta01 /usr/local/etc/postfix]# postconf -n|grep postscreen
[snip]
Am 04.08.2012 23:41, schrieb Chad M Stewart:
postscreen_greet_banner = Welcome to our mail server
This is non-compliant and a bad idea.
That is prepended to the banner, the banner becomes a multi-line response,
with the last line being the fqdn of the host.
this is a bad idea, this was
13 matches
Mail list logo