CiviCRM Community Forums (archive)

I am on a VPS now, but would prefer to use imap2soap since I'm not a true sysadmin and I am trying to reduce the number of really complicated things I will have to support.  That said, I think my problem is not specific to imap2soap, which is why I am posting it here.  I can't seem to get emails to actually get to the civimail account to be processed by any script, be it Amavis or imap2soap.

I am able to send out civimailings.  I do not get any errors when the imap2soap cron job runs.  My problem now is that when I test the return functions by clicking on an unsubscribe link in a civimail, the unsubscribe request bounces because the email was rejected by my mail server. AN Example:

This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

    unsubscribe.1.56.748.8af0d9d231427f5229fe40010310fa217feadbf3@mydomain.com

Technical details of permanent failure:
PERM_FAILURE: Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 553 553 sorry, relaying denied from your location [64.233.166.178] (#5.7.1) (state 14).

My mail server is Exim, and I have a WHM/cPanel account.  I tried changing the catch-all behavior to blackhole and restarting Exim, but no luck.  In cPanel, I went into Account Level Filtering and set up a filter like this:

Rule
To: matches the following regex:
/^(bounce|confirm|optOut|reply|subscribe|unsubscribe|resubscribe)\..*@mydomain\.comAction
redirect to email: civimail@mydomain.com

Its a GUI filter tool, so I don't know what the actual code is that is generated.

I do have an email account set up for that civimail@mydomain.com account.  Those are all the steps I've taken so far.  I'm sure there is a simple one somewhere in there but I am not too experienced with email admin stuff.  Any help would be appreciated.

Actually, the 553 error was related to the MX record not being set correctly.  That is fixed.

I also found that Exim apparently doesn't support a filter in this way as a replacement for a catch-all.  After talking with my NOC I ended up just using the catch-all email going to the civimail account, and turned on all the RBL's I could.  I'm hoping I won't have too much trouble trying to manage mailbox size issues with spam.

At least I now have CiviMail totally working correctly now.