Am using phpmailer to send email from my Gmail account.
Gmail is not delivering emails if I have a link in message body. Here is my email
Dear Zeeshan,
Thank you again for calling Test. We improve our service based on your feedback. Will you please rate your experience to let us know how we did? Click on the link below!
Click Here to Share Your Review
If I remove the link, email works fine. What is issue with this link?
Here is what gmail send me back
Delivery to the following recipient failed permanently:
shah.zeshan#gmail.com
Technical details of permanent failure:
Message rejected. See https://support.google.com/mail/answer/69585 for more information.
----- Original message -----
X-Received: by 10.202.67.133 with SMTP id q127mr3207265oia.116.1455592533646;
Mon, 15 Feb 2016 19:15:33 -0800 (PST)
Return-Path: <lockandtowservice#gmail.com>
Received: from rsasatisfaction.com (rs43.whbdns.com. [209.105.241.194])
by smtp.gmail.com with ESMTPSA id pp10sm17110856obc.16.2016.02.15.19.15.32
for <shah.zeshan#gmail.com>
(version=TLSv1/SSLv3 cipher=OTHER);
Mon, 15 Feb 2016 19:15:32 -0800 (PST)
Date: Tue, 16 Feb 2016 03:15:31 +0000
Return-Path: lockandtowservice#gmail.com
To: shah.zeshan#gmail.com
From: Test <lockandtowservice#gmail.com>
Subject: Share Your Review For Test
Message-ID: <5b7609c465e4ebe2ef057cc7f0db582f#rsasatisfaction.com>
X-Priority: 3
X-Mailer: PHPMailer 5.2 (http://code.google.com/a/apache-extras.org/p/phpmailer/)
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="b1_5b7609c465e4ebe2ef057cc7f0db582f"
<p>
Dear Zeeshan,
</p>
<p>
Thank you again for calling Test. We improve our
service based on your feedback. Will you please
rate your experience to let us know how we did?
Click on the link below!
</p>
<p>
<a
href="http://rsasatisfaction.com/home/feedback/57/1/Zeeshan/shah.zeshan#gmail.com">Click
Here to Share Your Review</a>
</p>
<p>
Thank you again. If we can be of more service,
please let us know.
</p>
<p>
Warm regards,<br>
Test<br>
</p>
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
Gmail gets flooded with spam emails from AWS Ses
After my spam email folder gets full the gmail is not getting any more emails. How can I report to AWS Ses not to send me an email from a specific AWS Ses Account.
Here is the details. I have contacted the company who is sending the emails. They are unable to solve the issue. ( In 3 years cant cope with change ).
I was once a permitted receiver but not anymore. Help would be appreciated.
Delivered-To: rifaterdemsahin#gmail.com Received: by 10.100.151.140
with SMTP id q12csp736984pja;
Thu, 22 Jun 2017 18:55:26 -0700 (PDT) X-Received: by 10.200.47.87 with SMTP id k23mr6662116qta.11.1498182926606;
Thu, 22 Jun 2017 18:55:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1498182926; cv=none;
d=google.com; s=arc-20160816;
b=VjPlf2DSOO/X+jFewPovx0GPtS81NriE988G1yhFs0sWUAULrnp31pIDjiI3v/MC2h
VOJDD6IkKpp+gsU4gYLo8BRoS71ZiHtB6O7Yk1z5Nc7QKxk+FjBuGK75Y8qM3dObxCKU
FpZ3vwZrmwHbL8etRznU/DwfcN5f60GP45eINzKe7QYS+HOquiISKfFI6Kjac5/GvHqu
fRL2zdFHu5E2aIXGUMUK4EdVsFjMQUsJUqBJC0OSoqLesyLdoyqV4oTAunH8BwYKWEY4
/JTNP2zR6+6wucgfEVVPUQ5W6ocKVWPlJnHDw+vP1y6JkKMNaNj9mYl0LORMKHU71ptN
f8Ig== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=feedback-id:date:message-id:content-transfer-encoding:mime-version
:subject:to:from:dkim-signature:arc-authentication-results;
bh=Y7pVjQ5emAE4pdcubLwi7473vY3OWUVV5NusExrVNc8=;
b=DlgSuorHXVeVtWhKM/csFcSeADLzJCLSuzCwZEsHVT7XLtmwSQERCwlIDHyabl8Ffa
NNXx8CCYYfrAu0mbg3vGnAvG8SmusEwfBe0cAaa7D1bGf2fM/hGJzsQX21e3rbyQzvnu
GSTZjwpW48sFkWzN863wLai5Z2Ne+eR/7lyzfEO/mIIJL0f3uvVmV32kFYMWHxYz0x8/
r8GpiLqfD6nxMqvpxn04a/KYgo97/TxyB9AFaKEN08ih1d7+qLE5isq+BJI2NjCJLHnW
vqlM1ideeygoN20cgTaz6ZQpYOQAsO0SIZQkoOtkT/6eb0DNCEa1RO45AmMgC9ZJ4rkc
PYKQ== ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass header.i=#amazonses.com header.b=WNeDQXRK;
spf=pass (google.com: domain of 0100015cd2a93eb9-85164c9c-6cfb-46ec-a985-02909a4b6b0c-000000#amazonses.com
designates 54.240.9.109 as permitted sender)
smtp.mailfrom=0100015cd2a93eb9-85164c9c-6cfb-46ec-a985-02909a4b6b0c-000000#amazonses.com
Return-Path:
<0100015cd2a93eb9-85164c9c-6cfb-46ec-a985-02909a4b6b0c-000000#amazonses.com>
Received: from a9-109.smtp-out.amazonses.com
(a9-109.smtp-out.amazonses.com. [54.240.9.109])
by mx.google.com with ESMTPS id h186si1190862qkc.200.2017.06.22.18.55.26
for
(version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
Thu, 22 Jun 2017 18:55:26 -0700 (PDT) Received-SPF: pass (google.com: domain of
0100015cd2a93eb9-85164c9c-6cfb-46ec-a985-02909a4b6b0c-000000#amazonses.com
designates 54.240.9.109 as permitted sender) client-ip=54.240.9.109;
Authentication-Results: mx.google.com;
dkim=pass header.i=#amazonses.com header.b=WNeDQXRK;
spf=pass (google.com: domain of 0100015cd2a93eb9-85164c9c-6cfb-46ec-a985-02909a4b6b0c-000000#amazonses.com
designates 54.240.9.109 as permitted sender)
smtp.mailfrom=0100015cd2a93eb9-85164c9c-6cfb-46ec-a985-02909a4b6b0c-000000#amazonses.com
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1498182926;
h=From:To:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID:Date:Feedback-ID;
bh=VCZKg8hFUb63lOKDitSw+wHccKQ7iJdOqT+3v5T9kMM=;
b=WNeDQXRKVjREfsyiCHuwazQD7AXWRfZc3UcrwH1AghtaCnavxJ6CBSLTUsIqc5GF
m6/uRCDItr6crWjplYgl14Dq2mbGHMFtB+vZHh0PPNmO4n3+/8PevleQbEYInRWmlec
ZbFX57QHhrNXtEyUc4qaM3ZtjpcwjaPzOXe2liB8= From: No-Reply
To: rifaterdemsahin#gmail.com Subject:
Performance Warning(3x) IP: 192.168.30.40 Method:
Broadage.Common.Tools.Email MIME-Version: 1.0 Content-Type: text/html;
charset=UTF-8 Content-Transfer-Encoding: quoted-printable Message-ID:
<0100015cd2a93eb9-85164c9c-6cfb-46ec-a985-02909a4b6b0c-000000#email.amazonses.com>
Date: Fri, 23 Jun 2017 01:55:26 +0000 X-SES-Outgoing:
2017.06.23-54.240.9.109 Feedback-ID: 1.us-east-1.SIJlVA2xTbAVdBXctlUaxBDeEU1mquOgueuof7Nldbc=:AmazonSES
Performans Uyar=C4=B1s=C4=B1Mak= ine Ip =3D> 192.168.30.40Uygulama Ad=C4=B1 =3D> Method Name =3D> Broadage.Common= .Tools.Email=C4=B0stenilen Performans S=C3=BCresi =3D>
250 ms elapsed timeHarcanan S=C3=BCre=
=3D> 786.708 ms elapsed time
1) As pointed by Jordan Stewart, configure your filter to delete messages, but don't mark them as spam.
2) As complaint directly to the company did not work, I suggest complaining to AWS. See here https://aws.amazon.com/premiumsupport/knowledge-center/report-aws-abuse/
They seem to take abuse (or misuse) of their platform quite seriously. So, I would expect the company will be forced to either fix the issue or be disconnected from SES service.
I think your best option is to automatically delete the emails in the gmail, through setting up a filter. I think this page explains how to setup the filter: https://www.businessinsider.com.au/automatically-delete-unwanted-gmail-2014-1
I don't think you can interact with their setup of AWS SES. If you were able to it would be a security vulnerability of SES.
It could be possible to setup a gmail custom script that could delete the emails, but in affect it would be doing the same thing as the filter. Except the filter is easier.
I think the business sending unwanted information is probably against an anti-spam act. So what they are doing is probably illegal, or at least probably negligent.
I hope that helps.
From my understanding of AWS, this is an error that needs to be fixed from the company that is sending these emails. There is SES probation (http://docs.aws.amazon.com/ses/latest/DeveloperGuide/e-faq-sp.html). I would try emailing ses-enforcement#amazon.com and see if they can help you.
I tried to install ReadTheDocs on my linux server following the documentation: http://read-the-docs.readthedocs.io/en/latest/install.html
However I do not receive the activation email.
I was able to see the output of the email on the server
Hello from example.com!
You're receiving this e-mail because you or someone else has requested a password for your user account at example.com.
It can be safely ignored if you did not request a password reset. Click the link below to reset your password.
http://xxxxx:8080/accounts/password/reset/key/xxxxxxxxxx/
In case you forgot, your username is xxxxxxxxxxxx.
Thank you for using example.com!
example.com
note: This email is a password reset email, it has the same problem as the activation email. (I didn't receive any email from my ReadTheDocs installation)
There are two things that got my attention.
1. Where does read the docs configure the website name, I would like to change example.com to th real website name.
2. The sending adres currently is no-reply#readthedocs.org, where can I change it? I think its also a part of the issue.
Here are the other headers of the email
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Subject: [example.com] Password Reset E-mail
From: no-reply#readthedocs.org
To: xxx#xxxxx.nl
Date: Tue, 12 Jul 2016 11:30:49 -0000
So actually I have two questions
Where can I change the content of the email and things like the sender adres.
What happend with the email (why won't I receive it)
I know this is a longshot, but does anybody have any VFP (Visual FoxPro) samples of submitting credit card transactions to paypal pay flow pro API using NVP or SOAP? All of the samples from paypal are in C#, vb.net, etc.
Here's a sample of building an HTTP POST with VFP.
LOCAL loHttp
LOCAL lnSuccess
LOCAL loReq
LOCAL loResp
loHttp = CreateObject('Chilkat_9_5_0.Http')
* Any string unlocks the component for the 1st 30-days.
lnSuccess = loHttp.UnlockComponent("Anything for 30-day trial")
IF (lnSuccess <> 1) THEN
? loHttp.LastErrorText
RELEASE loHttp
CANCEL
ENDIF
loReq = CreateObject('Chilkat_9_5_0.HttpRequest')
* Add the request params expected by the server-side:
loReq.AddParam("city","Paris")
loReq.AddParam("country","France")
* Send the POST (This is a real URL that may be tested.)
loResp = loHttp.PostUrlEncoded("http://www.chilkatsoft.com/httpTest/cityCountry.asp",loReq)
IF (ISNULL(loResp)) THEN
? loHttp.LastErrorText
RELEASE loHttp
RELEASE loReq
CANCEL
ENDIF
RELEASE loResp
* The exact HTTP request sent and response received
* by the example code above is as follows:
/*
---- Sending ----
POST /httpTest/cityCountry.asp HTTP/1.1
Host: www.chilkatsoft.com
Content-Type: application/x-www-form-urlencoded
Content-Length: 25
city=Paris&country=France
---- Received ----
HTTP/1.1 200 OK
Date: Wed, 09 Dec 2009 16:16:00 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 156
Content-Type: text/html
Set-Cookie: ASPSESSIONIDQCDTSSAC=MHJCNFMDENFOKGINOFEDILCM; path=/
Cache-control: private
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
</head>
<body>
France<br />Paris<br />
</body>
</html>
*/
RELEASE loHttp
RELEASE loReq
You should be able to work from that and turn it into a call to PayPal. You just need to change the endpoint URL to PayPal's and then add all your parameters for whatever call you're making.
You can use PayPal's API Reference to see what parameters are available for any call you want to make.
Is it alright to send HTML-only emails without the text/plain part when doing HTML only actions like clicking a link to view replies or some other "alert" type notification? For example, clicking a link to activate your email or clicking to see new comments.
Date: Wed, 07 Mar 2012 10:30:54 -0800 (PST)
From: email#site.com
Subject: Test Mail
To: <email#site.com>
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64
VGhpcyBpcyBdfJDFKdjfkdsFpbCBmcm9tIGxvY2FsaG9zdCB3aXRoIGZzbdrb3BlbigpIGF0IDEz
eGVvbmNyb3NzLmNvbSI+eGVvbmNyb3NzLmNvbTwvYT4gPGk+bGluazwvaT4hPHA+VGhpcyBpcyBt
b3JlIHRleHQ8L3A+
Instead of using multipart to create two copies of the same email.
Date: Wed, 07 Mar 2012 10:30:54 -0800 (PST)
From: email#site.com
Subject: Test Mail
To: <email#site.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4f57a7d259baf"
--4f57a7d259baf
Content-Type: text/html; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: base64
VGhpcyBpcyBdfJDFKdjfkdsFpbCBmcm9tIGxvY2FsaG9zdCB3aXRoIGZzbdrb3BlbigpIGF0IDEz
eGVvbmNyb3NzLmNvbSI+eGVvbmNyb3NzLmNvbTwvYT4gPGk+bGluazwvaT4hPHA+VGhpcyBpcyBt
b3JlIHRleHQ8L3A+
--4f57a7d259baf
Content-Type: text/text; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: base64
VGhpcyBpcyBdfJDFKdjfkdsFpbCBmcm9tIGxvY2FsaG9zdCB3aXRoIGZzbdrb3BlbigpIGF0IDEz
MzExNDQ2NTgKCkFsc28gd2l0aCBhIGdvb2dsZS5jb20gdXJsIGFuZCB4ZW9uY3Jvc3MuY29tIGxp
bmshVGhpcyBpcyBtb3JlIHRleHQ=
I would like to save the bandwidth if there isn't a very good reason to include the text version.
If you're looking to save bandwidth, I don't think you should be using base64 encoding as it makes your data 33% larger (on average). In my understanding, text/plain (not text/text) should always be provided in a human-readable format (like quoted-printable).
I don't think there are many e-mail clients that can't read HTML nowadays, still I think your decision should reflect how important it is for the end-user to be able to read (and understand) your e-mail / alert and not (minor) bandwidth limitations. I've no experience with AOL, but I think it had some issues with e-mail links a few years ago, perhaps that counts as a bonus points for the plain text alternative.
Also, don't forget that the actual links need to be displayed in plain text versions.
I'm trying to send some html in a generated email that looks something like this:
X-Sender: XXXX#xxxx.com
X-Receiver: XXXX#xxxx.com
MIME-Version: 1.0
From: XXXXXXX#xxxx.com
To: XXXXX#xxxx.com
Date: 9 Dec 2010 10:55:52 -0800
Subject: Test email
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
<p>Click on the link below</p><p>Click Here</p>
The email sends but for some reason the link tag doesn't show up. I'm thinking it has something to do with the the content type. Any ideas? Thanks in advance.
You could try this Content-Type: "Content-Type: text/html; charset=ISO-8859-1\r\n"
It should allow your HTML to be handled properly.