The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Email mail delivery error

Discussion in 'E-mail Discussions' started by Secret Agent, Jun 30, 2005.

  1. Secret Agent

    Secret Agent Guest

    This report relates to a message you sent with the following header fields:

    Message-id: <0IIW001FJZY3ZQ10@mta2.srv.hcvlny.cv.net>
    Date: Thu, 30 Jun 2005 16:37:20 -0400
    From: My Site <support@mydomain.com>
    To: customer@aol.com
    Subject: RE: Billing

    Your message cannot be delivered to the following recipients:

    Recipient address: customer@aol.com
    Reason: SMTP transmission failure has occurred
    Diagnostic code: smtp;554-: (HVU:NR) http://postmaster.info.aol.com/errors/554hvunr.html TRANSACTION FAILED
    Remote system: dns;mailin-02.mx.aol.com (TCP|167.206.4.197|48486|64.12.138.89|25) (rly-xl02.mx.aol.com ESMTP mail_relay_in-xl2.2; Thu, 30 Jun 2005 16:37:27 -0400)


    What would cause this? I got that from Modernbill outgoing and even manually sent via Outlook. Any ideas?


    AOL says this:

    554 HVU:NR
    http://postmaster.info.aol.com/errors/554hvunr.html
    EXPLANATION:

    A URL listed in your e-mail is improperly formatted. AOL requires that all URLs in an e-mail comply with the internet guidelines pertaining to URL and domain name formatting.

    SOLUTION:

    Please check the syntax of all URLs contained within your e-mail. Verifying your complete e-mail is compliant with current internet standards and guidelines.


    There is nothing wrong with the "broken url" or such and is in simle pain html formatting.
     
  2. webignition

    webignition Well-Known Member

    Joined:
    Jan 22, 2005
    Messages:
    1,880
    Likes Received:
    0
    Trophy Points:
    36
    What is the URL in question?
     
  3. Secret Agent

    Secret Agent Guest

    I don't want to post the email / url for privacy reasons

    However I can say this only happens with AOL, occasionally.
     
  4. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    Nothing much you can do about it. AOL pretty much arbitrarily don't accept email for delivery. The only things that you can do are:

    1. Make sure you or your users are not forwarding email from your server to AOL, especially if the email hasn't been cleaned of any viruses and all spam first

    2. Make sure that you have an rDNS PTR record for your main IP address

    That's it.
     
  5. Secret Agent

    Secret Agent Guest

    This is strange. Another problem but with Yahoo now

    sent test mail from Yahoo.

    The server responded as follows:

    <rivey1@remotedomain.net>:
    xxx.9.166.50 does not like recipient.
    Remote host said: 550-"The recipient cannot be verified. Please check all recipients of this 550 message to verify they are valid."
    Giving up on xxx.9.166.50.


    My specs:

    Exim 4.51x
    Cpanel 10.x (latest current)
    Exim ACL Dictionary Attack Script
    mod-security

    Tweak Settings:
    prevent user nobody from sending... .OFF
    track origin of mesages.... OFF
    Include a list of Pop before SMTP senders in the X-Pop... ON
    blackhole.... ON
    mailman.... ON
    Silently Discard all FormMail-clone requests.... ON

    EXIM config:

    OFF = Always set the Sender: header when the sender is changed from the actual sender. (Unchecking this will stop "On behalf of" data in Microsoft(R) Outlook, but may limit your ability to track abuse of the mail system.)

    ON = Verify the existance of email senders

    ON = Discard emails for users who have exceeded their quota instead of keeping them in the queue.

    Avanced mode in EXIM config:

    first box

    timeout_frozen_after = 2d
    ignore_bounce_errors_after = 12h

    domainlist rbl_blacklist = lsearch;/etc/rblblacklist
    domainlist rbl_bypass = lsearch;/etc/rblbypass
    hostlist rbl_whitelist = lsearch;/etc/relayhosts : partial-lsearch;/etc/rblwhitelist
    message_size_limit = 5M
    log_selector = +arguments +subject

    timeout_frozen_after = 2d
    ignore_bounce_errors_after = 12h

    Second Box:

    #!!# ACL that is used after the RCPT command
    check_recipient:
    # Exim 3 had no checking on -bs messages, so for compatibility
    # we accept if the source is local SMTP (i.e. not over TCP/IP).
    # We do this by testing for an empty sending host field.
    accept hosts = :

    drop hosts = /etc/exim_deny
    message = Connection denied after dictionary attack
    log_message = Connection denied from $sender_host_address after dictionary attack


    drop message = Appears to be a dictionary attack
    log_message = Dictionary attack (after $rcpt_fail_count failures)
    condition = ${if > {${eval:$rcpt_fail_count}}{3}{yes}{no}}
    condition = ${run{/etc/exim_deny.pl $sender_host_address }{yes}{no}}
    !verify = recipient

    # Accept bounces to lists even if callbacks or other checks would fail
    warn message = X-WhitelistedRCPT-nohdrfromcallback: Yes
    condition = \
    ${if and {{match{$local_part}{(.*)-bounces\+.*}} \
    {exists {/usr/local/cpanel/3rdparty/mailman/lists/${lc:$1}/config.pck}}} \
    {yes}{no}}

    accept condition = \
    ${if and {{match{$local_part}{(.*)-bounces\+.*}} \
    {exists {/usr/local/cpanel/3rdparty/mailman/lists/${lc:$1}/config.pck}}} \
    {yes}{no}}


    # Accept bounces to lists even if callbacks or other checks would fail
    warn message = X-WhitelistedRCPT-nohdrfromcallback: Yes
    condition = \
    ${if and {{match{$local_part}{(.*)-bounces\+.*}} \
    {exists {/usr/local/cpanel/3rdparty/mailman/lists/${lc:$1}_${lc:$domain}/config.pck}}} \
    {yes}{no}}

    accept condition = \
    ${if and {{match{$local_part}{(.*)-bounces\+.*}} \
    {exists {/usr/local/cpanel/3rdparty/mailman/lists/${lc:$1}_${lc:$domain}/config.pck}}} \
    {yes}{no}}

    #if it gets here it isn't mailman

    #sender verifications are required for all messages that are not sent to lists

    require verify = sender
    accept domains = +local_domains
    endpass

    #recipient verifications are required for all messages that are not sent to the local machine
    #this was done at multiple users requests

    message = "The recipient cannot be verified. Please check all recipients of this message to verify they are valid."
    verify = recipient

    accept domains = +relay_domains

    warn message = ${perl{popbeforesmtpwarn}{$sender_host_name}}
    hosts = +relay_hosts
    accept hosts = +relay_hosts

    warn message = ${perl{popbeforesmtpwarn}{$sender_host_address}}
    condition = ${perl{checkrelayhost}{$sender_host_address}}
    accept condition = ${perl{checkrelayhost}{$sender_host_address}}

    accept hosts = +auth_relay_hosts
    endpass
    message = $sender_fullhost is currently not permitted to \
    relay through this server. Perhaps you \
    have not logged into the pop/imap server in the \
    last 30 minutes or do not have SMTP Authentication turned on in your email client.
    authenticated = *

    deny message = $sender_fullhost is currently not permitted to \
    relay through this server. Perhaps you \
    have not logged into the pop/imap server in the \
    last 30 minutes or do not have SMTP Authentication turned on in your email client.


    #!!# ACL that is used after the DATA command
    check_message:
    require verify = header_sender
    accept



    Any suggestions?
     
  6. Secret Agent

    Secret Agent Guest

    Another example:

    Message-id:
    <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAQkAGC+svMEO/skbcf04vC8KAAAAQAAAA0qwb+XrKN0mUkvdqbJEQpwEAAAAA@hostdomain.com>
    Date: Fri, 08 Jul 2005 16:46:27 -0400
    From: Support <support@hostdomain.com>
    To: rivey1@accountdomain.net
    Subject: Test

    Your message cannot be delivered to the following recipients:

    Recipient address: rivey1@accountdomain.net
    Reason: Remote SMTP server has rejected address
    Diagnostic code: smtp;550-"The recipient cannot be verified. Please check all recipients of this message to verify they are valid."
    Remote system: dns;sub.accountdomain.net (TCP|167.206.4.205|55389|xxx.9.166.50|25) (server.hostdomain.com ESMTP Exim 4.50 #1 Fri, 08 Jul 2005 16:46:40 -0400 )
     
  7. Murtaza_t

    Murtaza_t Well-Known Member

    Joined:
    Jan 24, 2005
    Messages:
    476
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Earth
    cPanel Access Level:
    Website Owner
  8. carlosferns2004

    carlosferns2004 Active Member

    Joined:
    May 5, 2005
    Messages:
    41
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    india
    Hi

    DO a REVERSE DNS ENTRY AND UR PROBLEM WILL BE SOLVED








    CHEERS

    Regards
    Carlos Fernandes
     
  9. Secret Agent

    Secret Agent Guest

    No, reverse dns is not the problem. Had this server for 1 1/2yrs w/o rdns and worked fine until now.

    Any one, please help me out :)
     
  10. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    If you don't have an rDNS PTR record for your servers main IP address you will have mail delivery problems to a great deal of MTA's, in particular the likes of AOL and most sendmail based servers where the checking of the rDNS is commonplace.
     
  11. Secret Agent

    Secret Agent Guest

    Ok let me clarify. The first post, ignore it. Please look at only the posts after. The first was something else, I only added to the thread becaues I thought it was similiar but it is not.

    The two above are accounts that have been with me for several months without rDNS and suddenly stopped working
     
Loading...

Share This Page