SMTP Server problems, Anti-Spam and Windows Errors reported by FormTrap for SMTP: Versions 6 and 7 SMTP Server either responds to FormTrap server or does not, in which case FormTrap server considers it timed out 10 minutes later (that is the specification for SMTP which FormTrap respects). Anti-Spam Software may be the direct cause of timeouts, as may be different treatment of visible errors in the parameters passed to SMTP (SMTPTo and SMTPFrom). This documents identifies exceptions that are outside of FormTrap control. The first group are User Errors in SMTP parameters, second group are Anti-Spam and third group are Windows. User Errors Sending a website address in SMTPTo (ie missing the @ in the address): We have seen this stop the SMTP server cold, immediately. All following jobs stall in the Working Queue until they time out. If you have intermittent failure on long runs such as statements, you may well have a web site entry somewhere in your email addresses. You should look at the failed archive for the entry with a missing @ sign in its email address. If you catch this prior to timeout, you can resubmit all of the jobs in the Working Archive Display with the exception of the job with a Web Site address as SMTPTo (circled below).. You MUST modify the data in your system or this will happen next time and every subsequent time statement runs are a good example of a continually failing job through this cause..
Delimiters in SMTPFromName This happens commonly in the USA sending SMTPFromName as Name, Inc. where comma is assumed to be a delimiter and SMTP server cannot find either the Name nor Inc entries in its tables. You should change the name to a format without the comma. Errors reported by SMTP Server, incorrect Email addresses (dated August 2010) The SMTP server stopped accepting additional emails after returning an error code for illegal email addresses (the two cases were an email address of the form name@@website.com and name@website.com. - ends with a trailing full stop character). Both were errors in data, were reported by SMTP server to FormTrap and the SMTP server immediately stopped accepting any additional instructions. From FormTrap Spooler version 7.4.004 the routines have been amended so FormTrap disconnects from SMTP server when it receives an error and reconnects prior to the next message to SMTP server (customers current on Support and Upgrades may request the revised version).
Anti-Spam AVG Anti-Spam Filter Crashes (dated June 2010) The software does not handle load. (Please Google AVG or AVG Crash and see similar complaints from other users). AVG software crashes, remove the software entirely. White listing and other normal procedures do not resolve the issue, you will need to uninstall the AVG software and use another product which handles load and/or allows white-listing of the source of the email (FormTrap Spooler). This means the SMTP server program is left hanging and does not return a status to FormTrap, which waits 10 minutes (to SMTP server standards), then sends this message via Email to the FormTrap administrator: From: formtrap@custsite.com.au [mailto:formtrap@custsite.com.au] Sent: Thursday, 24 June 2010 10:34 AM To: Cust Person to receive FormTrap Failures Subject: Formtrap failure notification Formtrap job failed Submission Date/Time: 24/06/2010 9:42:40 AM Queue: email-fax Recipient: <recipient name="accounts@smtptocompany.com.au" class="to"/> Recipient type: smtp Reason: Failed in call to send MAIL command, OS error=10054 More information may be obtained from FTSpooler's archive or log file. This e-mail is auto-generated by Formtrap service. Please do not reply. To disable e-mail notification change the settings of the relevant queue This is the corresponding message from anti-spam, which arrived some time later, after the FormTrap error email for early outgoing emails presented to SMTP.: The message does not contain any threats AVG for MS Exchange Server (9.0.829-271.1.1/2959) A small number of emails are processed, then AVG crashes, not delivering further responses to SMTP server which therefore cannot reply to FormTrap. You will find this via the Event Log. This is not within FormTrap control, you will need to address this using resources other than FormTrap support, or if you do want our assistance be prepared to pay for services entirely outside of our normal support (and charged at nuisance rates). ATT0001.txt file delivered with your PDF via SMTP (dated November 2010) This is from anti-spam software.
Windows Outlook 2007 and FormTrap Emails (dated September 2010) Body text in Outlook either does not display or is corrupt when being read by Outlook 2007. Two sites reported problems with Emails when viewed with Outlook 2007, today, September 28 th, 2010. In the first case, a fax number appears illegible as shown (where the same email sent to FormTrap and read with Outlook 2003, Yahoo, Google and any other client is correct). This happens regardless of the location of the phone number, after 830 the remainder is illegible. These are screen shots from the first case: Outlook 2003 Tel +61 (0)8 8301 7777 Fax +61 (0)8 8384 7634 Outlook 2007: Tel +61 (0)8 830sss2[1][1][1] f[1]c [1][1] 3Cc The second case: here the body text cannot be seen at all (and is legible with Outlook 2003, Yahoo, Google etc.). Possible cause: This looks related to the standard use of Unicode by FormTrap for all body text being sent to SMTP which has been reliable since Version 6 some years ago. It appears there may be an issue with Unicode in Outlook 2007, although this is conjecture and needs further investigation. Please notify us if you find a cause/solution to this issue. 250 message limit in Exchange from the same source (dated October 2010) Exchange has a default of 200 or 250 messages from the same source, this conflicts with large runs, such as remittance advices or statement runs that are emailed. The limit is there to prevent Spam. http://www.eggheadcafe.com/software/aspnet/33635740/message-delivery-to-manyrecipients.aspx Exchange does not have any such limit for sending messages out.
However it does restrict more than 250 messages from the same IP if they are sent at the same time. We expect this limit can be changed in Exchange, but have not looked closely. This can be modified for you by our staff at consulting rates.