canno't send from plesk webmail to Gmail " a simple mail" - gmail

after i change my hostname in plesk " there was a IP adress but now i cant change hostname to ip" i can't send email to gmail. on outlook works propperly and plus on info#mydomain.com i cant send to info#myclientdomain.com email but on gmail i can't pls help me i'm getting this error
This is the mail system at host server1.mydomain.ge.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<astronaut.georgia#gmail.com>: host
gmail-smtp-in.l.google.com[2a00:1450:400c:c08::1a] said: 550-5.7.1
[2a01:4f8:c2c:fe73::1] Our system has detected that this message does
550-5.7.1 not meet IPv6 sending guidelines regarding PTR records and
550-5.7.1 authentication. Please review 550-5.7.1
https://support.google.com/mail/?p=IPv6AuthError for more information 550
5.7.1 . k2si2790691wrg.299 - gsmtp (in reply to end of DATA command)
Reporting-MTA: dns; mydomain.com
X-Postfix-Queue-ID: 03B9E6257E
X-Postfix-Sender: rfc822; info#mydomain.com
Arrival-Date: Thu, 5 Nov 2020 20:26:02 +0100 (CET)
Final-Recipient: rfc822; astronaut.georgia#gmail.com
Original-Recipient: rfc822;astronaut.georgia#gmail.com
Action: failed
Status: 5.7.1
Remote-MTA: dns; gmail-smtp-in.l.google.com
Diagnostic-Code: smtp; 550-5.7.1 [2a01:4f8:c2c:fe73::1] Our system has detected
that this message does 550-5.7.1 not meet IPv6 sending guidelines regarding
PTR records and 550-5.7.1 authentication. Please review 550-5.7.1
https://support.google.com/mail/?p=IPv6AuthError for more information 550
5.7.1 . k2si2790691wrg.299 - gsmtp
გამგზავნი info#mydomain.com
ვის astronaut.georgia#gmail.com
თარიღი დღეს 23:26
qqq

Try to apply the solution from this KB article - https://support.plesk.com/hc/en-us/articles/213936285-Unable-to-send-an-email-to-Gmail-from-a-Plesk-server-Our-system-has-detected-that-this-message-does-not-meet-IPv6-sending-guidelines-regarding-PTR-records

Related

Connect to SMTP relay in Azure VM with O365 Account fails

How can I use from a VM (linux) where a Java application is running a SMTP Server/relay?
For connecting to SMTP I want to use an O365 account, so configuration looks like:
host: smtp.office365.com
port: 587
TLS: true
uid: UID-O365
pwd: PWD-O365
As response I get:
An error has occurred with sending the test email:
MailException: com.sun.mail.smtp.SMTPSendFailedException:
501 5.1.7 Invalid address [AM4P190MB0211.EURP190.PROD.OUTLOOK.COM]
;
nested exception is:
com.sun.mail.smtp.SMTPSenderFailedException: 501 5.1.7 Invalid address
[AM4P190MB0211.EURP190.PROD.OUTLOOK.COM]
remark: The application that wants to connect runs on java, what is probably unimportant
The server is telling you that the address "AM4P190MB0211.EURP190.PROD.OUTLOOK.COM" that you're using in your message as a sender or recipient address is not a valid email address. It at least needs a "#" in there somewhere. You can get more detail in the JavaMail debug output.
The solution is simple: sender email address (what was not listed above) and UID must be the same

Use nodejs EWS library sending email through Exchange Online is always considered as spam

I implement an Exchange web mail client using EWS with nodejs. When I tested it by sending an email from my PC to Local Exchange server, everything was fine. All test emails were sent successfully.
But when I deployed the project on Server (VPS on Digial Ocean) and connect to Exchange Online which is part of Office365 subscription (Free Trial). The problem occurs, all emails sent from my server were considered as spam, and cannot be sent to reciepients.
I also change hosting from Digital Ocean to AWS, the result is the same.
Any help would be appreciated
Thanks in advance,
This is Diagnostic information
Authentication-Results: #########.com; dkim=none (message not signed)
header.d=none;########.com; dmarc=none action=none
header.from=exzyoffice.onmicrosoft.com;
Received: from SG2PR01MB0361.apcprd01.prod.exchangelabs.com (10.161.11.156) by
SG2PR01MB0362.apcprd01.prod.exchangelabs.com (10.161.11.16) with Microsoft
SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.649.16; Tue, 4 Oct
2016 16:58:07 +0000
Received: from SG2PR01MB0361.apcprd01.prod.exchangelabs.com ([10.161.11.156])
by SG2PR01MB0361.apcprd01.prod.exchangelabs.com ([10.161.11.156]) with mapi
id 15.01.0649.022; Tue, 4 Oct 2016 16:58:07 +0000
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: ###### ######## <#################.onmicrosoft.com>
To: "chanyut##########.com" <chanyut#########.com>, "chanyutx10######.com"
<chanyutx10###########.com>
Subject: Check-in PIN for Test PIN Email - Meeting System
Thread-Topic: Check-in PIN for Test PIN Email - Meeting System
Thread-Index: AQHSHmB6uwXOpaeopUqgpi/eM7C6wA==
Date: Tue, 4 Oct 2016 16:58:06 +0000
Message-ID: <SG2PR01MB03614F6A8834FDB61C01DEF2FDC50#SG2PR01MB0361.apcprd01.prod.exchangelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <SG2PR01MB03614F6A8834FDB61C01DEF2FDC50#SG2PR01MB0361.apcprd01.prod.exchangelabs.com>
MIME-Version: 1.0
X-Originating-IP: [188.166.177.7]
Return-Path: chanthat#exzyoffice.onmicrosoft.com
X-MS-Office365-Filtering-Correlation-Id: 567de66e-0dff-4626-9fa1-08d3ec779d39
X-Microsoft-Exchange-Diagnostics:
1;SG2PR01MB0362;2:zy4eJMXvSbYZweZat1h/FneV4A2yOxpO8vpRdwEwCLWm8QipVnNdHzsBf+KyaetEsivdt7hl30XR0eCUs5T7EL7aar+e5fDuacG0fUm/7j7SH93besRmhZRaLZIup+pZYqzXKS6xnbd+kPd4Nf6gyMcfj0DL8ALLqSmf5b6aI7nuwiOIuO+z9Hw7XAD9vGMIZNSA64aw3BTeAxnxqqY1pw==;3:5BABxsk+E39PYBKVh9pWEKhIMBMLNKyOseakzwXuwPpHSiVt3bS8Ov+hYnw6Qs3Y0GMVQY0wlnaMopAEVphplwf5oy+oT5cLDIXzvg+q1GoAaeCu3TFALwH98FrKZr787qYEFnRV9pV0zqyocM+XBw==;25:ctGAmAQ1cu+BduByl6+MPAKb8/xsxaUIMq7FPDVqzTZDtsDLYREoYwbNlL10iTwrv0ON01j2DfmyRNvh6e6gL2Xcb/qjVqavMTzITJAVuBJlIHNiCgfpnW4mVNkb1dO4vJEZV6CI0KSk3RQH9Dh6/u56/zjv5ESEuuv9EQxcKYC8Mf0TJR+NHAr540/1+7h0yLDm2495YG46kfuJft6Y74HaYFiNVl/L3r31kA84l82qQez2sGGcgHo6kJv3w3QmB5garjK7j0HfceHEogOuofDJwz0Y47YfMaJg1/kyQhDGytMmQxrdJ2aRt8VcbjcKnF7Nfl3KbU/CkU33kZ9Vp3Fa9hustkf7lOD/bL1PsMSH2kOXmolb5ks1kvmF1hZ+pTsNzd0Zz9mNuErtxp7lK5hMfNL+NeLnAjnRZfvqX6/JK4ZRr7IlPw/YSvmMMxPM
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SG2PR01MB0362;
X-Microsoft-Exchange-Diagnostics:
1;SG2PR01MB0362;31:GR+rFHTjFRwfnJTe4nsRPGyP0mSyV+kDu/elZc5VaNeIXHm90HhmKo5Bzt08Yg9rKmPGkbTp2OVLPv8WIMt0ssqobSrA4ZGc44yBtlqefEAI18SF76/RrOxzmXDwUX82fkrubNc2e6IVrlDWQ0HO5cc1AYbatOZEwAfe3OzBg9rhw+u3ef8oBU5E++bzAqdqL0n/o+TrnEhy18ZJrL14yIhXEYsy159STM7O4Szj4pxh02al5tcE0CrpzdET9Wxo;4:0g+YEprdQNgkE9AkEVGWN/VFqIpOq92oDR1yeXN1yQeuGkHuWB6I9KIZSMLZHsjKildUXRPySE/Wv/r61w8hqbz0goIrlvYrEg+tCTDjM/0IsdxhXnGcsmgLIXAu4PRoTlkejJlaNqwtHqT217nzBDlCVu7E/4LwAPUpSk6+wQZhjAUfG/v3t3PNCHpL7hEsaK/KkqyKuJ+TbybDB5D+/JmqfQpzvxsP7pIOntHQmwbakW6g/I474q6I6x34yzVHOsA8tP/70Y6NbpA3P6hAOIh8ioFswLPAKbc/rO3q4pcAyARvVyXmNh6NeVntO1SaFUxqCn9OZSVWN3/pK3rVLDCHDkHisckt4VSGcN54vQcYR79Cod5jgMSjA2aMTtY8wPYf1ZxbU67WgCk9XJ8dpIceUZzF7cxZs78fr5kY7q9IMaYciZB7zR4v2Ds0pdmP36iITdLNHXdxOaqt3gY2g3oktTguQ87whqzg6+RJrO8=
X-Microsoft-Antispam-PRVS:
<SG2PR01MB036291996D70C36ABCD297ECFDC50#SG2PR01MB0362.apcprd01.prod.exchangelabs.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test:
BCL:0;PCL:0;RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6002118)(6000006)(6043046)(6042046);SRVR:SG2PR01MB0362;
X-Forefront-PRVS: 00851CA28B
X-Microsoft-Exchange-Diagnostics:
1;SG2PR01MB0362;23:SGkU+hCO1Me9ul5A85nokDETPc2fvnqIJBuMSsUaizPW5SU30hQ/9h8FERIrUfQlyhOSjKXtfJtRPa7dctubpraPm8t+7i1Tu9MmC3xqJss5m9gdTncr4lcByV677Os8wLvADH/SnogL/EucwxkzNm2M2WVwLpE2sOw9ochCbZuAMN2CQT+XKJnuSefgwHo8tfCdYWSEVRE3gleOfPWMTtYERp11xjY4NRCqU9WTcPLq6OMA+LIwdc8D0wpEPF++UgSfYeQ5Rd+SKnXW/++ZWw==;6:YwRMvgBmAN1rsxVOfmcL8JnjlX63xYoEQRiiRNoehWPk1+mB8M2XiRWLtmuHBVuOmi0CUeuQXuFWGEIS+Z1q8u0ARqjLoVkjHjTsZUMeiliHUg4bNAZfZdZNL2JRsp6zrdY+xNotdkzKO1+QN+yUV5USrfMLPo3eX8p/XAsvCB2MUikXyUyv9Lwpp71jzDsLExLz+AkKi2JKAxquPePw3OyzITh/BEpnxnRBVVAAKwOLg0cdxtcHNFiztVLcHSdqs6ygXQftAh+CbSqWlKLwkXitOLDdwbXVo2RYvT3DDC+8CYyoab8sRGihjxfbFw3M

How is another IP sending email through my qMail?

My first question on here...
I have a VPS which I have a few small websites on and also run my email services, every now and then I see messages in my mail queue that I did not send.
Firstly my setup:
Ubuntu 12.04
Latest Plesk Panel
qMail SMTP Server
Courier-imap
Using the Plesk panel I have set up qmail to not act as an open relay, and must use SMTP authentication to send to remote accounts, also short mailbox names are not allowed only the full account names.
Today I received bounced messages, upon checking my mail queue I have found again emails in there with multiple recipients that I have not sent.
These are not being sent by a script on my server as I would see different header information with uid 33 being specified, instead I see invoked from network in the mail header, an example below...
Received: (qmail 17710 invoked from network); 2 Feb 2016 11:34:10 +0000
Received: from unknown (HELO mx1.variationdesign.co.uk) (182.190.250.238)
by lvps212-67-205-193.vps.webfusion.co.uk with ESMTPA;
2 Feb 2016 11:34:09 +0000
From: Merel de Bruin - Van de Beek <seth#variationdesign.co.uk>
Content-Type: multipart/alternative;
boundary=Apple-Mail-29D34A60-FB4E-38B5-1BBF-7DDE23285FD2
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Subject: Re(4): Surprise
Message-Id: <91925fdeae7d$78ac5f73$dfad0a17$#variationdesign.co.uk>
Date: Mon, 2 Feb 2016 12:33:59 +0000
To: "sanderdejong" <sanderdejong#hotmail.com>,
"Sanne van Roon" <sannevanroon#hotmail.com>,
"Sarah Dormaar" <sarahdormaar#hotmail.com>,
"Sarah Tempelaar" <bordeaux84#hotmail.com>, "saskia middel" <s.middel#jvo.nl>,
"Saskia Roovers" <matrixspijkertje#hotmail.com>,
"sinta sinta ss" <sinta_sinta_ss#hotmail.com>,
"Sinta de Wildt" <sinta_de_wildt#hotmail.com>,
"skizonespijkertje" <skizonespijkertje#hotmail.com>,
"spijkertje matrix" <spijkertje_matrix#hotmail.com>,
"sroovers007" <sroovers007#hotmail.com>, "sroovers75" <sroovers75#hotmail.com>,
"stali n" <stali_n#hotmail.com>, "stingarts" <stingarts#hotmail.com>,
"suus rem" <suus_rem#post.com>, "svdbersselaar" <svdbersselaar#hotmail.com>,
"teresa villalobos" <teresavs#hotmail.com>, "teresavs" <teresavs#home.nl>,
"Thomas Bollen" <T.P.F.Bollen#students.uu.nl>
X-Mailer: iPad Mail (13A452)
X-PPP-Message-ID: <20160202113410.17689.25881#lvps212-67-205-193.vps.webfusion.co.uk>
X-PPP-Vhost: variationdesign.co.uk
The IP: 182.190.250.238 is nothing to do with me, I also never use mx1.variationdesign.co.uk.
Every time I want to send an email, I have to send my username and password to be able to send through this server.
My question is, how on earth is this person/people able to physically send emails through my VPS without authenticating?
I see in the logs around the same time "smtp_auth' for username seth#variationdesign.co.uk, which is odd because that is actually just an alias and not an email account, the account itself uses my full name and a couple of numbers at the end, I did this to try and stop spammers from guessing the correct username.
My server is definitely sending these emails out and I can't figure out how they are doing it, what ma I missing here?
I appreciate any help you can give me on this matter.
Kind regards
Seth
qMail SMTP Server comes with a default configuration to be a open relay, make sure you disable that and only authenticaed users can send emails. And stop your server before you get into a blacklist for spam.
https://qmail.jms1.net/relay.shtml

emails are sent to spam folder despite having DKIM and SPF set?

My emails are delivered to spam folder at gmail and yahoo mail.
PTR, DKIM (1024 bit), SPF are okay. I don't know whether DMARC and ADSP or Domain Key are needed to be configured or else?
In addition, I have checked Bulk Senders Guidelines "support.google.com/ ----> mail/answer/81126" but I think I am in compliance with it, except the Format section of the webpage. I wonder is my email header is ISO-8859-1 compliant as is requested by gmail or my messages are formatted according to RFC 5322 as it is required!?
However, I have checked my email by various tools including:
1- www.brandonchecketts.com/emailtest.php
2- mail-tester.com (my email score: 10/10)
3- toolbox.googleapps.com ----> /apps/messageheader/analyzeheader
and all of them are ok and I can't get it right why my emails are categorised as spam?
By the way, I am not a bulk sender, my ip is clean (not in any of blacklists) and I have just started to configure my new VPS host.
I am confused a bit as it is obvious, Please guide me.
Note: (I have changed email addresses and real IPs in the message header)
Here is the header:
Delivered-To: user#gmail.com
Received: by 10.194.95.197 with SMTP id dm5csp291965wjb;
Fri, 30 Jan 2015 06:02:17 -0800 (PST)
X-Received: by 10.180.206.147 with SMTP id lo19mr5212607wic.32.1422626536876;
Fri, 30 Jan 2015 06:02:16 -0800 (PST)
Return-Path: <user#myemail.com>
Received: from myemail.com (myemail.com. [97.195.90.210])
by mx.google.com with ESMTPS id s3si20803914wjx.75.2015.01.30.06.02.16
for <user#gmail.com>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 30 Jan 2015 06:02:16 -0800 (PST)
Received-SPF: pass (google.com: domain of user#myemail.com designates 97.195.90.210 as permitted sender) client-ip=97.195.90.210;
Authentication-Results: mx.google.com;
spf=pass (google.com: domain of user#myemail.com designates 97.195.90.210 as permitted sender) smtp.mail=user#myemail.com;
dkim=pass header.i=#myemail.com
Received: from webmail.myemail.com (localhost.localdomain [127.0.0.1])
by myemail.com (Postfix) with ESMTPA id 0D4A122FAEF
for <user#gmail.com>; Fri, 30 Jan 2015 15:02:14 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=myemail.com;
s=default; t=1422626535;
bh=mg3gRDZT3ck+E3FdH2X4LLdsZ/+WeZuit/DVefJiJWc=;
h=Date:From:To:Subject;
b=NhJPZML/OvA/2LJbvqKxnV7AO3TeGPdDqwBI+iOceZk2bz2flsCun3AqJ4RPY8pqM
is+dlQWTFCmQ2T2He7cKU/nC28FmPY4cqwJgt6oSIW0bIWkh81JdzBZXoIDiBGGlkx
mkrpvKQ4vdFh2R7iIRmUJMJtAGWr7MGoS/J7sdi0=
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 30 Jan 2015 17:32:14 +0330
From: user#myemail.com
To: user#gmail.com
Subject: Hello
Message-ID: <7582a20431ca444b255e5e835e6ee87d#myemail.com>
X-Sender: user#myemail.com
User-Agent: Roundcube Webmail/1.0.0
Regards
Since you've said that you've modified the header records, it's hard to determine a few things. However, the sending mail server seems to be webmail.domain.com --- Are the DNS records set to point to mail.domain.com or webmail.domain.com or both?
Since you've done the rest of the configuration: just enter a dmarc DNS record, it might increase your server's reputation. Speaking of reputation, if your email server only handles a few emails a day from a couple of users - then your reputation as a 'spammy' server can be greatly affected by a just a few unopened or manually spam marked messages. Also, I believe there's a time lag between when you setup a mail server and when it's reputation gets out of the 'default to spam' folder.

Google Apps Gmail SPF error

I moved one client to Google Apps and it's been crazy! So many problems! And I never had these kind of problems
Client is using Outlook with Imap to manage his Google Apps Gmail account
Now when he sends email he got this kind of errors (for some addresses only):
Delivery to the following recipient failed permanently:
spf-test#openspf.org
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.7.1 <spf-test#openspf.org>: Recipient address rejected: SPF Tests: Mail-From Result="pass": Mail From="nelson#samarfil.com" HELO name="mail-qa0-f45.google.com" HELO Result="none" Remote IP="209.85.216.45" (state 13).
----- Original message -----
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=samarfil.com; s=google;
h=mime-version:x-originating-ip:date:message-id:subject:from:to
:content-type;
bh=bjpej8F5vAhPQFF4gZXUvUHOGuDj2lURhN5uAXH+4o4=;
b=Gvhx7DYYlBFN1b0DQDDTq7Ll0tiGrrzMRGxVnIXOlbr8E3xhtY/lJGNcETSNDIblTT
yQHNyBlnPZxm2AqN8aeJ60lM54QofFtEt4jZe4V0b9WkP8rBXl5KbEfADcJw3kgZQMN/
8I0cpLYALe4YJ0PX8ZCXbtmFtd7m/Jmc/vKEo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:x-originating-ip:date:message-id:subject:from:to
:content-type:x-gm-message-state;
bh=bjpej8F5vAhPQFF4gZXUvUHOGuDj2lURhN5uAXH+4o4=;
b=fdNJWqcTEv1GE5giglb7CBRbU5+1w0VBF8DGjAN2YlrNH624no/00JcJgu/cyw7eAs
cIUUsU2vjMr7Kjjmc3xKbadMyF3A7b7u36l2t80aknCTdkSQuZ6yKT1EYY3INVUhue4Y
Ml7qNaSiAPhNEHlzEttJn/OFYgPeG0rSC8OM5MyZdY6gE64bqrDLH/3chq/0M+yHclon
hEYO7VytoV3BsNxr/HvEJEyNcHtTeX+WsVmxtNc5qgpxytbtReHEjl94auifz/YN16mg
wyC7LUXIBfF3Tffs0NIL5ITwQIj4rSKNm/4N20bfWa6uPJn/30J1uvVoRjHegDtwYQyK
yt8g==
MIME-Version: 1.0
Received: by 10.224.70.138 with SMTP id d10mr27073000qaj.12.1350404560884;
Tue, 16 Oct 2012 09:22:40 -0700 (PDT)
Received: by 10.49.24.205 with HTTP; Tue, 16 Oct 2012 09:22:40 -0700 (PDT)
X-Originating-IP: [94.133.34.4]
Date: Tue, 16 Oct 2012 17:22:40 +0100
Message-ID: <CACP3cFsLYGus9Sr-cbuEFezBEXhdzSJ6gqGPOJr___UJARaBMw#mail.gmail.com>
Subject:
From: Nelson Santos <nelson#samarfil.com>
To: spf-test#openspf.org
Content-Type: multipart/alternative; boundary=bcaec51a81ec2793fc04cc2f90aa
X-Gm-Message-State: ALoCoQkvxVOP+l0d4ugZSxBkKf6IBmd7UYEWPxtodPNh+L5hBOkQD2zREymT1Eal1lH9JUSgBavX
I've already configured DNS to TXT record v=spf1 include:_spf.google.com ~all
what else can I do to fix this?
It's normal to receive this message, as that SPF test uses the error message to send back results. Are you experiencing errors when sending to other addresses?

Resources