2013-11-11 6:48 pm EST
If you are using PHPMAIL in order to send emails, then it will typically use the account user name and server name as the sending address. For example, account5@domain_name.com. However, if you are using SMTP settings to send the email then it would require a valid email account for authentication. We have an article on how PHPmailer works here if you want to compare. The WordPress plugins generally give you the option. However, if you're using SMTP (meaning that you're using a domain email account), then it should still work, but will use your account user name in order to identify the email sender.
The answer to your question is no - the email would still go out, but use the user name on the account as the sender. You would need to provide a link for screenshots if you want use them on the posts in the Support center.
I hope this helps to answer your question, please let us know if you require any further assistance.
http://imageshack.com/a/img203/8725/jg07.jpg link to my real life example. i used the same @hotmail.com email in both "Email To:" and "Return-path" address and the forms' send is working, i'm getting (at least some) form messages to the @hotmail.com id. so i'm assuming Inmotionhosting is NOT in the same category as Godaddy, (not allowing this to happen).
i have 25, going to 40, domains/sites on my inmotionhosting account. i do NOT want to set domain emails for each account unless i have to, i want to use a hotmail, gmail. yahoo email id. unless inmotionhosting will make some future server changes that makes using @hotmail.com email stop working.
this plugin has not settings for phpmailer or SMTP. the plugin, wordpress, or default install of wordpress must have defaults settings. i never did a thing on inmotion to ever set up any email accounts.
<div style="background-color: #FFF; padding-left: 10px;">Hello Lee,
As you've already discovered on our servers it will allow you specify an email address outside of the domain name you're hosting with us to send email. However please keep in mind, that for the longevity of your mailing activities, it probably wouldn't be advisable to do this.
The reason being is that large mail hosts like <strong>hotmail.com</strong> will publish <a href="http://www.inmotionhosting.com/support/edu/everything-email/spam-prevention-techniques/spf-records-domain-keys-combating-spam" target="_blank">SPF records</a> or <strong>Sender Policy Framework</strong> records, to dictate what mail server IP addresses other mail servers should expect mail from <strong>@hotmail.com</strong> users from to help weed out spam.
That DNS SPF record looks like this for <strong>hotmail.com</strong>:
<pre class="code_block" style="width: 500px; white-space: normal; margin-bottom: -30px;">"v=spf1 include:spf-a.hotmail.com include:spf-b.hotmail.com include:spf-c.hotmail.com include:spf-d.hotmail.com ~all"</pre>
Each of those <strong>include:</strong> statements includes a range of IPs, for instance the <strong>spf-a.hotmail.com</strong> SPF record looks like this:
<pre class="code_block" style="width: 500px; white-space: normal; margin-bottom: -30px;">"v=spf1 ip4:220.127.116.11/26 ip4:18.104.22.168/26 ip4:22.214.171.124/25 ip4:126.96.36.199/24 ip4:188.8.131.52/26 ip4:184.108.40.206/26 ip4:220.127.116.11/24 ip4:18.104.22.168/25 ip4:22.214.171.124/24 ip4:126.96.36.199/24 ip4:188.8.131.52/24 ip4:184.108.40.206/24 ~all"</pre>
So even though our server will allow you to use a <strong>@hotmail.com</strong> address as your <strong>Return-path address</strong>. It will be dependant on the spam policies of the <strong>Email to</strong> address and its mail server, which could possibly cause the message to get flagged as spam.
For instance, I set the <strong>Email to</strong> value to my <strong>@gmail.com</strong> account, and just set the <strong>Return-path address</strong> to <strong>email@example.com</strong>. Our server sends out the message without any issue at all, but when looking at the message that ends up on <strong>gmail.com</strong> you can see it's detecting a SPF problem:
<pre class="code_block" style="width: 500px; white-space: normal; margin-bottom: -30px;"><strong style="color: red;">Received-SPF: softfail</strong> (google.com: domain of transitioning <strong style="color: red;">firstname.lastname@example.org does not designate 220.127.116.11 as permitted sender</strong>) client-ip=18.104.22.168;
<strong style="color: red;">spf=softfail</strong> (google.com: domain of transitioning <strong style="color: red;">email@example.com does not designate 22.214.171.124 as permitted sender</strong>) smtp.mail=<strong style="color: red;">firstname.lastname@example.org</strong>
Received: from example by vps1234.inmotionhosting.com with local (Exim 4.80.1)
(<strong style="color: red;">envelope-from <email@example.com></strong>)</pre>
It's pretty easy to <a href="http://www.inmotionhosting.com/support/edu/everything-email/introduction-email/creating-email-account" target="_blank">create an email account</a> or in your case to simply <a href="http://www.inmotionhosting.com/support/edu/cpanel/cpanel-email/import-email-accounts-forwarders-in-cpanel" target="_blank">import email accounts from a CSV file</a>. For instance if you had this stored in an <strong>emails.csv</strong> file:
<pre class="code_block" style="width: 500px; white-space: normal; margin-bottom: -30px;">Email,Password,Quota
Then imported it into cPanel, it would create 3 separate email accounts across your domains, <strong>firstname.lastname@example.org</strong>, <strong>email@example.com</strong>, and <strong>firstname.lastname@example.org</strong> in this case all with the same password <strong>PasswordHere</strong> and a <strong>0</strong> or <strong>unlimited</strong> mail quota.
This would be your best bet to ensure that even though something might work right this moment, it continues to work going forward for you as well.