A few months ago I set up WAMP server on my Windows 7 machine to develop a Wordpress site locally. I added Sendmail.exe to make Contact Form 7 (a contact form which sends out an email from me, to me) work properly. All was well. But, on a once or twice daily basis, I receive, to the Gmail account I set up with sendmail, a "testing sendmail.exe" email. Even when my computer (running WAMP) is off. How can this be?
Once the development of the website was complete and ready to go live, I uploaded it using the Wordpress Duplicator (https://wordpress.org/plugins/duplicator/) plugin. I have searched (using ftp) through the live site, and cannot find any kind of sendmail files there.
For client approval, I uploaded the site (again using the Worpdress Duplicator plugin) to a subdirectory on my own site, but since then I have deleted all the files from that directory.
So my question is: How on earth are theses emails getting sent? Does the sendmail application actually use some other server somewhere out there (not my WAMP "server") to send the emails, and it's got stuck in the habit of sending out this test email?
Thanks in advance for any help on this!
Here's the full header (I've changed my email to "xxxxxxx#gmail.com"):
Delivered-To: xxxxxxx#gmail.com Received: by 10.25.214.135 with
SMTP id p7csp302451lfi; Sat, 13 Dec 2014 06:57:18 -0800 (PST)
X-Received: by 10.181.12.17 with SMTP id em17mr16780659wid.45.1418482637935; Sat, 13 Dec 2014 06:57:17 -0800 (PST)
Return-Path: <xxxxxxx#gmail.com> Received: from mout.kundenserver.de (mout.kundenserver.de. [212.227.126.131])
by mx.google.com with ESMTPS id gf8si8194056wib.61.2014.12.13.06.57.17 for <xxxxxxx#gmail.com>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 13 Dec 2014 06:57:17 -0800 (PST)
Received-SPF: softfail (google.com: domain of transitioning xxxxxxx#gmail.com does not designate 212.227.126.131 as permitted sender)
client-ip=212.227.126.131; Authentication-Results: mx.google.com; spf=softfail
(google.com: domain of transitioning xxxxxxx#gmail.com does not designate 212.227.126.131 as permitted sender) smtp.mail=xxxxxxx#gmail.com;
dmarc=fail (p=NONE dis=NONE) header.from=gmail.com
Received: from icpu1054.kundenserver.de
(infong247.kundenserver.de [212.227.29.151]) by mrelayeu.kundenserver.de
(node=mreue007) with ESMTP (Nemesis) id 0LbCQQ-1XXwAh0AAM-00kyHa; Sat, 13 Dec 2014 15:57:17 +0100
Received: from 72.167.159.8 (IP may be forged by CGI script) by icpu1054.kundenserver.de with HTTP id 49vAEC-1XsTpZ40PF-017nps; Sat, 13 Dec 2014 15:57:16 +0100
X-Sender-Info: <264661319#icpu1054.kundenserver.de> Date: Sat, 13 Dec 2014 15:57:16 +0100 Message-Id: <49vAEC-1XsTpZ40PF-017nps#icpu1054.kundenserver.de> Precedence:
Paul
Related
I have an Ubuntu-server with Wordpress installed. When sending out emails from the server I get the following header:
Received-Spf: neutral.
I did set the SPF-record in the following matter:
v=spf1 mx a include:_spf.google.com include:spf.gigahost.dk ~all
The a-record resolves to the IP of my server which is
46.101.199.65
When testing with http://vamsoft.com/support/tools/spf-policy-tester with the IP and email hello#kjottogblod.com it passes.
Any idea why Google is not marking emails send from the server as "pass"?
This is the complete header. I've replaced my email with xxx#xxx.com. But the receiving email is a Google Apps account.
Delivered-To: xxx#xxx.com
Received: by 10.157.38.140 with SMTP id l12csp352662otb;
Tue, 5 Jul 2016 06:42:16 -0700 (PDT)
X-Received: by 10.28.50.131 with SMTP id y125mr17192051wmy.94.1467726136065;
Tue, 05 Jul 2016 06:42:16 -0700 (PDT)
Return-Path: <www-data#ubuntu-2gb-fra1-01-tpk>
Received: from ubuntu-2gb-fra1-01-tpk ([46.101.199.65])
by mx.google.com with ESMTP id f66si16033wme.56.2016.07.05.06.42.15
for <xxx#xxx.com>;
Tue, 05 Jul 2016 06:42:16 -0700 (PDT)
Received-SPF: neutral (google.com: 46.101.199.65 is neither permitted nor denied by best guess record for domain of www-data#ubuntu-2gb-fra1-01-tpk) client-ip=46.101.199.65;
Authentication-Results: mx.google.com;
spf=neutral (google.com: 46.101.199.65 is neither permitted nor denied by best guess record for domain of www-data#ubuntu-2gb-fra1-01-tpk) smtp.mailfrom=www-data#ubuntu-2gb-fra1-01-tpk
Received: by ubuntu-2gb-fra1-01-tpk (Postfix, from userid 33)
id AF06414471B; Tue, 5 Jul 2016 09:42:15 -0400 (EDT)
To: xxx#xxx.com
Subject: =?UTF-8?Q?Your_Kj=C3=B8tt_og_Blod_order_receipt_from_July_5,_2016?=
X-PHP-Originating-Script: 33:class-phpmailer.php
Date: Tue, 5 Jul 2016 13:42:15 +0000
From: =?UTF-8?Q?Kj=C3=B8tt_og_Blod?= <hello#kjottogblod.com>
Message-ID: <9e947b8b46848b4f9fb10ff2e25ee2a1#kjottogblod.com>
X-Mailer: PHPMailer 5.2.14 (https://github.com/PHPMailer/PHPMailer)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
It's the smtp.mailfrom address that is used in the SPF check. This is the so-called envelope sender. And since ubuntu-2gb-fra1-01-tpk is not a valid domain it can not have a SPF record, hence the Neutral result.
So you will have to set up your Wordpress installation to use a better envelope-sender. I'm no Wordpress expert, but it seems that there are several filters/plugins that allow you to change the mail settings.
I have a web application that offers file downloading functionality. I would like to enable browser cache (Cache-Control header) so that subsequent downloads of a file come from the browser cache, instead of generating a new HTTP Request to the server.
HTTP Request:
http://localhost:9080/webapp/action/content/somefile.exe
HTTP Response:
Cache-Control:max-age=600
Content-Disposition:inline;filename="somefile.exe"
Content-Length:20952624
Content-Type:application/x-msdownload
Date:Thu, 22 Oct 2015 10:46:17 GMT
Last-Modified:Thu, 22 Oct 2015 10:44:49 GMT
X-Powered-By:Servlet/3.1
However, despite the Cache-Control header, the browser (latest releases from Firefox & Chrome) always asks the server for the file. Any idea why?
I currently have a client that is using AEM 6.0. As they have some URL's that are lengthy they have been looking for a solution to shorten them without editing a virtual host file and adding redirects to the virtual host (they do not have the proper knowledge to do that). The only solution I found was to use vanity urls which per my research is supported in AEM 6.0 and as of Dispatcher 4.1.9.
Currently they have a dispatcher version 4.1.10 and I have gone through the AEM documentation https://docs.adobe.com/docs/en/dispatcher/disp-config.html#par_title_21 that discribes how to configure the Dispatcher and Publisher to enable access to vanity urls.
So far:
I have installed the VanityURLS-Components package on the Publisher.
I have added the following configuration to the dispatcher.any on the Dispatcher:
/vanity_urls {
/url "/libs/granite/dispatcher/content/vanityUrls.html"
/file "/tmp/vanity_urls"
/delay 300
}
and checked that the paths are correct.
I have created /tmp/vanity_urls file with ownership of apache:apache (this is on Centos) and permissions of 777.
And I have restarted apache.
Despite these steps it looks like I've overlooked something as /tmp/vanity_urls is not being updated. Maybe there is something I am not understanding here but I thought that the dispatcher updated every x seconds (here 300) /tmp/vanity_urls via the Publisher's /libs/granite/dispatcher/content/vanityUrls.html. Then used /tmp/vanity_urls as a whitelist of vanity urls that are allowed.
I am wondering why this is not working, any thoughts ?
Could it be a permission issue on /tmp/vanity_urls ?
Maybe there is something I erroneously assumed ?
Are there existing bugs out there I am unaware of that impact this dispatcher vanity urls feature ?
Any help is welcome ...
Best,
Nicola
UPDATE:
In my logs found the following:
[Thu Oct 08 16:11:03 2015] [D] [1780(140151407138784)] Vanity URL file (/tmp/vanity_urls) too old (1443478601 < 1444345863) on startup, fetching...
[Thu Oct 08 16:11:03 2015] [D] [1780(140151407138784)] Creating new socket: 127.0.0.1:8080
[Thu Oct 08 16:11:03 2015] [W] [1780(140151407138784)] Unable to connect to 127.0.0.1:8080: Connection refused
[Thu Oct 08 16:11:03 2015] [D] [1780(140151407138784)] incomplete request, no socket reuse
[Thu Oct 08 16:11:03 2015] [E] [1780(140151407138784)] Unable to fetch vanity URLs on farm website: no backend available.
[Thu Oct 08 16:11:03 2015] [D] [1780(140151407138784)] Loaded 0 vanity URLs from file /tmp/vanity_urls
Fairly self explanatory given that my publisher is not on localhost port 8080 ...
Hopefully that should fix my issue will update soon.
Thanks,
Nicola
I figured it out it was a network issue nothing to do with AEM,
/libs/granite/dispatcher/content/vanityUrls.htm was not accessible from my publisher.
I'm running Wordpress 4.2 on AWS Elastic Beanstalk. I'm using a plugin that sends emails using the WP email API, which uses the server's (i.e. Elastic Beanstalk's) internal mail system.
The problem: emails that the app attempts to send to my university email (let's call it .uni.edu) fail, and they do work when sent to my standard gmail.
What's interesting is that I have no issues running the same application locally. The emails associated with the app send fine -- so obviously there's some issue with the way Elastic Beanstalk in particular is attempting to relay the messages to the .uni.edu server. Perhaps the .uni.edu server is picking it up as spam (when sent from Elastic Beanstalk, not when being sent through my local system) and bouncing it back, but I'm not experienced enough to diagnose this.
Does anyone have suggestions for either directly applying some kind of fix to this problem, or creating some sort of setup that is a workaround (e.g. setting something up on Elastic Beanstalk to send emails in a non-default way that is less likely to have issues working with the university email server)?
Here's a log from /var/mail:
From MAILER-DAEMON#ip-172-31-41-109.ec2.internal Fri Apr 24 21:39:52 2015
Return-Path: <MAILER-DAEMON#ip-172-31-41-109.ec2.internal>
Received: from localhost (localhost)
by ip-172-31-41-109.ec2.internal (8.14.4/8.14.4) id t3OLdq1k026047;
Fri, 24 Apr 2015 21:39:52 GMT
Date: Fri, 24 Apr 2015 21:39:52 GMT
From: Mail Delivery Subsystem <MAILER-DAEMON#ip-172-31-41-109.ec2.internal>
Message-Id: <201504242139.t3OLdq1k026047#ip-172-31-41-109.ec2.internal>
To: <webapp#ip-172-31-41-109.ec2.internal>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="t3OLdq1k026047.1429911592/ip-172-31-41-109.ec2.internal"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)
This is a MIME-encapsulated message
--t3OLdq1k026047.1429911592/ip-172-31-41-109.ec2.internal
The original message was received at Fri, 24 Apr 2015 21:39:42 GMT
from localhost [127.0.0.1]
----- The following addresses had permanent fatal errors -----
<univstudent#uni.edu>
(reason: 553 5.1.8 <webapp#ip-172-31-41-109.ec2.internal>... Domain of sender address webapp#ip-172-31-41-109.ec2.internal does not exist)
----- Transcript of session follows -----
... while talking to apathy.uni.edu.:
>>> MAIL From:<webapp#ip-172-31-41-109.ec2.internal> SIZE=1191
<<< 553 5.1.8 <webapp#ip-172-31-41-109.ec2.internal>... Domain of sender address webapp#ip-172-31-41-109.ec2.internal does not exist
501 5.6.0 Data format error
--t3OLdq1k026047.1429911592/ip-172-31-41-109.ec2.internal
Content-Type: message/delivery-status
Reporting-MTA: dns; ip-172-31-41-109.ec2.internal
Received-From-MTA: DNS; localhost
Arrival-Date: Fri, 24 Apr 2015 21:39:42 GMT
Final-Recipient: RFC822; univstudent#uni.edu
Action: failed
Status: 5.1.8
Diagnostic-Code: SMTP; 553 5.1.8 <webapp#ip-172-31-41-109.ec2.internal>... Domain of sender address webapp#ip-172-31-41-109.ec2.internal does not exist
Last-Attempt-Date: Fri, 24 Apr 2015 21:39:52 GMT
--t3OLdq1k026047.1429911592/ip-172-31-41-109.ec2.internal
Content-Type: message/rfc822
Return-Path: <webapp#ip-172-31-41-109.ec2.internal>
Received: from ip-172-31-41-109.ec2.internal (localhost [127.0.0.1])
by ip-172-31-41-109.ec2.internal (8.14.4/8.14.4) with ESMTP id t3OLdg1k026045
for <univstudent#uni.edu>; Fri, 24 Apr 2015 21:39:42 GMT
Received: (from webapp#localhost)
by ip-172-31-41-109.ec2.internal (8.14.4/8.14.4/Submit) id t3OLdgcq026044;
Fri, 24 Apr 2015 21:39:42 GMT
To: univstudent#uni.edu
Subject: [classifiedads] Password Reset
X-PHP-Originating-Script: 498:class-phpmailer.php
Date: Fri, 24 Apr 2015 21:39:42 +0000
From: WordPress <wordpress#classifiedads-test.elasticbeanstalk.com>
Message-ID: <bace4f13cdc099117cd4ac9c70e2531c#classifiedads-test.elasticbeanstalk.com>
X-Priority: 3
X-Mailer: PHPMailer 5.2.7 (https://github.com/PHPMailer/PHPMailer/)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Someone requested that the password be reset for the following account:
http://classifiedads-test.elasticbeanstalk.com/
Username: univstudentseas
If this was a mistake, just ignore this email and nothing will happen.
To reset your password, visit the following address:
<http://classifiedads-test.elasticbeanstalk.com/wp-login.php?action=rp&key=dzaUvJpcjAe243gNOysZ&login=univstudentseas>
--t3OLdq1k026047.1429911592/ip-179-35-41-109.ec2.internal--
This sounds very similar to another recent question about email:
http://stackoverflow.com/questions/29808262/unable-to-send-emails-from-linux/29810884#29810884
Does your ec2 instance have an associated external DNS? Is there a public IP associated with it. You'll need to apply some type of fix so that your outgoing email message has a domain other than webapp#ip-172-31-41-109.ec2.internal
We are transferring servers tonight, and we started the process. The new DNS has resolved and everything, but if you type in the site name localreviewengine.com. It kicks it to http//localreviewengine.com (so really, http://http//localreviewengine.com).
What would cause that? It's a wordpress install, and Sitename and Home in the DB are set properly, there are no redirects in CPanel, and the htaccess looks fine?
EDIT: It looks like localreviewengine.com/readme.html works though..?
Watching the response headers for this site brings a bit light into the dark:
~ # curl -I "http://localreviewengine.com/"
HTTP/1.1 301 Moved Permanently
Date: Sat, 01 Dec 2012 01:57:11 GMT
Server: Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/1.0.0-fips DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
X-Powered-By: PHP/5.2.17
Location: http://http://localreviewengine.com
Content-Type: text/html
As you can see webserver is redirecting to http://http://localreviewengine.com
That's a typo / incorrect protocol prefix in your configuration.
check your apache config or (most likely) your document root .htaccess
Did you add any redirect / rewrites for the move process? e.g. we're moving our site, come back when the 5.000 machines are finally up and running again? (hopefully)