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.

no mail being forwared

Discussion in 'E-mail Discussions' started by WeMasterz5, Mar 23, 2003.

  1. WeMasterz5

    WeMasterz5 Well-Known Member

    Joined:
    Feb 24, 2003
    Messages:
    361
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Miami
    is this a WHM or cpanel issue, but there is no email being forwared any more, any ideas

    thanks
     
  2. PPNSteve

    PPNSteve Well-Known Member

    Joined:
    Mar 13, 2003
    Messages:
    393
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    Somewhere in Ilex Forest
    cPanel Access Level:
    Root Administrator
    Twitter:
    think the whole mail system in ver6 is broke.. i can't send mail, set up or edit any mail accounts only started up since we upgraded to cP 6
     
  3. WeMasterz5

    WeMasterz5 Well-Known Member

    Joined:
    Feb 24, 2003
    Messages:
    361
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Miami
    I can loin to the clients accounts email system via there cpanel and the neomail etc works from there...but there is no forwarding going out...this was working a week or so ago
     
  4. PPNSteve

    PPNSteve Well-Known Member

    Joined:
    Mar 13, 2003
    Messages:
    393
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    Somewhere in Ilex Forest
    cPanel Access Level:
    Root Administrator
    Twitter:
    hmm
    well my webmail (horde) is working (at the moment) but smtp isn't and i can not edit or add email accounts from users cp
     
  5. WeMasterz5

    WeMasterz5 Well-Known Member

    Joined:
    Feb 24, 2003
    Messages:
    361
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Miami
    I just tried this and got a forward

    If I run "./exim -d9 -bt user@domain" all seems well, but when I send a message from my User Agent, it does not arrive at its destination.
    A0010: Try sending a message directly to Exim by typing this:

    exim -d9 user@domain
    <some message, could be empty>

    If the message gets delivered to a remote host, but never arrives at its final destination, then the problem is at the remote host. If, however, the message gets through correctly, then the problem may be between your User Agent and Exim. Try setting Exim's log_arguments option, to see with which arguments the UA is calling Exim.



    (logged in as root in shell)

    and it sent the email to the domain and forwarded it From: root <root@
     
  6. WeMasterz5

    WeMasterz5 Well-Known Member

    Joined:
    Feb 24, 2003
    Messages:
    361
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Miami
    Exim version 3.36 debug level 1 uid=0 gid=0
    Berkeley DB: Sleepycat Software: DB 2.4.14: (6/2/98)


    anyone know the command to upgrade to the newest version?

    4.10 and 4.11
     
  7. WeMasterz5

    WeMasterz5 Well-Known Member

    Joined:
    Feb 24, 2003
    Messages:
    361
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Miami
    Having installed Exim, you can check that the run time configuration file is syntactically valid by running the command

    exim -bV

    If there are any errors in the configuration file, Exim will output error messages. Otherwise it just outputs the version number and build date. Some simple routing tests can be done by using the address testing option. For example,

    exim -v -bt <local username>

    should verify that it recognizes a local mailbox, and

    exim -v -bt <remote address>

    a remote one. Then try getting it to deliver mail, both locally and remotely. This can be done by passing messages directly to Exim, without going through a user agent. For example:

    exim postmaster@your.domain
    From: user@your.domain
    To: postmaster@your.domain
    Subject: Testing Exim

    This is a test message.
    ^D

    If you encounter problems, look at Exim's log files (mainlog and paniclog) to see if there is any relevant information there. Another source of information is running Exim with debugging turned on, by specifying the -d option. The larger the number after -d (up to 9), the more information is output. With -d2, for example, the sequence of directors or routers that process an address is output. If there's a message stuck on Exim's spool, you can force a delivery with debugging turned on by a command of the form

    exim -d9 -M <message-id>
     
Loading...

Share This Page