Community Forums
Connect with us on LinkedIn
+ Reply to Thread
Page 2 of 2 FirstFirst 1 2
Results 16 to 22 of 22
  1. #16
    Registered User
    Join Date
    Nov 2010
    Posts
    3

    Default Re: invalid helo after latest update

    Quote Originally Posted by nileshparmar View Post
    i am also facing the same issue.
    Hi can you please read my above message carefully. I was facing this issue in .NET. I hope this will help you.

    Thanks
    Jatin

  2. #17
    Member
    Join Date
    Nov 2007
    Posts
    865

    Default Re: invalid helo after latest update

    Quote Originally Posted by jatinshah1 View Post
    Hi can you please read my above message carefully. I was facing this issue in .NET. I hope this will help you.

    Thanks
    Jatin
    Yeah I already read your thread & i am facing the same problem as per thread invalid helo after latest update

  3. #18
    Member
    Join Date
    Nov 2007
    Posts
    865

    Default Re: invalid helo after latest update

    I am waiting for the FIX

  4. #19
    Member
    Join Date
    Jul 2006
    Posts
    90

    Default Re: invalid helo after latest update

    Quote Originally Posted by nileshparmar View Post
    I am waiting for the FIX
    Did you tried sending mails WITH authentication, as normally should?

  5. #20
    Member
    Join Date
    Nov 2007
    Posts
    865

    Default Re: invalid helo after latest update

    Quote Originally Posted by lehels View Post
    Did you tried sending mails WITH authentication, as normally should?
    First of all i am not a sender, Sender is our client (example.com & they are using google apps mail server) &
    i am a recipient (testdomain.com & use Exim mail server )

    when 123@example.com sends mail to 123@testdomain.com it doesn't delivered
    It means our recipient server (testdomain.com & use Exim mail server ) is blocking email

    I found error below while checking exim logs

    2011-01-03 15:14:08 H=(EXPDSI01) [209.143.xx.xx] rejected MAIL <123@exp-inc.com>: Access denied - Invalid HELO name (See RFC2821 4.1.1.1)

    But when 123@example.com sends mail to any other email service provider like yahoo, google,hotmail,rediffmail,aol it successfully delivered


    means our Exim email server blocking email with error Access denied - Invalid HELO name (See RFC2821 4.1.1.1)

  6. #21
    Member
    Join Date
    Sep 2004
    Location
    inside a catfish
    Posts
    963
    cPanel/Enkompass Access Level

    Root Administrator

    Default Re: invalid helo after latest update

    Quote Originally Posted by nileshparmar View Post
    First of all i am not a sender, Sender is our client (example.com & they are using google apps mail server) &
    i am a recipient (testdomain.com & use Exim mail server )

    when 123@example.com sends mail to 123@testdomain.com it doesn't delivered
    It means our recipient server (testdomain.com & use Exim mail server ) is blocking email

    I found error below while checking exim logs

    2011-01-03 15:14:08 H=(EXPDSI01) [209.143.xx.xx] rejected MAIL <123@exp-inc.com>: Access denied - Invalid HELO name (See RFC2821 4.1.1.1)

    But when 123@example.com sends mail to any other email service provider like yahoo, google,hotmail,rediffmail,aol it successfully delivered


    means our Exim email server blocking email with error Access denied - Invalid HELO name (See RFC2821 4.1.1.1)
    Turn off this option in the Exim Configuration Editor:

    Require incoming SMTP connections to send HELO conforming to internet standards (RFC2821 4.1.1.1)

    I believe that with this option on, the server is expecting the client to send a FQDN (xxxx.yyyyyyy.zzz or yyyyyyy.zzz) OR an IP address [ex: 1.1.1.1] but the client is sending only xxxx.

    Having this option enabled is going to block some more spam, but it is also going to break legitimate mail delivery in some cases -- as you have seen.

    Mike

  7. #22
    Member
    Join Date
    Nov 2007
    Posts
    865

    Default Re: invalid helo after latest update

    Quote Originally Posted by mtindor View Post
    Turn off this option in the Exim Configuration Editor:

    Require incoming SMTP connections to send HELO conforming to internet standards (RFC2821 4.1.1.1)

    I believe that with this option on, the server is expecting the client to send a FQDN (xxxx.yyyyyyy.zzz or yyyyyyy.zzz) OR an IP address [ex: 1.1.1.1] but the client is sending only xxxx.

    Having this option enabled is going to block some more spam, but it is also going to break legitimate mail delivery in some cases -- as you have seen.

    Mike
    Oh Yeah,

    Problem has been solved

Similar Threads & Tags
Similar threads

  1. Install/Update a SSL Host: Invalid IP specified
    By FreedomBI in forum cPanel and WHM Discussions
    Replies: 2
    Last Post: 11-20-2009, 05:51 AM
  2. Invalid HELO name
    By BigPete in forum E-mail Discussions
    Replies: 0
    Last Post: 03-06-2009, 10:56 AM
  3. HELO/EHLO domain is invalid....!!??
    By x-man in forum E-mail Discussions
    Replies: 2
    Last Post: 02-19-2009, 04:03 PM
  4. /etc/mailhelo problem with invalid HELO argument
    By deanstev in forum E-mail Discussions
    Replies: 7
    Last Post: 06-05-2008, 06:18 PM
Linkedin       Facebook       Twitter       RSS       Flickr       YouTube