Sending an email using someones email address (NOT SPAM)

Hi, just like to say this is not a spam question before we start.

I'm working on a newsletter project for a company. Their email is run through an internal server containing Microsoft Exchange, say the domain is www.internal.com. The newsletter system I'm building is hosted on a third party remote server (Digiweb), under domain www.external.com. When the newsletters are sent from the external server, they need to appear as though they're being sent from the internal email addresses of www.internal.com.

Using PHPMailer, I can change the sender's email address and name. This works fine......but the emails are only received by non-Microsoft Exchange servers.....for example my personal Yahoo and Hotmail accounts.

I've done some digging into the header and I found this line:

Received-SPF: none (mail1.hosting.digiweb.ie: domain at win4.hosting.digiweb.ie does not designate permitted sender hosts)

How do I overcome this? Can I add the IP Address of the Microsoft Exchange server to the code in PHPMailer, thereby authenticating the header? Thanks in advance, sorry if the question is in breach of the EE guidelines but it's a genuine non-spam question.
kbitAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

VanHackmanCommented:
"When the newsletters are sent from the external server, they need to appear as though they're being sent from the internal email addresses of www.internal.com. "

Woowowow!... You are in a little trouble, if you really need that your clients get successful your Newsletter you must consider (and do it) to host the Newsletter application in the same server of  www.internal.com domain,  if both domains were hosted in the same server would not have any problem, but in your case, seems almost impossible delivery your Newsletters successful  without get flagged as SPAM
0
kbitAuthor Commented:
Even if I send the email from "noreplies@external.com" I get the same SPF error, even though that email account does exist on that server.
0
Ray PaseurCommented:
SPF is specifically for preventing what you are trying to do here.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Ray PaseurCommented:
This is a nettlesome issue, so I will give you my take on it.  First the easy answer (and the one I have come to use with great success for thousands of emails every week).  Drop everything and use Constant Contact.  They run a business with full-time employees devoted to making sure your email gets to the intended recipients.  You cannot do what they do, and it is embarrassingly inexpensive - literally less than the cost of a cup of coffee per day.  There are other vendors besides CC, but we chose them because my staff liked their web interface.  It has been an excellent experience.

Now to the second (and in my mind less satisfactory) solution... learn about SPF.  Read this:
http://emailuniverse.com/ezine-tips/?id=1202

You will want the owners of the domain to take action on your behalf.  SPF allows a domain to specify which machines are authorized to send email for that domain.  They will need to specify that your server is allowed to send the email.

SPF is a big step in the right direction, but you will still have anti-spam issues, and dealing with those is a time-consuming and thankless task.  That is why the Constant Contact solution is so inviting.  After you lose a few days of your life explaining to your clients why their emails were mishandled, you will probably agree about Constant Contact.

Best regards, and best of luck with it, ~Ray
0
kbitAuthor Commented:
OK thanks for that, so SPF is to prevent faking someone else's email address.

But if I send the newsletter from tom@external.com on the EXTERNAL machine, why does it still give the same SPF warning? The tom@external.com email account is on that server
0
kbitAuthor Commented:
Maybe it doesn't matter, the email gets through to the invox and is not detected as spam in Yahoo,Google,Outlook (with high sensitivity junk settings) or Gmail.
0
Ray PaseurCommented:
The SPF warning shows up when the domain host does not have SPF records that identify the sending host as a permitted sender.  It is not dependent on the domain names at all (these can be faked as everyone who has ever received any spam knows), only on the presence of the record.
0
kbitAuthor Commented:
So which server needs the SPF details added to it, the one I've described as internal (MS Exchange) or my external one (3rd party)?
0
Ray PaseurCommented:
You will want the owners of the domain to take action on your behalf.  SPF allows a domain to specify which machines are authorized to send email for that domain.  They will need to specify that your server is allowed to send the email.

So if your domain is "myDomain.com" you need to get the owners of that domain name involved.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
kbitAuthor Commented:
Ok thanks for that, will my server's IP Address be enough for the other domain administrator to add the TXT record?
0
kbitAuthor Commented:
The Exchange guy sent me his SMTP details which I entered into my PHPMailer script and it looks encouraging but not sure if the header information indicates that things are good or not (I've masked the names, email addresses and domains):
Return-Path: <system.notification@internal.com>
Delivered-To: me@myemailaddress.ie
X-Envelope-To: me@myemailaddress.ie
Received: (qmail 26177 invoked by uid 399); 22 Jan 2010 17:11:07 -0000
Received: from unknown (HELO server107.appriver.com) (207.97.204.37)
  by mail1.hosting.digiweb.ie with ESMTP; 22 Jan 2010 17:11:07 -0000
X-Originating-IP: 207.97.204.37
Received-SPF: none (mail1.hosting.digiweb.ie: domain at internal.com does not designate permitted sender hosts)
	identity=mailfrom; client-ip=207.97.204.37;
	envelope-from=<system.notification@internal.com>;
X-Policy: GLOBAL - internal.com
X-Primary: system.notification@internal.com
X-Note: This Email was scanned by AppRiver SecureTide
X-ALLOW: system.notification@internal.com ALLOWED
X-Virus-Scan: V-
X-Note: Spam Tests Failed: 
X-Country-Path: UNITED STATES->UNITED STATES->UNITED STATES->UNITED STATES
X-Note-Sending-IP: 207.97.230.162
X-Note-Reverse-DNS: fe02.exg3.exghost.com
X-Note-WHTLIST: system.notification@internal.com
X-Note: User Rule Hits: 
X-Note: Global Rule Hits: G115 G116 G117 G118 G122 G123 G134 G221 
X-Note: Encrypt Rule Hits: 
X-Note: Mail Class: ALLOWEDSENDER
X-Note: Headers Injected
Received: from [207.97.230.162] (HELO FE02.exg3.exghost.com)
  by server107.appriver.com (CommuniGate Pro SMTP 5.3.0)
  with ESMTP id 203217760 for me@myemailaddress.ie; Fri, 22 Jan 2010 12:11:06 -0500
Received: from FE02.exg3.exghost.com ([207.97.230.162]) by FE02.exg3.exghost.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Fri, 22 Jan 2010 12:10:59 -0500
Received: from www.external.com ([207.97.202.208]) by FE02.exg3.exghost.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Fri, 22 Jan 2010 12:10:58 -0500
Date: Fri, 22 Jan 2010 17:10:55 +0000
Return-Path: System.notification@internal.com
To: me@myemailaddress.ie
From: =?iso-8859-1?Q?Joe_Bloggs=2C_MyCompany?= <System.notification@internal.com>
Reply-to: =?iso-8859-1?Q?Joe_Bloggs=2C_MyCompany?= <joe.bloggs@internal.com>
Subject: Newsletter 22/01/2010
Message-ID: <b192467d9428225fd008a8827abe2428@www.external.com>
X-Priority: 3
X-Mailer: PHPMailer 5.1 (phpmailer.sourceforge.net)
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset="iso-8859-1"
X-OriginalArrivalTime: 22 Jan 2010 17:10:58.0945 (UTC) FILETIME=[DDE8AF10:01CA9B85]
X-Antivirus: AVG for E-mail 8.5.432 [271.1.1/2638]

Open in new window

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
PHP

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.