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.

Mail not delivered and not sent

Discussion in 'E-mail Discussions' started by Fryday, Sep 29, 2011.

  1. Fryday

    Fryday Registered

    Joined:
    Sep 29, 2011
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Hello,

    Can't figure out the issue of sending and receiving emails on newly set up server.
    Emails that are sent out, all go to "mail Queue". If I "try to deliver now", getting the following error:
    Why is the "MAIN Spool file" locked and what is the process, that is called "another" and "handling"?

    Do I need to look beyond just server set up perhaps,... even into DNS records?
    This is virtual server, KVM based.

    P.S.
    - this command posted elsewhere
    /scripts/courierup --force
    /scripts/eximup --force
    Does not help

    - Restarting Mail Server (Exim) does not help
     
    #1 Fryday, Sep 29, 2011
    Last edited: Sep 29, 2011
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,678
    Likes Received:
    654
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    That typically means Exim is already attempting to deliver that message. Messages will only remain in the mail queue if delivery fails. You can check the Exim logs to determine why the message failed to deliver with a command such as:

    Code:
    # /usr/sbin/exigrep [email]user@domain.com[/email] /var/log/exim_mainlog
    Simply replace "user@domain.com" with the email address used in an email that failed to deliver.

    Thank you.
     
  3. Fryday

    Fryday Registered

    Joined:
    Sep 29, 2011
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Thank you,
    This issue is solved. It actually related to some special setup with the datacenter, that we didn't know about.
     
Loading...

Share This Page