Child's Play Technologies

The Marketing Email Send Log

Each time an email campaign is run, a send_log.txt file is created. The log file lists each recipient whether or not the email was rejected, if it was sent successfully, and a summary.

Recipient Keywords
Following is an explanation of keywords that may appear in the log next to a recipient email address.
  • Accepted - The recipient qualifies to be sent a message. This does not mean that an email was sent to the recipient, only that the recipient has a valid email address and is not excluded.
  • ALREADY PRESENTT - he recipient was not added because they are already in the list.
  • ALREADY SENT - The recipient received the message in an earlier mailing. This only occurs when "Only send when before"is checked.
  • BEGIN - The recipient specified in the "Begin With Recipient" fieldhas not yet been encountered.
  • CLAUSE # - The recipient is rejected because of a clause in the clause table. The row of the clause is listed inside parenthesis. This only appears when clauses are processed manually.
  • DISREGARDED(a) - The [[disregard]] statement was encountered in the list of attachments.
  • DISREGARDED(bcc) - The [[disregard]] statement was encountered in the "BCC:" header.
  • DISREGARDED(cc) - The [[disregard]] statement was encountered in the "CC:" header.
  • DISREGARDED(ch) - The [[disregard]] statement was encountered in the list of Custom Headers.
  • DISREGARDED(e) - The [[disregard]] statement was encountered in the HTML embedded fileslist.
  • DISREGARDED(ea) - The [[disregard]] statement was encountered in an explicit attachment.
  • DISREGARDED(f) - The [[disregard]] statement was encountered in the"From:" header.
  • DISREGARDED(h) - The [[disregard]] statement was encountered in the HTML Body.
  • DISREGARDED(r) - The [[disregard]] statement was encountered in the "Reply-To:" header.
  • DISREGARDED(rc) - The [[disregard]] statement was encountered in the "Reading Confirmation" header.
  • DISREGARDED(s) - The [[disregard]] statement was encountered in the subject.
  • DISREGARDED(se) - The [[disregard]] statement was encountered in the "Sender:" field.
  • DISREGARDED(t) - The [[disregard]] statement was encountered in the Text Body.
  • DISREGARDED(to) - The [[disregard]] statement was encountered in the "To:" header.
  • DOMAIN(e) - The recipient's domain has been excludedfrom the mailing.
  • DOMAIN(i) - The recipient's domain has not been includedin the mailing.
  • DUPLICATE - The recipient has already been included in the mailing (and "Eliminate Duplicates"is checked).
  • EXCLUDED - The recipient was found in the list of exclusions.
  • ILLEGAL ADDRESS - The recipient's email address is not of valid syntax. The address must contain exactly one @ sign.
  • INDEX - The recipient is not within the index filter range.
  • REMOVED - The recipient was previously removed by placing a checkmark in the "Removal column"identified on the Remove/Options branch.
  • REMOVED(!) - The first character of the recipient's address is an exclamation point, so the recipient was rejected.
  • retried - Direct Deliveryfailed, so the message will be resent to the default SMTP server.
  • success - The message was successfully sent to the recipient.
  • USER - The user name portion of the recipient's address was found in the Exclude Users field.
Common Errors
Following is a list of some common error codes that may appear in the Send Log.

Error 553 (5.7.1) Error 553 is a "feature" of your SMTP server. It will not let you send mail unless you are authenticated first. Sometimes you can become authenticated if you check for mail first. Otherwise, a user name and password will be required. This is designed to prevent others from sending spam through your account. Your ISP may be able to disable this safeguard.

Error 3007 Error 3007 indicates that the operating system could not establish a connection with a remote computer. This error is outside the scope of Gammadyne Mailer.

Error 3008 Error 3008 indicates that a timeout error occurred while waiting for a response from the SMTP server. Although a connection was established with the server, the server did not send a proper greeting within the timeout period, probably because it is under too much load. You should reduce the number of threadsin order to reduce the load on the mail server, switch to Direct Delivery, or extend the timeout period.

Error 3010 Error 3010 indicates that the SMTP Authenticationfailed. Either your user name or password is incorrect, the server does not require authentication, or Gammadyne Mailer does not support the server's authentication protocol. Gammadyne Mailer supports the PLAIN, LOGIN, and CRAM-MD5 protocols.

Error 4510 Error 4510 occurs when a connection cannot be made with the SMTP server. Check the following: Make sure you have the correct name of the SMTP server. Make sure the SMTP server's port number is correct. This is almost always 25. Make sure the DNS Server settingsare correct and that the DNS server is responding. Make sure you are using the correct authentication. Try it without authentication, as most SMTP servers do not require it. Try using POP3 authentication. Some servers may require that you check for incoming mail via POP3 before sending mail with SMTP. Try specifying the SMTP server's IP address instead of its name. Check to see if you can send email from another program using the same settings.

Error 4570 Error 4570 is caused when the SMTP server does not like something about the "From:" header. This can sometimes be solved by surrounding the address in < ... >. Also be aware that some mail servers will only transport mail that originates from or goes to one of its users.

Error 4590 - Relaying Denied By far the most common error encountered is "Relaying Denied", such as when the log shows one of the following messages:
505 Missing or incorrect domain in RCPT command
550 Mail relay not allowed at this server
SMTP Error 4590

A mail server will produce a "Relaying Denied" error when an unauthorized user attempts to send non-local email through the server. Non-local email is email which is addressed to a different server.

Mail servers will not relay mail from just anyone. Otherwise, spammers could flood the mail server, making it do their dirty work. You must be authorized to use a mail server. Unauthorized users will always receive the "Relaying Denied" error.

To use a mail server, you must prove to the mail server that you are authorized to send email.
  • The sender of the email must be a user on the server. In Gammadyne Mailer, this corresponds to the "Sender:" fieldon the "Headers" branch.
  • Some servers require that the "From:" email header is a user on the server.
  • If the mail server is on a Local Area Network, it may be necessary to specify the mail server's local IP address, not its name.
  • This error can sometimes be circumvented by first checking for incoming email. Some servers are smart enough to recognize that when you are properly authenticated to receive mail, then you should also be able to send mail.
  • It is also possible that the mail server will only relay mail for users that are currently connected to the ISP. If you want to be able to send mail when using a different connection, you will need to ask your ISP if "SMTP authenticated login" is supported. If it is, they will give you a user name and password. Enter this information on the SMTP branch.
  • Occasionally, a mail server may require that the email program say hello properly. This corresponds to the HELO or EHLO command in the SMTP protocol. The mail server may require that this command reports a proper domain name that is authorized to send email. Even though this practice is discouraged, some mail servers perform this check as a form of spam prevention. In Gammadyne Mailer, this corresponds to the "Override EHLO Domain" fieldon the Send branch.
  • Error 4590 will also occur when attempting to deliver an email to a nonexistent mailbox. Don't confuse this with the Relaying Denied problem, which occurs for all non-local mailboxes.
The only other solution is to not use the mail server at all. Check the "Direct Delivery" boxon the "Send" branch. This will bypass the SMTP server altogether, and deliver each email directly to the recipient. This has the additional benefit of eliminating a point of failure.

Error 4640 Error 4640 indicates that the mail server did not respond properly after the message body was delivered. This may result from a broken connection, or the recipient mailbox may be invalid. Whatever the reason, the email could not be delivered.

Winsock Error 10051 Socket error 10051 is indicative of an improperly configured network. This problem is outside the scope of Gammadyne Mailer. Following is the official explanation for this error code:

The local network system can generate this error if there is no default route configured. Typically though, Winsock generates this error when it receives a "host unreachable" ICMP message from a router. The ICMP message means that a router cannot forward the IP datagram, possibly because it did not get a response to an ARP request (which might mean the destination host is down).

Winsock Error 10054 - Cause: The remote computer closed the connection for unknown reasons. There may be a problem with the remote computer, or it may be specifically refusing connections from you. In any case, this error code does not involve Gammadyne Mailer directly because the operating system is responsible for establishing all remote connections.

Solution: Contact the remote machine's administrator. Try connecting from a different machine. Winsock Error 10055 Cause: An operation on a socket was not performed because the system lacked sufficient buffer space or because a queue was full. This error indicates a shortage of resources on your system. It can occur if you're trying to run too many applications (of any kind) simultaneously on your machine. Solutions: Reboot the machine. Reduce the number of Threads on the Send branch. Install the latest operating system service pack. Consider upgrading to Windows 2000 or XP.

Winsock Error 10061 This can occur when the server is too overloaded to accept new email. The server is actively refusing to allow your connection. This error code does not involve Gammadyne Mailer directly because the operating system is responsible for establishing all remote connections.

Solutions:
  • Reduce the number of Threads on the "Send" branch.
  • Use the Throttle in the SMTP Server Table on the "SMTP" branch.
  • Use the "Direct Delivery" feature(on the "Send" branch) to bypass the SMTP server altogether.
  • Wait a bit and try again.
Winsock Error 10065 Error 10065 is indicative of a network problem that is outside the scope of Gammadyne Mailer. Try bypassing your mail server by using the Direct Delivery featureon the "Send" branch.

Copyright 2002, Child's Play Technologies, LLC