[Users] claws mail network log and SMTP timing

[wwp]

Hello Dave,


On Mon, 29 Apr 2019 17:33:12 +0100 Dave Howorth <dave at howorth.org.uk> wrote:

> > > And does 'SMTP> . (EOM)' mean that is
> > > the timestamp at which the end of the message was sent?    
> > 
> > Sending . means sending end of message. This is
> > SMTP-protocol-dependent.  
> 
> I don't understand what you mean here. Has the last byte of the message
> been sent at this time or not, is the question I'd like to answer.

The answer to your former question is "yes", provided that I understand
your question, which is not 100% sure. Is it grammatically correct? If
so, please forgive my Engrish!


> > > So the delay is
> > > definitely claws waiting for the SMTP server to respond, not the
> > > SMTP server waiting for claws to send something?    
> > 
> > I think so, even if I've never such delay. Are you sending huge emails
> > w/ tons of recipiends and attachments? They parse the email,
> > potentially "long" studies (and usually, recipients are validated
> > before that step, which can take a looong time too, could take 1-3 sec
> > per recipient as I could see here).  
> 
> My ignorance is confusing me. I thought SMTP servers received messages,
> queued them and then forwarded them. So I'd expect them to close the
> incoming connection when they have queued the message, which could be
> seconds, minutes or indeed hours before they processed the mail such as
> validating recipients. Is that not correct?

I do not know what your ISP's SMTP server does at this last step (when
it appears to stick for a while). The log is not showing more since the
SMTP server doesn't say what is done, and IIRC, at this step in the SMTP
protocol, nothing more informative is expected. What is certain is that
the delay is on SMTP-server side.


Regards,

-- 
wwp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://lists.claws-mail.org/pipermail/users/attachments/20190429/97db9c1b/attachment-0001.sig>