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.

Need ideas on 451 temp local problem mail error

Discussion in 'E-mail Discussions' started by domainorders, Aug 28, 2004.

  1. domainorders

    domainorders Registered

    Joined:
    Aug 28, 2004
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    I'm having a mail related problem with one of my domains. I have limited access to the server and I'm having difficulty communicating with the host on this problem. Perhaps if I had some ideas on what to check I could get them to do it.

    The story -- Linux Apache cPanel. call the domain aaaaa.com. The main user name for this domain, i.e., the Main Account under Mail Account Maintenance, is aaaaa. Things worked fine before the server crashed a month ago and they did a restore onto a backup server. The problem is that any mail to the aaaaa mailbox is bounced and the error is host aaaaa.com[ip address] said: 451 Temporary local problem - please try later (in reply to RCPT TO command).

    I have sent mail from my normal ISP as well as 2 different web based accounts I have. None of the mail goes through, sometimes I get the above error msg, sometimes I get nothing back.

    Initially the aaaaa mailbox was the default mailbox so I wasn't getting any mail; I did not have any extra users/mailboxes or forwarders set up. I set up another user on the domain, call it bbbbb. Mail to bbbbb@aaaaa.com goes through fine. I made bbbbb the default mailbox and now I am getting mail, it comes through the bbbbb mailbox. But if I send mail to aaaaa@aaaaa.com I still get the 451 error.

    If I create a mail forwarder in cPanel so that aaaaa@aaaaa.com is forwarded to bbbbb@aaaaa.com then mail to aaaaa@aaaaa.com goes through and is received at bbbbb@aaaaa.com. If I remove the forwarder then I am back where I started where mail to aaaaa@aaaaa.com does not go through.

    On dnsstuff.com there's an email test tool. If I enter address aaaaa@aaaaa.com then it says aaaaa.com - [Could not connect: Got an unknown RCPT TO response: 451 Temporary local problem - please try later
    ] If I enter address bbbbb@aaaaa.com then it says aaaaa.com. - [Successful connect: Got a good response [250 Accepted]]

    The problem seems to be related to the mailbox named aaaaa. Since this is the Main Account mailbox, I cannot remove or change it. At least, if I can remove or change it, I do not know how. I have asked my host if I can remove or change it from cPanel and they did not answer.

    Early on my host suggested it was a problem with my ISP. I don't see how since mail I sent from 3 sources yields the same results. Plus consider the results from dnsstuff.com. Plus consider that if I create the forwarder for aaaaa@aaaaa.com then it goes through.

    I've seen a number of posts on 451 errors referring to something to do with DNS lookups on the sender. I don't think that's the issue either since mail to bbbbb@aaaaa.com goes through, as well as mail going through with the forwarder created.

    I found a couple of posts suggesting that the domain aaaaa.com is missing from /etc/localaliases. I don't have access to this file to check. But, if the entry is missing, would mail to bbbbb@aaaaa.com still go through? Seems to me that it would not, but I do not know.

    I have seen posts on 451 errors mentioning problems with MX records. Again, I do not see how since mail to bbbbb@aaaaa.com goes through, as well as it going through with the forwarder in place. But if someone can tell me otherwise, then please explain.

    I don't know of anything to check in my cPanel or files that could be causing this, unless it's some type of missing file, directory, or bad permissions that I don't know about. Everything looks in place, but I confess that I might not know what to look for. As I said, the only thing I can look at is what my cPanel allows me to look at, plus what I can look at with ftp, but that basically amounts to the same thing as far as the files and folders are concerned.

    I hope my description of the symptoms makes sense. Does anyone have any ideas as to what could be causing this error with these symptoms? Am I maybe missing a file/directory/permission related to the aaaaa mailbox that I might be able to check and correct myself? Or is it likely some config file or permission on the server somewhere that I have to get the host to check, and if so, an idea of what or where to look would help as I could try to get them to check it.

    Thanks for any help.
     
  2. domainorders

    domainorders Registered

    Joined:
    Aug 28, 2004
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    What? All that brain power out there and nobody has any ideas on this? Maybe that's why I can't get the host to fix it, nobody knows what might be causing this problem. I hate to just punt, but it looks like I might have to.
     
  3. sawbuck

    sawbuck Well-Known Member

    Joined:
    Jan 18, 2004
    Messages:
    1,367
    Likes Received:
    5
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Post some domain info so we can check your DNS.
     
  4. domainorders

    domainorders Registered

    Joined:
    Aug 28, 2004
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Please explain why DNS might be an issue if mail to bbbbb@aaaaa.com goes through as well as if I create a forwarder for aaaaa@aaaaa.com to go to bbbbb@aaaaa.com then it goes through as well? If there were a DNS problem then these would have problems as well.

    Also, I just got some new info -- the hosted domain that is having the problem is actually a domain/account I set up in a reseller account that I have on the server.

    The hosting provider set up my reseller account with a main domain and it appears that the main account mailbox for that domain has the same 451 error problem.

    Also, I created an entirely new site in my account. Using the email test in dnsstuff.com I used the new main account name at serverx.hostname.com and it gives the same 451 error. I set up the same account on another cpanel server and the dnsstuff.com email test works. Note that by using the server and host name for the email address I don't have to wait for any DNS propogations for the new domain to take place. The serverx.hostname.com address is a synonym for the actual email address using the domain name.

    So it appears that any new account I set up in my reseller account will have this same 451 error with its default main account mailbox.

    Does this give any clues as to the problem? I think this test eliminates anything to do with DNS.
     
  5. areha

    areha Well-Known Member

    Joined:
    Oct 30, 2002
    Messages:
    52
    Likes Received:
    0
    Trophy Points:
    6
    Hi

    I have had the same error message 451. I belive the error can come of many reasons, but mine was wrong path to clamd emailscanner.

    Before this, I reinstalled exim, checked dns, fixperms, fixndc etc. When I checked the /var/log/exim_paniclog:
    2004-09-11 13:02:57 1A65ej-23444-Bp malware acl condition: clamd: unable to connect to UNIX socket /var/run/clamav/clamd (Connection refused)

    In the exim_configuration editor in WHM, I removed:
    av_scanner = clamd:/var/run/clamav/clamd

    When I removed this line, everything worked again.
     
  6. Insyder

    Insyder Member

    Joined:
    Jun 29, 2003
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    Does seem to be a problem with clamav
     
  7. Lestat

    Lestat Well-Known Member

    Joined:
    Sep 13, 2003
    Messages:
    199
    Likes Received:
    0
    Trophy Points:
    16
    In the exim_configuration editor in WHM, I removed:
    av_scanner = clamd:/var/run/clamav/clamd

    I just changed mine to:
    av_scanner = clamd:/var/clamd

    being that is where I found the clamd file. the other directory was no existant. This has resolved 451 temporary issue... all is working great now! thanks for the tid bit....!!!
     
  8. Gilfil

    Gilfil Member

    Joined:
    Sep 5, 2003
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    Thnx Lestat

    Almost the same thing here, mine was:
    av_scanner = clamd:/tmp/clamd


    Changed to:
    av_scanner = clamd:/var/clamd

    As you did and it worked just great :)
     
  9. Lestat

    Lestat Well-Known Member

    Joined:
    Sep 13, 2003
    Messages:
    199
    Likes Received:
    0
    Trophy Points:
    16
    excellent...
     
  10. Biotron2000

    Biotron2000 Active Member

    Joined:
    Jul 20, 2004
    Messages:
    41
    Likes Received:
    0
    Trophy Points:
    6
    Thanks...

    I just installed the ClamAV connector this morning and had the same problem. I think it was because I had ClamAV already installed manually and did not uninstall it first. After uninstalling the old one and changing the path to clamd, everything works.
    Thanks for posting the answer before I needed it! ;)

    Patrick

    P.S. This might make a good Sticky topic!
     
  11. ispro

    ispro Well-Known Member

    Joined:
    Apr 8, 2004
    Messages:
    628
    Likes Received:
    1
    Trophy Points:
    18
    Addition.

    We had the same problem.
    While we had the correct paths for ClamAV (manually installed) clamd actually not running.
    ps ax |grep clamd
    shows that clams not running.

    Reinstalling ClamAV helps.
     
  12. cyon

    cyon Well-Known Member
    PartnerNOC

    Joined:
    Jan 15, 2003
    Messages:
    320
    Likes Received:
    0
    Trophy Points:
    16
  13. chae

    chae Well-Known Member

    Joined:
    Apr 19, 2003
    Messages:
    145
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Auckland, New Zealand
    cPanel just updated to exim 4.44.0 tonight and we started receiving the error messages...after tail logs we found the issue was with one of the ACL's we had for SPAM checking.

    ###### ACL for SURBL

    deny set acl_m1 = ${perl{surblspamcheck}}
    message = Message contains blacklisted domain $acl_m1. See http://www.surbl.org/lists.html. (Rule 21)
    log_message = Message contains blacklisted domain $acl_m1. See http://www.surbl.org/lists.html. R=$recipients (Rule 21)
    condition = ${if eq {$acl_m1}{false} {no}{yes} }

    ##### end of SURBL acl

    After removing the ACL everything went back to normal...the ACL was working 100% before the new Exim upgrade. Will contact the author of the ACL and SURBL and see if they are going to update to accommodate the exim changes.

    Hope that helps anyone who has just noticed the same thing happening today :)
     
  14. jsnape

    jsnape Well-Known Member

    Joined:
    Mar 11, 2002
    Messages:
    174
    Likes Received:
    0
    Trophy Points:
    16
    I had the same thing and it was a forwarder set up to send bob@domain.com --> domain.com (no valid address)

    tail -f /var/log/exim_mainlog

    and send mail to bob and watch the error get displayed in real time.
     
  15. Shadeaux

    Shadeaux Registered

    Joined:
    Nov 19, 2001
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    I tried all of the above, the only thing to fix me was the
    Changed to:
    av_scanner = clamd:/var/clamd
     
  16. SupermanInNY

    SupermanInNY Well-Known Member

    Joined:
    Jul 19, 2003
    Messages:
    255
    Likes Received:
    0
    Trophy Points:
    16
    Kinda old posting, but new problem for me (now resolved after reading this thread).

    I believe I had the clamAV installed previously,. anyway.. I went through the Addon Modules and saw it was NOT installed.
    After installing it.. I experienced the same 451 errors and the log:

    malware acl condition: clamd: unable to connect to UNIX socket /var/run/clamav/clamd (
    Connection refused)

    So,. I changed it to the suggested path and it worked with no problem immediatly.

    Thanks!

    -Alon.
     
Loading...

Share This Page