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 receipt problem - local delivery failed

Discussion in 'E-mail Discussions' started by quortex, Mar 15, 2005.

  1. quortex

    quortex Member

    Joined:
    Mar 15, 2005
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    Hi,

    I have a domain used for email that runs cPanel that was working absolutely fine using exim. For some reason now any address emailed to bounces with the error:

    "local delivery failed"

    I have checked the mx record and exim restarts without errors. All other email accounts on other domains running on the same server work fine.

    Any ideas how to fix this?

    Kind Regards,
    Mark
     
  2. laura

    laura Active Member

    Joined:
    Sep 12, 2003
    Messages:
    35
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    indonesia
    421 Lost incoming connection

    me too!, just happen in few domains only...412 Lost incoming connection?

    help me!

    error message :
    >This message was created automatically by mail delivery software.
    >
    >A message that you sent could not be delivered to one or more of its
    >recipients. This is a permanent error. The following address(es) failed:
    >
    > name@domain.com
    > local delivery failed
    >
    >The following text was generated during the delivery attempt:
    >
    >------ name@domain.com ------
    >
    >An error was detected while processing a file of BSMTP input.
    >The error message was:
    >
    > 421 Lost incoming connection
    >
    >The SMTP transaction started in line 0.
    >The error was detected in line 3.
    >0 previous messages were successfully processed.
    >The rest of the batch was abandoned.
    >421 Lost incoming connection
    >Transaction started in line 0
    >Error detected in line 3
     
  3. Stream

    Stream Well-Known Member

    Joined:
    Feb 7, 2004
    Messages:
    64
    Likes Received:
    0
    Trophy Points:
    6
    This has been discussed earlier. Seems it's a problem with SpamAssassin on certain installations. Try disabling it.
    There is also a patch for SpamAssassin, but it says it's for v3.0.0, not v3.0.2 so I never tried it myself.
     
Loading...

Share This Page