|
dougintexas
|
May 3, 2018 at 11:00 pm
This is the topic to support the token.
|
|
Josh
|
May 4, 2018 at 6:43 am
Hi Doug,
We’ve received your request for priority support and this reply is to let you know we’re troubleshooting your site at the moment.
|
|
Josh
|
May 4, 2018 at 7:37 am
I turned on your SMTP plugin’s debug mode and this is the error:
SMTP ERROR: DATA END command failed: 550 This message was classified as SPAM and may not be delivered
SMTP Error: data not accepted.CLIENT -> SERVER: QUIT
So it appears that some messages are triggering the mail server’s outbound spam screening.
|
|
Josh
|
May 4, 2018 at 7:54 am
So you could check with your host to see if they have logs that can shed some light on what specifically is triggering the SMTP error. Or you could use a transactional email service like one of the options listed here:
https://eventespresso.com/wiki/postmark-app-mandrill-transactional-email-handling-services/
|
|
Josh
|
May 4, 2018 at 8:21 am
In the meantime, you can remove this shortcode from your email templates:
[GOOGLE_MAP_IMAGE]
and try replacing with
[GOOGLE_MAP_LINK]
I found that the email will send without failure on your site when the static Google map isn’t included in the email.
|
|
dougintexas
|
May 4, 2018 at 1:48 pm
Josh, they have checked everything and they are saying that there is something amiss in EE. I really need this resolved as soon as possible. I am assuming that a paid token accelerates this.
|
|
Josh
|
May 4, 2018 at 1:58 pm
Doug,
Did you read my last reply? You’ll need to remove the [GOOGLE_MAP_IMAGE] shortcodes from your email message templates.
There’s nothing amiss with Event Espresso here. The emails are getting flagged as spam due to the Google map image code. Remove the code and they’ll send.
|
|
dougintexas
|
May 4, 2018 at 2:00 pm
Yes, I read it and changed it. But that did not fix it. I’m having inMotionHosting take a deeper look as we speak.
The problem is not consistent. It works for one addressee and fails for another. There is some setting related to outgoing spam on the server that is throwing this.
|
|
dougintexas
|
May 4, 2018 at 2:01 pm
I have them on the call with me right now. They are looking at the settings related to the outgoing email account.
|
|
Josh
|
May 4, 2018 at 2:06 pm
May I ask how did you verify this? If you view the failed messages in the queue, do any of them not include a Google Map?
I’d check, but it appears that the password you sent earlier is no longer valid.
|
|
dougintexas
|
May 4, 2018 at 2:10 pm
I verified the short-code change by doing it myself. Now, there’s no map at all (not ideal but not necessarily a problem). In spite of that change, the outgoing mails for some customers were still failing. I just got off the phone with inMotion and they said they have Span Assassin as a gate-keeper on outgoing email. Turns out that THAT is the issue! They turned it off and everything goes out as it should.
Since this is resolved, did we consume the support token?
|
|
Josh
|
May 4, 2018 at 2:26 pm
Yes token is consumed because Event Espresso support staff spent over 30 minutes investigating your site this morning. I reported the results of the investigation here:
https://eventespresso.com/topic/confirmation-emails-fail/#post-268718
|
