When mails are submited from application these parameter commented in
main.cf file
#postscreen_upstream_proxy_protocol = haproxy
#postscreen_upstream_proxy_timeout = 1s
#smtpd_upstream_proxy_protocol = haproxy

server relaying mails and and tcpdump shows

tcpdump -s0 -w file.cap
tcpdump: WARNING: arptype 65535 not supported by libpcap - falling back to
cooked socket
tcpdump: listening on venet0, link-type LINUX_SLL (Linux cooked), capture
size 65535 bytes
294 packets captured
296 packets received by filter
0 packets dropped by kernel

 tcpdump -ni venet0 -s0 -w file.cap port 25
tcpdump: WARNING: arptype 65535 not supported by libpcap - falling back to
cooked socket
tcpdump: listening on venet0, link-type LINUX_SLL (Linux cooked), capture
size 65535 bytes
323 packets captured
324 packets received by filter
0 packets dropped by kernel


When mails are submited from application these parameter are not commented
in main.cf file
postscreen_upstream_proxy_protocol = haproxy
postscreen_upstream_proxy_timeout = 1s
smtpd_upstream_proxy_protocol = haproxy

server stops relaying of  mails and and tcpdump shows
tcpdump -s0 -w file.cap
tcpdump: WARNING: arptype 65535 not supported by libpcap - falling back to
cooked socket
tcpdump: listening on venet0, link-type LINUX_SLL (Linux cooked), capture
size 65535 bytes
41 packets captured
43 packets received by filter
0 packets dropped by kernel



tcpdump -ni venet0 -s0 -w file.cap port 25
tcpdump: WARNING: arptype 65535 not supported by libpcap - falling back to
cooked socket
tcpdump: listening on venet0, link-type LINUX_SLL (Linux cooked), capture
size 65535 bytes
40 packets captured
41 packets received by filter
0 packets dropped by kernel
 now tell me where the problem and logs of load balancer are
/var/log/mailllog
Sep  7 17:12:14 r22 postfix/smtp[7362]: 47A8B1F54156: to=<
bournbo...@gmail.com>, relay=gmail-smtp-in.l.google.com[173.194.64.26]:25,
delay=1.9, delays=0.4/0/0.21/1.3, dsn=2.0.0, status=sent (250 2.0.0 OK
1347023531 b10si6583182oee.33)
Sep  7 17:12:14 r22 postfix/qmgr[6035]: 47A8B1F54156: removed
Sep  7 17:12:14 r22 postfix/cleanup[7175]: 154991F54154: message-id=<
a68a1d0a9b810e18fb79787cd9e20...@test.25smtp.com>
Sep  7 17:12:14 r22 postfix/postfix-script[7386]: stopping the Postfix mail
system
Sep  7 17:12:14 r22 postfix/master[6034]: terminating on signal 15
Sep  7 17:12:30 r22 postfix/postfix-script[7461]: starting the Postfix mail
system
Sep  7 17:12:30 r22 postfix/master[7463]: daemon started -- version
2.10-20120902, configuration /etc/postfix
Sep  7 17:12:30 r22 postfix/qmgr[7464]: 1F2FF1F54153: from=<
bou...@test.25smtp.com>, size=7874, nrcpt=1 (queue active)
Sep  7 17:12:31 r22 postfix/smtp[7468]: 1F2FF1F54153: to=<monu2...@gmail.com>,
relay=gmail-smtp-in.l.google.com[173.194.64.26]:25, delay=25,
delays=24/0.01/0.21/0.58, dsn=2.0.0, status=sent (250 2.0.0 OK 1347023548
b10si6586615oee.28)
Sep  7 17:12:31 r22 postfix/qmgr[7464]: 1F2FF1F54153: removed
Sep  7 17:12:31 r22 postfix/postscreen[7469]: warning: haproxy read: time
limit exceeded
Sep  7 17:13:02 r22 last message repeated 15 times
~

log of node server
/var/log/maillog

Sep  7 16:31:40 r23 postfix/master[1783]: terminating on signal 15
Sep  7 16:31:40 r23 postfix/postfix-script[2019]: starting the Postfix mail
system
Sep  7 16:31:41 r23 postfix/master[2021]: daemon started -- version
2.10-20120902, configuration /etc/postfix
Sep  7 16:55:14 r23 postfix/postfix-script[5465]: stopping the Postfix mail
system
Sep  7 16:55:14 r23 postfix/master[2021]: terminating on signal 15
Sep  7 16:55:15 r23 postfix/postfix-script[5539]: starting the Postfix mail
system
Sep  7 16:55:15 r23 postfix/master[5541]: daemon started -- version
2.10-20120902, configuration /etc/postfix



On Fri, Sep 7, 2012 at 4:02 PM, Wietse Venema [via Postfix] <
ml-node+s1071664n50354...@n5.nabble.com> wrote:

> Naval saini:
> > and regarding to smtp trafic when i connect my load balancer from my php
> > application this shows
> > "* 421 4.3.2 No system resources"*
>
> You have haproxy turned on in postscreen, but your load
> balancer is not sending the haproxy protocol.
>
> Where is the tcpdump output file?
>
>         Wietse
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://postfix.1071664.n5.nabble.com/postfix-version-2-10-20120902-relay-issue-tp50315p50354.html
>  To unsubscribe from postfix version 2.10-20120902 relay issue, click 
> here<http://postfix.1071664.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=50315&code=c2FpbmluYXZhbDU4QGdtYWlsLmNvbXw1MDMxNXwyODE4NTg0MTY=>
> .
> NAML<http://postfix.1071664.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: 
http://postfix.1071664.n5.nabble.com/postfix-version-2-10-20120902-relay-issue-tp50315p50361.html
Sent from the Postfix Users mailing list archive at Nabble.com.

Reply via email to