[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: smtp ta problem? (was: Re: hotmail problem... again :-( )
Hi,
has anyone looked at this?
I have a customer yelling at me because he's getting loads of bounces like
this one from hotmail and he's blaming our mailer... and the worst part is
that I'm think he's right!
I tried reading smtp.c but it's definitively too much for me... I'm too
old to C :-(.I tried to diff from the last version I had installed (which
I _think_ was working OK), but it is huge (a 2200 lines diff -u on a 5300
lines source):
cvs diff -u -D 2003-02-14 -D 2003-09-03 transports/smtp/smtp.c
I'm trying to follow the ChangeLog... I see a new ZENV variable
TA_USE_MMAP=0... would setting it to something else (or deleting it
entirely) change something that might be affecting me?
Newer changes (from September 9 until now) only seem to add new
functionality, so I don't think upgrading would put me in a better
situation...
Would an old smtp ta (e.g from Februrary) work within the newer zmailer?
scheduler/ta interaction shouldn't have changed...
El 16 Oct 2003 a las 17:23, Mariano Absatz escribió:
> Hi Matti,
>
> it happened again... though this time the smtp ta is being run with "-77",
> it is somehow bouncing a message with status "OK" (2.0.0) after being
> forcefully (and silently) disconnected from the smtp server.
>
> As the transcripts were rather long, I uploaded them so you can browse
> them.
>
> In http://www.baby.com.ar/ZMailer/hotmail-bounce.msg is the bounce message
> generated by zmailer.
>
> I edited it a little to delete all the "RELAYED" data and concentrate on
> the "FAILED" part. The edited message is at
> http://www.baby.com.ar/ZMailer/hotmail-bounce-edited.msg
>
> The smtp ta log corresponding to the specific smtp ta process is in
> http://www.baby.com.ar/ZMailer/smtpwebs.30529
>
> The edited version (only showing the job involved) is at
> http://www.baby.com.ar/ZMailer/smtpwebs-edited.30529
>
> Relevant parts of scheduler.conf follow:
>
> */* interval=1m
> idlemax=4m # Max lifetime of idled TA before it is killed
> expiry=3d
> expiry2=2d
> retries="1 1 2 3 5 8 13 21 34"
> maxchannel=0
> maxring=20
> maxta=0 # Let it be automagically determined
> user=root
> group=daemon
> ageorder
> overfeed=150
> # nice=2
> ##priority=0
> # sysnice=-2
> # syspriority=-2
>
> # smtp/*hotmail.com
> smtp/hotmail.com
> smtp/*.hotmail.com
> maxchannel=199
> maxring=33
> maxthr=8
> overfeed=20
> command="smtp -P -77 -s -l ${LOGDIR}/smtpwebs"
>
> Do you have any idea about what is going on?
>
> Thanx in advance.
>
> El 9 Oct 2003 a las 17:47, Mariano Absatz escribió:
>
> > Hi,
> >
> > I'm running 2.99.56-pre9 taken from CVS on September 3.
> >
> > A customer showed to me a bounce (alas, on paper) generated by thiz zmailer
> > which was rather weird.
> >
> > It was a failure report "Returned mail: see the transcript [FAILED(1)]"
> >
> > However, the Status was "2.0.0" (OK, IIRC) and the Diagnostic-Code was "250
> > (OK)".
> >
> > I don't understand why it is reporting a failure with "OK" status &
> > diagnostic codes...
> >
> >
> >
> > I'll transcribe below excerpts of the bounce mail (by hand) :-(
> > I'm attaching the smtp log.
> >
> > If I understand correctly, zmailer issues a EHLO, hotmail's exchange says it
> > supports PIPELINING, 8bitmime, etc.
> >
> > In log line 12092C031-0344-1804#, zmailer starts processing this job.
> >
> > It sends MAIL From:, RCPT To:, BDAT and RSET (using pipelining) and on line
> > 12092C031-0350-1804# it discovers remote hung up, and just below, says:
> > "smtp_sync() did yield code 75/TEMPFAIL".
> >
> > After that, it tries to reconnect (successfully) but sends another message...
> >
> >
> > I understand (from log line 12092C031-0351-1804#) that it is a temporary
> > failure, why, then, zmailer is issuing the failure report and not retrying?
> > And anyway, shouldn't the report say something about remote server hunging up
> > on us?
> >
> > The message, in fact, was actually bounced and didn't reach the recipient.
> >
> > After seeing this, I added a "-P -77" (would "-P" only suffice?) to the
> > relevant channel/host in scheduler.conf, however, this is not what was
> > usually happening with exchanges... IIRC, messages were kept in the scheduler
> > queue...
> >
> > ==================BOUNCE MESSAGE==========================
> > FAILED:
> > Arrived Recipient:
> > rfc822;XXXX@hotmail.com
> > Original Recipient:
> > rfc822;XXXX@hotmail.com
> > Final Recipient:
> > RFC822;XXXX@hotmail.com
> > Status:
> > 2.0.0
> > Remote MTA:
> > dns; mx4.hotmail.com (65.54.167.230|25|192.168.1.21|37774)
> > Last Attempt Date:
> > Tue, 7 Oct 2003 11:01:13 -0300
> > X-ZTAID:
> > smtp[12092]
> > Diagnostic Code:
> > smtp; 250 (OK)
> > Control data:
> > smtp hotmail.com XXXX@hotmail.com 99
> > Diagnostic texts:
> > <<- EHLO myhost.example.com
> > ->> 250-mc12-f32.hotmail.com (02.03.00.0022) Hello [1.2.3.4]
> > ->> 250-SIZE 35840000
> > ->> 250-PIPELINING
> > ->> 250-8bitmime
> > ->> 250-BINARYMIME
> > ->> 250-CHUNKING
> > ->> 250-VRFY
> > ->> 250-AUTH LOGIN
> > ->> 250-AUTH=LOGIN
> > ->> 250-X-HMAUTH
> > ->> 250 OK
> >
> > Following is a copy...
> > ...
> >
> > Reporting-MTA: dns; myhost.example.com
> > Arrival-Date: Tue, 7 Oct 2003 11:01:06 -0300
> > Local-Spool-ID: S1563667AbTJGOBG
> >
> > Original-Recipient: rfc822;XXXX@hotmail.com
> > Final-Recipient: RFC822;XXXX@hotmail.com
> > Action failed
> > Status: 2.0.0
> > Remote-MTA: dns; mx4.hotmail.com (65.54.167.230|25|192.168.1.21|37774)
> > Last Attempt Date: Tue, 7 Oct 2003 11:01:13 -0300
> > Diagnostic Code: smtp; 250 (OK)
> >
> > Following is copy of the message headers...
> > ...
> > ==================BOUNCE MESSAGE==========================
--
Mariano Absatz
El Baby
----------------------------------------------------------
I must say that I find television very educational.
The minute somebody turns it on, I go to the library and read a book.
-- Groucho Marx
-
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi