Skip to main content
cherdt
cherdt
Inspiring
March 5, 2008
Question

cfmail and EOF messages in mail.log

  • March 5, 2008
  • 3 replies
  • 1747 views
Sporadically, we're seeing that messages that should have been sent via a cfmail tag are lingering in the undeliverable mail folder. The mail.log file shows entries to accompany these undeliverable messages that look like this:

"Error","jrpp-1602","03/04/08","21:51:39",,"[EOF]"

I know that EOF signifies End-Of-File, but what does that mean in this context? If we move the undeliverable message back to the spool folder, the message gets delivered without any futher ado.
    This topic has been closed for replies.

    3 replies

    D
    Dan_Bracuk
    Inspiring
    September 15, 2008
    Our approach is to run a task every 15 minutes that copies mail files from undeliverable to spool, AND send an email to the administrators. If the 2nd attempt is successful, life is good. Otherwise, eventually one of the administrators will get tired of all the mail they are getting and investigate.
    A
    Anonymous
    July 29, 2008
    Has anyone figured out a solution to this? I'm having the same problem.

    Thanks
    Jeff
    cherdt
    cherdtAuthor
    Inspiring
    September 12, 2008
    The primary and backup mail servers we have listed are both Barracuda spam firewalls. When we check the Barracuda logs for the messages that produced the EOF message (and get moved to the Undelivr folder), it indicates that there was a client timeout. It does not appear that the Barracuda systems were under a particularly high load at the time, so my current theory is that there was some kind of network hiccup and that breaks the connection.

    It's frustrating that ColdFusion does not attempt to re-queue the message, but ColdFusion isn't an MTA--I suppose one solution would be to run an SMTP server on the ColdFusion host, as it should always be able to connect and maintain a connection to 127.0.0.1, but that seems less than ideal--we'd like to keep the two services as separate as possible.

    We've also increased the connection timeout from the default (30 seconds) to 600 seconds, which seems a little absurd, but it does seem to have reduced (though not entirely eliminated) the errors.

    Any tips or suggestions are greatly appreciated--we'd definitely like to eliminate these errors entirely.
    A
    Anonymous
    March 21, 2008
    I'm seeing this same problem. Does anyone have any idea on this?
    cherdt
    cherdtAuthor
    Inspiring
    March 21, 2008
    In my case, I found that the cfmail tag in one of our applications was setting the spoolenable attribute to "no", overriding our mail spool setting the CF administrator.

    I removed the spoolenable="no" attribute and haven't seen the problem since.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices