[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: more smtp ta doubts
On Thu, Oct 23, 2003 at 03:54:36PM -0300, Mariano Absatz wrote:
> I installed an smtp ta from March CVS (2.99.56-pre4) that was
> running before this one... I actually don't know if problems
> started after the upgrade, but just in case, I'm downgrading
> (only the smtp ta).
>
> I keep looking at the smtp logs and see strange things (for
> bounces, I have to wait for users to report it to my customer
> and then he sends them to me... quite annoyed, btw).
>
> Look at this (it is yahoo, not hotmail):
Yes. This is the older RSET processing, which didn't
RSET every time.. Or did reset in weird ways.
Partly things are confused by the protocol running in
PIPELINING client mode.
Now I think I have succeeded at creating nicely behaving
connection restart in case the cached socket has failed
when MAIL FROM is sent thru it.
At least it works for HOTMAIL now. (Which incidentally, seems
to be closing the SMTP connection right after the end of previous
message...)
> 11922176F-0047-0253# jobspec: F/T/1563737-18510 yahoo.com.ar
> 11922176F-0048-0253# 1563737-18510: <3BF9E40DA0FAE64AB79FD52405158F14031F9988@XCHADM1.uade.edu.ar>
> 11922176F-0049-0253w MAIL From:<rscher@uade.edu.ar> BODY=8BITMIME SIZE=1013593
> 11922176F-0050-0253w RCPT To:<javierduek@yahoo.com.ar>
> 11922176F-0051-0253w DATA
> 11922176F-0052-0253# Remote hung up on us while 3 responses missing
> 11922176F-0053-0253# smtp_sync() did yield code 75/TEMPFAIL
> 11922176F-0054-0253# (closed SMTP channel - after delivery failure)
> 11922176F-0055-0253# (Connecting to `mta-v21.level3.mail.yahoo.com' [64.156.215.6|25] Thu Oct 23 15:05:10 2003)
> 11922176F-0056-0254r 220 YSmtp mta199.mail.scd.yahoo.com ESMTP service ready
> 11922176F-0057-0254w EHLO alerce1-or.uade.edu.ar
> 11922176F-0058-0254r 250-mta199.mail.scd.yahoo.com
> 11922176F-0059-0254r 250-8BITMIME
> 11922176F-0060-0254r 250-SIZE 10485760
> 11922176F-0061-0254r 250 PIPELINING
> 11922176F-0062-0254# EHLO rc=0 demand_TLS_mode=0 tls_available=0
> 11922176F-0063-0254# smtpopen: status = 0
> 11922176F-0064-0254w MAIL From:<rscher@uade.edu.ar> BODY=8BITMIME SIZE=1013593
> 11922176F-0065-0254# jobspec: E/E/1563696-18511 yahoo.com.ar
> 11922176F-0066-0254# 1563696-18511: <3BF9E40DA0FAE64AB79FD52405158F14031F9989@XCHADM1.uade.edu.ar>
> 11922176F-0067-0254w RSET
> 11922176F-0068-0255r 250 sender <rscher@uade.edu.ar> ok
> 11922176F-0069-0255w MAIL From:<mbronenberg@uade.edu.ar> BODY=8BITMIME SIZE=3910
> 11922176F-0070-0255w RCPT To:<lucianadabat@yahoo.com.ar>
> 11922176F-0071-0255w DATA
> 11922176F-0072-0255r 250 reset ok
> 11922176F-0073-0255r 250 sender <mbronenberg@uade.edu.ar> ok
> 11922176F-0074-0255r 250 recipient <lucianadabat@yahoo.com.ar> ok
> 11922176F-0075-0256w .
> 11922176F-0076-0256r 354 go ahead
> 11922176F-0077-0256# 3833 bytes, 1390 in header, 1 recipients, 0 secs for envelope, 1 secs for body xfer
> 11922176F-0078-0256# jobspec: #idle
>
> Why does smtp ta starts processing a new jobspec
> (E/E/1563696-18511) when it hasn't finished the one before
> (F/T/1563737-18510), moreover, sending a RSET to an already
> restarted SMTP transaction (after a remote hungup)...
>
> I don't know if zmailer generated a bounce for this, but it's
> clear that it didn't retried it...
>
> Somehow, there seems to be a problem when smtp_sync() gets a
> 75/TEMPFAIL... is the caller ignoring the actual rc value and
> treating TEMPFAIL as a permanent failure?
>
> TIA
> --
> Mariano Absatz
> El Baby
--
/Matti Aarnio <mea@nic.funet.fi>
-
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi