cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
New

Suddenly can't send and receive after using own mx record

i created new domain for our company, setup all required a and mx record, but when sending a email via smary host, my email is being blocked by gmail and other domains. already check for blacklist, and my public ip is clean.

any idea.?

2 REPLIES 2
Super User III
Super User III

Re: Suddenly can't send and receive after using own mx record

@Napyo 

 

MX records control inbound email - You might want to check if you have an SPF record configured. Also you say you are being blocked - are you getting a bounce message and if so what is it saying?



I am a GoDaddy End User - Just Like You
Check out my site! | I currently manage over 300 WordPress Websites
* Please note that I offer free advice on this forum. If you would like personalized help, please contact me. Otherwise, please ask your question in the proper forum so the answer can assist EVERYONE in the community and not just you. Thanks! *

Once your issue is resolved,
please be sure to come back and click accept for the solution

Get Better Support on the Community Boards!
Etiquette When Asking for Help from the Community

New

Re: Suddenly can't send and receive after using own mx record

my spf entry is v=spf1 a mx ip4:210.5.88.228 ip4:119.93.93.105 include:_spf.google.com ~all

 

Bounced message i get from my yahoo account to my domain.

Sorry, we were unable to deliver your message to the following address.

 

<user@mydomain.com>:

Unable to deliver message after multiple retries, giving up.

 

--- Below this line is a copy of the message.

 

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1572973119; bh=DNamgKtqNN34Ci8tSn9IgrvmnPsLYuWBJTXHimyIYA4=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=HhZMdTMZZAqDylIuXa55NmNtqj9V5S+r8BAlav6+wAlny8JiU6y8ioMXmb3Cw67vAhpzQVHNQ2306sqE3LUrDOCua8rX135auU/qr5IxjjYmWVpzii6sPyapd5f2UuCdo9XsRpJqljzhrO8JZRSH/XxLZkmb37fulnCEcTPmY4ZZb26cuOVqcrR+ZzgV6/RyJ5Og733jbobqi2IhxNro1877Jhe5y3DLMt2/ASDHe1r7o+cuB02IirMpCh4oPm4N2AXVocCJIFe/GvIuzDB3PwVr5VdZW+PqvDRUJdbHCiagFtcH2C9xAO0kkE4nRSOH+ncmBpSiPeqXPJVzlwNjIA==

X-YMail-OSG:

Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.gq1.yahoo.com with HTTP; Tue, 5 Nov 2019 16:58:39 +0000

Date: Tue, 5 Nov 2019 13:51:04 +0000 (UTC)

From: user <user@yahoo.com>

Reply-To: "user@yahoo.com" <user@yahoo.com>

To: user <user@mydomain.com>

Message-ID: <640364065.1531299.1572961864401@mail.yahoo.com>

Subject: Hey

MIME-Version: 1.0

Content-Type: multipart/alternative;

    boundary="----=_Part_1531298_566628860.1572961864400"

References: <640364065.1531299.1572961864401.ref@mail.yahoo.com>

X-Mailer: WebService/1.1.14638 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.0.13; Android/9; PPR1.180610.011; a7y18lte; samsung; SM-A750GN; 5.76; 2094x1080;)

Content-Length: 638

------=_Part_1531298_566628860.1572961864400

Content-Type: text/plain; charset=UTF-8

Content-Transfer-Encoding: 7bit

Sent from Yahoo Mail on Android

------=_Part_1531298_566628860.1572961864400

Content-Type: text/html; charset=UTF-8

Content-Transfer-Encoding: 7bit