Skip to main content
B
bjnolley
New Participant
September 19, 2008
Answered

CFMail won't send email with FQDN

  • September 19, 2008
  • 2 replies
  • 979 views
The CFMAIL won't include the fully qualified domain name (FQDN).

I found Knowledge Base article kb400753 at http://www.adobe.com/go/kb400753 and added
-Dmail.host=server-name.domain-name.com to the JVM Arguments section, as instructed by this article.

It did not make any difference. First I restarted just the CF server. When it still didn't send the email, I rebooted the entire Windows 2003 server and it still didn't help.

According to our web host, the following error was still occurring:

Sep 18 17:22:11 mail postfix/smtpd[55543]: NOQUEUE: reject: RCPT from domain-name.com[209.50.251.106]: 504 5.5.2 <server-name>: Helo command rejected: need fully-qualified hostname; from=<email-address@rvnetworking.com> to=<email-address@rvnetworking.com> proto=ESMTP helo=<server-name>

I'm out of ideas on this one!
    This topic has been closed for replies.
    Correct answer Newsgroup_User
    bjnolley wrote:
    > Do you know how to configure CF to send the FQDN in the HELO?

    http://jochem.vandieten.net/2008/09/19/configuring-coldfusion-to-use-a-fqdn-in-the-cfmail-ehlo/

    Jochem


    --
    Jochem van Dieten
    Adobe Community Expert for ColdFusion

    2 replies

    B
    bjnolleyAuthor
    New Participant
    September 19, 2008
    This was the info I needed … it solved my problem … thanx!
    N
    Newsgroup_User
    Inspiring
    September 19, 2008
    bjnolley wrote:
    > The CFMAIL won't include the fully qualified domain name (FQDN).
    >
    > I found Knowledge Base article kb400753 at http://www.adobe.com/go/kb400753
    > and added
    > -Dmail.host=server-name.domain-name.com to the JVM Arguments section, as
    > instructed by this article.
    >
    > It did not make any difference.

    That is correct, KB 400753 is only about changing the name in the
    MessageID, not in the HELO/EHLO.


    > Sep 18 17:22:11 mail postfix/smtpd[55543]: NOQUEUE: reject: RCPT from
    > domain-name.com[209.50.251.106]: 504 5.5.2 <server-name>: Helo command
    > rejected: need fully-qualified hostname; from=<email-address@rvnetworking.com>
    > to=<email-address@rvnetworking.com> proto=ESMTP helo=<server-name>

    What have you filled out in CF as the mail server? What is the full
    error message without your attempts at obfuscation?

    Jochem


    --
    Jochem van Dieten
    Adobe Community Expert for ColdFusion
    B
    bjnolleyAuthor
    New Participant
    September 19, 2008
    You said:
    > Sep 18 17:22:11 mail postfix/smtpd[55543]: NOQUEUE: reject: RCPT from
    > domain-name.com[209.50.251.106]: 504 5.5.2 <server-name>: Helo command
    > rejected: need fully-qualified hostname; from=<email-address@rvnetworking.com>
    > to=<email-address@rvnetworking.com> proto=ESMTP helo=<server-name>

    "What have you filled out in CF as the mail server? What is the full error message without your attempts at obfuscation?"

    I certainly didn't want to publish my email address ... I'm sure you don't like spam either. ;)

    At any rate, that IS the FULL error, with the following substitutions:
    - Where it says "server-name" the actual error says our server's Windows machine name, bjserver.
    - Where it says "domain-name" the actual error says our server's hostname and domain, bj-consulting.com.
    - Where it says "email-address" the actual error says my email name "bjnolley". rvnetworking.com is the true domain for my email address.

    The Windows computer name properties include the domain, bj-consulting.com.

    Cold Fusion specifies mail.servint.com, our web server host's mail server, which we use. This mail server is receiving the CF generated email, but rejects it with the above-mentioned error.

    This function worked until the mail server was upgraded to a version that requires the FQDN to be specified in the HELO.

    Do you know how to configure CF to send the FQDN in the HELO?
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices