unsubscribe

2015-07-15 9:17 GMT-03:00 mlist <[email protected]>:

> We take a tcpdump. Following the tcp traffic we can see each step.
> Reproducing manually the mail was sent. Probably HAProxy SMTP communication
> has an error on the final stage <CRLF>.<CRLF> as of that all goes right.
>
> Follows manual communication with mmail server reproducing tpcdump smto
> command seguence.
> EHLO smtp1
> 250-MAIL1 Hello [192.168.1.x]
> 250-SIZE 10485760
> 250-PIPELINING
> 250-DSN
> 250-ENHANCEDSTATUSCODES
> 250-STARTTLS
> 250-AUTH
> 250-8BITMIME
> 250-XEXCH50
> 250 XSHADOW
> MAIL FROM:<loadbha1@domain>
> 250 2.1.0 Sender OK
> RCPT TO:<alerts@domain>
> 250 2.1.5 Recipient OK
> DATA
> 354 Start mail input; end with <CRLF>.<CRLF>
> From: loadbha1@domain
> To: alerts@domain
> Date: Wed, 15 Jul 2015 12:50:48 +0200 (CEST)
> Subject: [HAproxy Alert] Server <backend>/webhost1 is DOWN, reason: Layer4
> timeout, check duration: 5002ms. 1 active and 0 backup servers left. 0
> sessions active, 0 requeued, 0 remaining in queue
>
> Server <backend>/webhost1 is DOWN, reason: Layer4 timeout, check duration:
> 5002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued,
> 0 remaining in queue
> .
> 250 2.6.0 <7c4f8f74-8d6b-446e-a504-e7a45fc58baf@MAIL> [InternalId=293812]
> Queued mail for delivery
>
> Entering manually all these commands we correctly receive the email.
>
>
> Dr. Roberto Cazzato
> Divisione ICT e Sicurezza
> Senior IT Designer
> gsm +39 348 22 00 850
>
> A.P. SYSTEMS s.r.l.
> 20013 Magenta (Milano)
> Via Milano 89/91 (ang.Via Cimarosa) Italia - www.apsystems.it
> tel. +39 02 97226.1 - fax 02 97226.339
>
>
> -----Original Message-----
> From: Baptiste [mailto:[email protected]]
> Sent: mercoledì 15 luglio 2015 12.01
> To: mlist
> Cc: [email protected]
> Subject: Re: Mailer does not work
>
> On Wed, Jul 15, 2015 at 9:48 AM, mlist <[email protected]> wrote:
> > We compiled from source haproxy-1.6-dev2.tar.gz. New Mailers mechanism
> does
> > not seems to work, we configured as on manual:
> >
> >
> >
> > mailers apsmailer1
> >
> >    mailer smtp1 <mailserver ip>:10025
> >
> >
> >
> > …
> >
> > …
> >
> >
> >
> > backend somebackend_https
> >
> >    mode http
> >
> >    balance roundrobin
> >
> >    …
> >
> >    email-alert mailers apsmailer1
> >
> >    email-alert from <from mail>
> >
> >    email-alert to <to mail>
> >
> >   email-alert level info
> >
> >    …
> >
> >
> >
> > We see in haproxy.log server status change:
> >
> > Jul 15 09:42:00 localhost.localdomain haproxy[3342]: Server …/<server1>
> is
> > UP, reason: Layer4 check passed, check duration: 0ms. 2 active and 0
> backup
> > servers online. 0 sessions requeued, 0 total in queue.
> >
> > Jul 15 09:42:00 localhost.localdomain haproxy[3342]: Server …/<server1>
> is
> > UP, reason: Layer6 check passed, check duration: 1ms. 2 active and 0
> backup
> > servers online. 0 sessions requeued, 0 total in queue.
> >
> >
> >
> > But no mail alerts are sent, no error or warning logged about sending
> mail.
> >
> >
> >
> > haproxy -f /etc/haproxy/haproxy.cfg –c
> >
> > does not return any error. All seems to be right, but mail alerts are not
> > sent.
> >
> >
> > Roberto
> >
>
> Hi Roberto,
>
> Could you please take a tcpdump on port 10025 and confirm HAProxy
> tries to get connected to the SMTP server?
>
> Baptiste
>
> --
> Il messaggio e' stato analizzato alla ricerca di virus o
> contenuti pericolosi da MailScanner, ed e'
> risultato non infetto.
>
>


-- 
Atte
Jorge Severino
Numero movil Personal: 08-7775834

Reply via email to