XMailforum is a readonly knowledge archive now.

Registering as a new user or answering posts is not possible anymore.

Might the force be with you, to find here what you are looking for.

2019-09-20 - hschneider, Admin

Cookie Disclaimer: This forum uses only essential, anonymous session cookies (xmailforum*), nothing to be scared of.

XMail Forum [Powered by Invision Power Board]
Printable Version of Topic
Click here to view this topic in its original format
XMail Forum > Documentation and Knowledge Base > End of socket stream data


Posted by: hschneider May 2 2004, 07:55 AM
Meanwhile I collected some more information about this very unclear error message. The following article will go into the builtin knowledgebase of the next XQM release. I'm pretty sure this will help many people running into this situation:

QUOTE

NETWORK?

XMail assumes, that you have a network problem or a bad routing to
the recipient's host. This error comes up, when a connection is
dropped or cannot be established.

Possible reasons for this are
- The recipient's address is malformed
- The recipient's SMTP server dropped the connection, because his
  RDNS check has failed.
- The recipient's SMTP has connection problems.
- Your TCP/IP packets are lost on the route to the recipients SMTP
  (MX Server).
 
Things to check:

Your Firewall
If you are behind a F-Secure (or similar) firewall and this error
only happens when sending large attachments, then your problem IS
the firewall. In that case you should contact the FW support or
migrate to another firewall.

Your RDNS entry
To check your RDNS entry, use the services under
http://www.dnsstuff.com
Does your mail_from match your RDNS entry?
If your mail was generated by a PHP script, make sure that SMTP_FROM
is set to a valid host name in your PHP.INI.

Your hardware
If you can exclude the above then please check if
- Your network hardware (NIC, cabling, switch, HUB etc.) is intact and
- your router and firewall are setup correctly.

Your routing
To verify a recipient's host side problem, get the destination's
MX record from the SLOG file. Then do a

tracert mx_record_of_recipient  (on WINDOWS)
traceroute mx_record_of_recipient  (on UNIX like platforms)

This will print the routing and the time until your packets arrive
on each node on your route. It will also tell you the exact node,
where the routing is interrupted (marked with a '*' and no time value).

When you can verify a bad routing and your packets are not lost
inside your LAN, then you have no further influence on this
NETWORK issue. Just leave the mail inside the queue and defrost it
from time to time until it gets through (or increase the timeout
until XMail freezes messages).


Posted by: matrice64 Jun 18 2004, 09:59 PM
I get this when I do CtrlClnt -s <domain> -u <user> -p <passwd> <command> , is the above sitiuation(s) apply to this as well?

edit: I'm using .20 btw

Posted by: hschneider Jun 19 2004, 09:35 PM
No. There is something wrong with your username or password. Typically XMail cancels the connection when there are special chars used like e.g. german Umlauts or french accents. These are not allowed in CTRL accout data.

Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)