Thanks for the reply,
but again, i’m not sure if the problem is the error msg or maybe it’s actually ok that the sender is not the same as the blog’s domain?
i changed the ‘fake’ user’s (the one that i’m using in Subscriber2) email from user@domain.com to user@hosting.com just to see the difference in the email source, and this is the outcome:
Delivered-To: my_email@gmail.com
Return-Path: <name@253717.hostname.net>
Received: from 253717.hostname.net ([xxx.xxx.xxx.xx])
To: my_email@gmail.com
Subject: =xxxx=
From: blogname <name@253717.hostname.net>
Reply-To: <name@253717.hostname.net>
so compared to the prev email src, it’s obvious that you control the ‘From’, and ‘Reply-To’,
so maybe, and again i’m not an expert on email ‘rules’, in scenarios like mine (on shared hosting etc), the ‘From’ should be the hosting address (and not the domain, since the email are coming from the hosting mail server), and the ‘Reply-To’ can actually be anything the user chooses?
or maybe just to have the ability to manually set these settings with an input box? that way you can set the reply-to to a diff address, since many admins probably never read their domain email at all.
I don’t see why these 2 settings has to be the domain, while the ‘Return-Path’ and ‘Received’ are set to the hosting’s.
also i noted on my prev comment, that when i select in Subscriber2 ‘From’ dropdown the ‘blog name’, and set the blog email to the domain, it shows the warning msg, as if it’s pulling the email from somewhere else, why is that?
thanks again
@finklez,
From the 2 message headers it seems that if you use a on-domain sender that is preserved, if you use and off domain sender then the header is re-written to your hostname.net details.
The warning message does not stop anything from happening though – it’s just a message. It’s being improved in the next version though to make it more sensitive to the actual settings. If your emails are sending please ignore it.
Hi mattyrob,
I am also struggling with this warning message.
To get rid of it, I followed exactly your recommendation on creating a new user with an email address same like the domain. Done, de-activated plugin, re-activated plugin and guess what : warning message still is present. I have no clue why: domain name is ‘siedelwood.de’, email is ‘siedelwood@siedelwood.de’ and ‘Send email from’ is set to user ‘siedelwood’.
Does the warning check IP addresses? Because this is different. My email server is not on the same IP as my web server using a MX record.
Or what else could cause the warning then?
Users report that email notification is unreliable – sometimes they get emails, sometimes not. Sending wp_mail direct from my code always works – nothing is lost.
@hittheroadjack,
Okay, you’ve done the first step in creating a user with an on-domain email address but you haven’t said whether you changed the Sender in the Subscribe2->Settings page.
I suspect the ‘siedelwood’ entry is the name of your blog rather than a specific user. So, in the dropdown list in the settings page where it says “Send Email From:” you need to pick an option other than the top two that are available. Try to pick the user name of the user you created with your on-domain email address.
IP addresses are not checked, just the domain aspect of the sending account email address.
Also step two was completely done:
‘Send email from’ is set to user ‘siedelwood’
The user name created and selected is ‘siedelwood’ and the domain/blog name is ‘siedelwood.de’.
the full email address is ‘siedelwood@siedelwood.de’. Tested with wp_mail from my own code in functions.php and with WP SMTP Email plugin’s test facility and it works perfect.
And after selecting this user, I ran through a de-activate/re-activate cycle.
The message did not get away.
@hittheroadjack,
I’ve just visited your site again to have a look – your domain name resolves to an IP address at the moment and this is displayed in the browser address bar.
My code compares what is stored by PHP in the global variable $_SERVER[‘SERVER_NAME’] with the domain part of the entered email address.
I suspect the global variable $_SERVER[‘SERVER_NAME’] actually contains your server IP address rather than the domain. Do you know why your site is like that?
I guess, there have been problems with migrating the site to a new server . So they solved it by a quick 301 redirect rather than a in AA record + migrating the database.
If it is like that and it is just the way you generate the warning message, it does not harm me and my users any further. If email servers do it in a similar way and thus we are having troubles delivering notifications that would be more severe.
Do they mind a redirect? This is happening all the time in the net when moving sites!
@hittheroadjack,
This is just a warning message and it does not stop the sending of emails. It simply warns you of a major reason why your emails may not send.
I don’t think the mail server will be affect by a re-direct but I honestly don’t know; I’ve migrated hosts twice and never had this issue arise.
Now I know and I plan to fix it with the next server maintenance with a longer announced time-out period.
Thanks for helping!
Hi i am seeing this below thread on my blog when i click on to subscribers on subscribe2 settings tab….how to rectify…
Fatal error: Class ‘Subscribe2_List_Table’ not found in /home/rajaht64/public_html/wp-content/plugins/subscribe2/admin/subscribers.php on line 136
@bheem,
This is a know issue affecting some sites probably down to your PHP version.
It’s fixed in the development version that you can access and install from here:
http://downloads.wordpress.org/plugin/subscribe2.zip
Also, as a polite request, please note that you should open a new thread for new issues instead of joining onto the end on an unrelated thread – getting a response is more likely this way.
