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.

Problem with delivery error messages

Discussion in 'General Discussion' started by AlexVB, Dec 1, 2007.

  1. AlexVB

    AlexVB Member

    Joined:
    Oct 23, 2007
    Messages:
    13
    Likes Received:
    1
    Trophy Points:
    1
    Hi.

    One of our customers was setup "default address" forwarding of all his mail to the mailbox on other mail server. This user's domain receives a lot of spam messages, that are forwarded to the pointed out address. The destination mail server is rejecting lot of messages that makes exim to send deliverty error to the "sender" of the message, this error messages of cource cannot be delivered because sender that in the "from" header does not exist. Because of that - mail queue is filled out with undelivered "delivery error" messages.

    It is possible make exim not to send deliverty status notifications to the sender of the message?
     
  2. mtindor

    mtindor Well-Known Member

    Joined:
    Sep 14, 2004
    Messages:
    1,279
    Likes Received:
    36
    Trophy Points:
    48
    Location:
    inside a catfish
    cPanel Access Level:
    Root Administrator
    Better to do the following:
    1. enable sender verify in WHM / Exim Configuration Editor
    2. set up a single POP3 account for your customer's domain
    3. set up his domain default address to dump to his POP3 account
    4. set up a forwarder with the same name as the POP3 account you created
    - set that forwarder to forward to his mailbox on another server
    5. Set up spamassassin on this user's domain and tell it to delete anything it thinks is spam with a score of '5' or greater (the default) - or set it to whatever you prefer.


    With sender verification enabled on _your_ server, _your_ server should reject the emails that were previously being delivered to the other server and being refused by that server when it performed its sender verification.

    With the POP3 account set up, with spamassassin enabled and deleting likely spam, with the default address forwarding to that POP3 account and a forwarder set up to forward that same users mail to the mailbox on the other server, your server should filter out the majority of the spam before it is forwarded it on to the 'other' server.

    If you/your customer are unwilling/unable to do this, then you should prohibit your customers from forwarding their email to other servers. Most mail servers these days react negatively to automatically forwarded mail, especially if that mail has not been 'spam cleaned' before it was forwarded.

    scenario:
    domain: blah.com
    pop3 account: blah@blah.com
    forwarder blah@blah.com added which forwards to blah@otherdomain.com
    default address: set to forward mail to blah@blah.com
    spamassassin enabled on blah.com (set to auto delete mail above certain spam score)

    NOTE: If you do it this way, the local POP3 account blah@blah.com will fill up with the same emails as it forwards to blah@otherdomain.com. But if you want this customer's mail to be run through spamassassin before it is forwarded to blah@otherdomain.com, this is how you need to set it up.

    Mike
     
  3. AlexVB

    AlexVB Member

    Joined:
    Oct 23, 2007
    Messages:
    13
    Likes Received:
    1
    Trophy Points:
    1
    Thank you for your reply, it was helpful.
     
Loading...

Share This Page