Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Email Registrations trapped in Spam | Event Espresso - Staging Server
Hi,
I’m using EE 3, just installed yesterday and finding my way around – but I may have found a deal-breaker. While testing sample orders to multiple email addresses (not just one) the majority of the confirmations are being trapped by the spam filter. I can’t sell tickets to my event if people can’t receive their tickets!
I tried the solution mentioned here but that has not corrected the problem.
Any help is gratefully appreciated.
Postmark offers 10,000 email ‘credits’ then you must purchase more.
Mandrill offers up to 12,000 per month free.
Personally I use Mandrill, one thing I would like to note if using Mandrill (or even Postmark for that matter) is that we are starting to phase out the ee-transactional-plugin in favour of wpMandrill.
The ee-transactional-plugin does almost the same as wpMandrill only it was created to fill a need when there was no other alternative, wpMandrill has now been released which is actively updated/supported and as such I would recommend using that over ours.
Same, I tried the wpmandrill tonight and it work really well to fix all these spam issues I had. Thanks :-)
Viewing 5 reply threads
The support post ‘Email Registrations trapped in Spam’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.