Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bludit v3.5: SMTP does not work #3

Closed
clickwork-git opened this issue Dec 24, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@clickwork-git
Copy link

commented Dec 24, 2018

SMTP does not work for me.

@novafacile

This comment has been minimized.

Copy link
Owner

commented Jan 27, 2019

In our configuration it's working.
Can you please add some more error information?

@clickwork-git

This comment has been minimized.

Copy link
Author

commented Jan 29, 2019

The problem could be caused by the e-mail settings of the hoster. I will try again.

@ltGuillaume

This comment has been minimized.

Copy link
Contributor

commented Feb 4, 2019

This could be caused by someone else on the webhosting server (e.g. by being naughty and sending spam messages), but it can also be caused by the email message format as set up by this plugin, so I thought I'd ask for help in order to confirm or falsify: I can't use this plugin at all (on two servers) to send to @gmail.com addresses.

The feedback is that the message has been sent successfully, but no message will be received (it's not even in spam, or anywhere else). It is entirely possible that Gmail handles suspicious (spam) servers, or messages in a suspicious format, by simply acting like it accepts the email and then throwing it away immediately.

The only reliable way around this is to create an "intermediate" email address on the same server and send the filled in contact forms there, and afterwards importing the messages on that address's POP/IMAP server into the actual destination Gmail mailbox.

@novafacile

This comment has been minimized.

Copy link
Owner

commented Feb 15, 2019

I close the issue. Last problem is fixed in #9

@novafacile novafacile closed this Feb 15, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.