creatorsite
Forum Replies Created
-
That’s correct; the messages (sent from S2 member’s registration form) are reaching the web mailbox, but not Gmail, which is the client I’m using. Keep in mind that this is S2 member’s form not the theme’s form, not the host’s form, but S2 member’s form. I’ve checked my spam folder throughout this process and it is not going to spam.
What doesn’t make sense is if I can send messages to all those addresses and Gmail receives them without issue, it seems if the host were the problem I would not receive them in either case. Since I do receive them in webmail and in Gmail when I generate them it seems S2 member is where the glitch originates.
Furthermore, my contact form (not an S2 member form) delivers mail immediately on the same site where I’ve got S2member installed, and the host has no delivery issues. From where I’m sitting S2 member forms remain suspect.
There has to be another way to prove S2 member is not the issue. One of the S2 member forms should work without a hitch, but which S2 member form is the best to test. This raises a more fundamental question: Is there ANOTHER EMAIL SETTING in S2 member that is causing the delivery issue to email clients?
I know you seem ready to hang it on the host, but I’m asking in the spirit of understanding the true smoking gun.
Would you like me to send screenshots of every email setting in S2 member to see if it reveals important information that we’re missing?
To quote the host’s email server guy…
“220-We do not authorize the use of this system to transport unsolicited, and/or bulk e-mail.” — is not an error — This is the statement the server gives to any incoming connection. You can see this by seeing the next line is the server saying hello, “EHLO localhost250-whub44.webhostinghub.com Hello” which precedes it actually receiving your message data. You can also see at the bottom the server reports a 250 OK which is it saying everything went as expected in the sending “250 OK id=1aPC2B-0003M0-Fg “.
These emails are being sent to customer@creatorsite.com and admin@creatorsite.com, when logging into the webmail via cPanel and checking the inbox of these accounts I see a number of emails with the subjects “[creatorsite.com] Username/Password” and “[creatorsite.com] New User Registration” which are coming from your plugin.
Are you potentially checking for these emails in a third party email client? Are you able to see other emails in your inbox besides the test messages?
Checked with the host and it is NOT blocking. The messages are getting through, but for some reason Gmail is not receiving. Proof is twofold . . .
1. the messages are in my webmail account associated w/my hosting account.
2. I can send messages to the addresses involved and they come through without issue.
Any ideas about the next suspect?
Okay. Thanks. I’ll follow your instructions.
Thanks. Will do.
Everything seems good. The only section in the transcript I wasn’t certain about was . . .
220-whub44.webhostinghub.com ESMTP Exim 4.85 #2 Thu, 28 Jan 2016 15:29:34 -0800
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.Everything else said “succeeded,” or “accepted.”
Upon your recommendation…
I installed the Postman
configured through the wizard
confirmed the settings
cleared cache
deleted the WP SMTP plugin
ran another test
but still nothingIt was the plugin, which I’ve fixed. Thank you for your assistance.
I’ve got a message into a developer of a plugin, Mediapress, because it is generating an error.
Thanks. I’ll do that now.
By “white screen” I mean that it’s blank where the content should be, but the header, logo, menu, footer are all there.
It’s just a white screen. How do I turn on debug?
Let me try to explain another way…
I have a page labeled, “login,” which is where the code is placed.
My understanding from the knowledge base page is that the shortcode will redirect to another page labeled, “account.”
Does that make sesne?
Here’s the S2 member knowledge base page where I got the information.
http://s2member.com/kb-article/s2member-login-shortcode-documentation/
Yes. That’s where I placed the shortcode, which is a separate page from the account page.