XF 2.3 Bounces email mailbox

[ichpen]

Quickie question for you.

Does the bounces email mailbox (for automated bounce handling) have to be on the same domain as sender domain?

Appreciate it.

 

[Alpha1]

No, thats not needed. But it may not be a free email provider like gmail, hotmail. I used mxroute inbox with a domain I own, which worked well. I did switch to Amazon SNS API which works better. The benefit of API is that its instant and you never have the problem of inbox retrieval issues. I use Dragonbyte tech MAIL addon for SNS API.

 

[ichpen]

No, thats not needed. But it may not be a free email provider like gmail, hotmail. I used mxroute inbox with a domain I own, which worked well. I did switch to Amazon SNS API which works better. The benefit of API is that its instant and you never have the problem of inbox retrieval issues. I use Dragonbyte tech MAIL addon for SNS API.

Thanks and good reminder. I'm using Julan's old SES email handler and had it all setup long ago.

Should I disable the XF bounces handling in that case I wonder?

 

[Alpha1]

Thats really hard to answer because its unmaintained and SES, bounces and XenForo change. Just check the bugs and suggestions i filed here:

bounce handling

xenforo.com

Latest XenForo version fixes an important issue in the bounce handler. The SNS handler needs to be updated accordingly.

XenForo does not handle SES complaints. It seems julians addon also does not. IMHO this is critical.
@DragonByte Tech Mail does and is regularly pushing updates .

I think one of the most important things is to make sure that the solution you choose will keep working. If it stops working correctly without you noticing it, it can be a massive headache to resolve .

If you opt for both SNS and XenForo bounce processing then consider that this will duplicate the soft bounce count.

Id consider an actively maintained SES addon.

 

[ichpen]

Thats really hard to answer because its unmaintained and SES, bounces and XenForo change. Just check the bugs and suggestions i filed here:

bounce handling

xenforo.com

Latest XenForo version fixes an important issue in the bounce handler. The SNS handler needs to be updated accordingly.

XenForo does not handle SES complaints. It seems julians addon also does not. IMHO this is critical.
@DragonByte Tech Mail does and is regularly pushing updates .

I think one of the most important things is to make sure that the solution you choose will keep working. If it stops working correctly without you noticing it, it can be a massive headache to resolve .

If you opt for both SNS and XenForo bounce processing then consider that this will duplicate the soft bounce count.

Id consider an actively maintained SES addon.

Yep all valid points. I'll need to transition off it. I was curious if both bounce handling and sns/ses handlers were required as they should essentially do the same thing ultimately.

 

[Alpha1]

If you move to DBT Mail and setup SES on it, then disable mailbox bounce handing. Let the API handle it.

 

[Mouth]

But it may not be a free email provider like gmail

Still working acceptably for me ... (but all your mail handling bugs/suggestions are very much welcome and long overdue)

 

[Alpha1]

The issue with free email providers is that the use is against their policy and they can deactivate the mailbox at any time. If you keep an eye on it then you will be fine. If it catches you by surprise and you find out months later then not so much. True story lol.

 

[Mouth]

The issue with free email providers is that the use is against their policy and they can deactivate the mailbox at any time.

Gmail? Where's this in their policy/guides?

 

[Alpha1]

I'm not sure. If I recall correctly I received an email from Google last year stating it was no longer allowed to use free mail for transactional email or bulk mail.
I previously use a yahoo account for bounced mail. This account was locked without notification. There was no error in XF. Just no bounces coming in. I then looked into gmail as a replacement and found out this was also a no go. I think switched to MXroute which worked well. I now use AWS SNS API and no longer need MXRoute.