When a message is sent through Web Crossing:
If the email is accepted into webx from an outside email client (Outlook, Pegasus, Eudora, etc) via SMTP In, the first entry is similar to the following:
20-Jun-03 08:27:18 smtp-in OK (Received mail from: firstname.lastname@example.org to: email@example.com client-IP:188.8.131.52)
However that will not be present if the email is generated from within Web Crossing (say from a macro, or an outgoing subscription notification, or a WebMail generated email).
Followed shortly by:
20-Jun-03 08:09:46 smtp-out OK ID=2549 Send email. Outgoing message queued To: firstname.lastname@example.org From: email@example.com
Then when the email is successfully sent out of Web Crossing:
20-Jun-03 08:11:04 smtp-out OK ID=2549 Send email. Sent email To: firstname.lastname@example.org From: email@example.com
Occasionally, you may also see the following a number of times before the email is actually sent successfully, if so, ignore it as a transient problem (receiving email server is busy, temporarily offline, etc):
20-Jun-03 08:11:02 smtp-out error ID=2549 Send email. Connect error (Internet address disconnected.) To: firstname.lastname@example.org From: email@example.com
When a user checks email in Web Crossing:
A POP check looks like:
20-Jun-03 03:43:31 pop3 connect 184.108.40.206
20-Jun-03 03:43:31 pop3 OK LOGIN by support from 220.127.116.11
20-Jun-03 03:43:40 pop3 disconnect 18.104.22.168
An IMAP check looks like:
26-Jun-03 09:05:39 imap connect 22.214.171.124
26-Jun-03 09:05:39 imap OK LOGIN by Support from 126.96.36.199
26-Jun-03 09:05:39 imap disconnect 188.8.131.52
Mail accepted into, and destined for a Web Crossing account:
20-Jun-03 00:52:00 smtp-in OK (Received mail from: firstname.lastname@example.org: email@example.com client-IP:184.108.40.206)
Various Error Messages (trimmed for readability):
Could not deliver mail within NN hour(s)
Web Crossing gave up the delivery based on your "Maximum number of hours to hold undeliverable email:" control panel setting, and returned the email to the sender.
DNS lookup -- no host
Usually due to a forged domain name, but could be caused by a missing, incorrect, or failed DNS server setting in the Email Services Control Panel.
This user doesn't have a domainName.com account
No such user firstname.lastname@example.org
Internet address disconnected.
Mail delivery error ( <email@example.com> user unknown
<firstname.lastname@example.org>... User unknown
Fatal error from destination SMTP server ( not our customer)
Mail delivery error ( not our customer)
Requested action not taken: mailbox unavailable
Disconnected from: 0.1.2.3.4
These messages, and ones similar, all mean that the destination email account does not exist at the domain accepting the email, or the destination email server is otherwise rejecting your email.
Sorry, your message to email@example.com cannot be delivered. This account is over quota. – diapers.smell.com
These messages, and ones similar, mean that the destination email account has reached the maximum number of messages it is permitted to accept by their system administrator.
VS10-RT Possible forgery or deactivated due to abuse (#5.1.1))