[EMAIL PROTECTED] wrote:
>I've got problems with sites that limit their message size.
>One example site uses some kind of sendmail that also logs
>the whole conversation. This is from the remote end:
>
>03-29-2000.00:04:09 SMTPresponder-26115: << DATA
>03-29-2000.00:04:09 SMTPresponder-26115: created temp file:
>/var/spool/MHS2/SMTPresponder-SMTP-in/TEMP.6603.38e18ec9.7fb90.1
>03-29-2000.00:04:09 SMTPresponder-26115: >> 354 Enter mail, end with "." on a line by
>itself
>03-29-2000.00:19:26 SMTPresponder-26115: size of data portion from 192.168.2.2
>exceeded maximum
>03-29-2000.00:19:26 SMTPresponder-26115: >> 552 message size exceeds maximum message
>size
>03-29-2000.00:19:26 SMTPresponder-26115: 192.168.2.2 did not send <CR><LF>.<CR><LF>,
>message discarded
>
>
>Locally I get:
>
>03-29-2000.00:19:27.702631 delivery 4: deferral:
>Connected_to_192.168.1.1_but_connection_died._(#4.4.2)/
Looks like the remote MTA is sending that 552 message while qmail is
still transmitting data, which I think violates the SMTP protocol. I'm
not an SMTP expert, but I really doubt qmail is misbehaving. Dan is
just too careful to miss something like that.
>I would like to see qmail bouncing this mail immediately stating to
>the sender that the message was too big instead of trying the
>message again and again to no avail except filling the pipe.
It's retrying because the remote end is breaking the connection
prematurely. The remote site should wait until qmail is done sending
the data before it responds with the 552 message.
-Dave
