Skip to main content
Participating Frequently
February 26, 2010
Question

cfmail glitches in ColdFusion 9 (not sending, but says sent)

  • February 26, 2010
  • 11 replies
  • 24755 views

I'm seeing the strange behavior with basic cfmail sends in CF9.  CF9 has an entry in the mailsent log  that is was successfully sent but on the MailEnable logs (Mailenable exists on the same server as CF and CF sends all it's l through it) there wasn't even a connection attempt.  Now  this is a my bulk  mail server and I'm probably averaging about 70,000 e-mails a day from that server and most mails go through just fine.

What i've discovered about the few that don't is they have a few things in common. Anything that goes out with a "mailworker" thread works 100% of the time.  Mail that goes out as a "scheduler" thread seems to be 50/50".   There is no spam filter involved here.  I'm just checking logs from the CF side and from the mailenable side.  CF says is was sent....mailenable doesn't ever see an attempt at that time. I've seen this on another of my CF9 servers that relays through our ISP's SMTP server.  CF send it was sent in the mail sent log, but ISP has to record of a conenction attempt let alone a full message at that time.  I think there is a CF9 cfmail bug,  I never had an issue with this on CF8 (or cf7 for that matter).  The setup was exactly the same.  These problems just started a couple mounth ago when we upgraded to CF9.

Anyone have any ideas, or if other people think this sounds like a bug how I can prove it to Adobe?

-Dan

    This topic has been closed for replies.

    11 replies

    October 29, 2010

    Just a note to let you know that I'm experiencing the same issue.  Hundreds of emails go out fine and then one will show up as successful in the ColdFusion mailsent logs but will not even appear in the email server logs ~ no error message, not even a connection attempt.  You make a good point about the "scheduler" thread ID and the "mailWorker" thread ID as this has only happened with "scheduler" thread IDs.  I'm on Windows 2008 Enterprise Server (32bit) with ColdFusion Standard 9.01.  The email server is running Merak/IceWarp. I am unable to duplicate the problem; it just happens randomly.  I was going to try a new email server, but if you're experiencing the same problem on a completely different email server it sounds like it very well could be ColdFusion bug. 

    Tom

    booster94Author
    Participating Frequently
    October 29, 2010

    Ahh...finally!  I was really starting to doubt my sanity.  We just upgraded

    to Update 1 with CHF 1 hoping that might fix something (although nothing in the fix list indictated it would) but the problem persists.  I'm now 9.01 CHF 1 32bit on Windows Server 2003 Standard.  The mail server is on the same box as this server is pretty much dedicated to e-mail (mostly bulk mailings, but not all) so there are no network devices at all in between...the server is basically delievering the mail to itself, and then out to the internet.  I was using MailEnable 1.0 for the mail server program but upgraded to the most recent version (i think it's version 4) after i started seeing these issues crop after shortly after upgrading to CF9, but that made no difference.  These issues never happened when we were using CF8.

    We typically notice it when our support team replies to a customer through our ticketing system that sends e-mails out through CF.  Sometimes it works fine, other times it doesn't.  They have gotten into the habit of copying themselves on those e-mails to see if they are actually going out.  If they don't see the e-mail after 10-15 minutes they resend and it seems to work fine on the subsequent try.

    Like you, I'm unable to reproduce this on demand, but it does still happen randomly.  I don't have a good understanding of when a thread uses "mailworker" vs "scheduler".  Maybe if i knew more about that i could come up with a hypothosis, but right now I have no idea..  I'm surprised more people haven't been talking about this.  Maybe they just have't noticed.  Hopefully Adobe will take notice of this thread.

    October 29, 2010

    I also suspected a possible network issue, so it's interesting to know that you have the email server on the CF Server box.  I'm using cfmail to send out a notification of an external user form submission, so I can't even use a 'bcc' to catch this problem.  Since the email server is not even showing the connection from CF 9, it's as if CF 9 is just marking the email as sent without any connection to (or confirmation from) the email server.   I have screen shots from the CF 9 mailsent log and the corresponding email server log showing that there is no connection to the email server at the time CF 9 records that it successfully sent the email. Emails before and after the missing email show up in both the CF mailsent log and the email server log and go out as expected.

    It seems to be a rare occurrence, so it doesn't surprise me that more people haven't noticed it or they blame it on the emails getting lost in cyberspace.  In the past 3 weeks I've confirmed it happened twice, but that's only because one of my clients noticed it when they received email notification of a new form submission and then found a previous form submission in the database that they did not get an email notice for.  When I looked up the email, CF shows it as sent but it's nowhere in the email server logs.  This is bad because without the email, my clients don't know that a new form has been submitted until they login to my application and check the database; the point of the email is to let them know exactly when they have to check the database for a new form submission.

    Does anyone know the difference between a cfmail "mailworker" ThreadID and a "scheduler" ThreadID?   Is there any way to force cfmail to send using a "mailworker" thread?   I guess another idea would be to try spoolenable="no" for the specific cfmail tag since these are not bulk emails.

    Tom