Email forwarding resulting in SPAM and bad headers - email

How can I circumvent spam errors when using a mail forwarder in cPanel?
I have a domain which I have configured an email forwarder to forward all emails sent to me#mydomain.com -> me#gmail.com so all my emails land in my Gmail Inbox.
I am receiving emails from trusted external sources but they are going to spam more often than not AND the email address in Gmail shows sender#senderdomain.com via mydomain.com
This also results in bad headers where it fails:
Failed: DMARC Compliant (No DMARC Record Found)
Ok: SPF Alignment
Failed: SPF Authenticated
Failed: DKIM Alignment
Failed: DKIM
Authenticated
I have contacted my server host but they dont know what is happening. Is there anyway to fix this or is there a recommended workaround?

Related

Spoof email online serivce: how it works? i.e. https://emkei.cz/

How do these online services of spoof email work?
They usually require the from domain really exists. It means there is a smtp server which accepts the connection.
Let's say I send a mail from test#xxx.com. The site will try to connect to the xxx.com smtp server and it will deliver the message.
The questions are:
How it is able to find the xxx.com domain smtp server?
To correctly deliver the message, xxx.com has to be without authentication. However, also with a fake gmail.com domain, the email is correctly sent, even though Gmail requires auth.

VestaCP/exim mail server returns 550 smtp auth requried

I have just installed VestaCP on a fresh CentOS VPS.
I have set up email for one domain. All mail sent to that domain bounces with the error 550 smtp auth requried
I have commented out the following;
deny message = smtp auth requried
from exim.conf
I have turned off anti-spam.
I still get the bounce with this message.
Specifically, if I send an email from a gmail account google responds:
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server for the recipient domain foobar.tld by mail.foobar.tld. [x.x.x.x].
The error that the other server returned was:
550 smtp auth requried
Any experience with this? I have seen the problem on a number of threads but have not found a solution.
I partially solved the problem. It only occurred when sending mail to the smtp server from a domain that was hosted on the same server for web but not for email. When I sent email from a domain that had nothing to do with any domains hosted on the same server as the exim instance, then it got through. I still can't send email from the domain that was causing the problem and I would like to, but I can work around it.
So to be clear in case anyone reads this:
domain1 web is hosted on server1
domain1 email is hosted on google's servers
domain2 is hosted on server1 for web and email
exim is running on server1
when I send email from thunderbird via google's server from email#domain1 to and email#domain2 the exim instance asks google's smtp server for authentication even though the mail is being delivered to a mailbox in its list of domains it can deliver to on the same physical server where it is running.
I suspect that it is suspicious of the from address, which it shouldn't be since the mx records indicate that it does not host mail for that domain.

DotNetNuke is not sending out mails using SMTP Server

I have configured my DNN mail server to send out mail using our companies Email service provider. I cannot send any emails to external email server.
For ex. My email provider is testx#ttt.com. I can send emails to testy#ttt.com and textz#ttt.com. However i cannot send to testy#gmail.com or testy#hotmail.com
The error i see in the DNN event viewer is as below
System.Net.Mail.SmtpFailedRecipientsException: Unable to send to all recipients.
System.Net.Mail.SmtpFailedRecipientException: Mailbox unavailable.
The server response was: This domain is not hosted here
I have the same email address configured in my outlook and i can send/recieve to any emails like gmail or hotmail. Following are my DNN email settings
It sounds like one or two things might be happening here:
Your SMTP server isn't set up to allow relaying from the IP address of your web server.
You may need to create an SPF (Sender Policy Framework) or TXT record in DNS for your SMTP server's primary domain that allows SMTP traffic from the IP address of the server where your DNN website is hosted. An SPF record may already be in use for your email domain, but generally you'd add something like this to it: v=spf1 a ip4:1.2.3.4 -all, where 1.2.3.4 is the IP address of your web server.

450 error when sending email through IIS, SMTP

One of our servers is running a website that sends out email addresses with
logins and passwords upon a user's registration. The email is configured with CDO. We seem to be getting blocked by some email services (see below). Is there a way to configure either rDNS, DNS, PTR, or SPF records to avoid getting bounce-backs?
Our company's public IP is x.x.x.195
The IIS server name is Server1a; private domain is private.com
The site it is sending from is public.com; public IP is x.x.x.140
We are getting bouncebacks from ATT, AOL, and other email services. Here is an
example of one:
Message delivery to the host '204.127.217.21' failed while delivering to the
remote domain 'att.net' for the following reason: An SMTP protocol error
occurred.
The SMTP verb which caused the error is 'MAIL'. The response from the remote
server is '450 service permits 2 unverifyable sending IPs - server1a.private.com
is not x.x.x.195
Problem was a greylisting due to higher requirements by Yahoo, AOL, and several other mail systems. The issue was fixed by updating the SPF record and creating a reverse-dns PTR record that would resolve to our server name.

Email error 503, how to solve?

I have problem sending emails, i checked the email sending error logs, and I found this:
RCPT RCPT TO:
503 This mail server requires authentication when attempting to send to a non-local e-mail address. Please check your mail client settings or contact your administrator to verify that the domain or address is defined for this server.
And this:
Sending unsolicited commercial or bulk e-mail to Microsoft's computer network is prohibited. Other restrictions are found at http://privacy.msn.com/Anti-spam/. Violations will result in use of equipment located in California and other states.
And following I dont understand what it means:
DATA DATA 354+Start+mail+input;+end+with+.
RCPT RCPT TO: 250 Requested mail action okay, completed
and some others...
This SMTP server requires authentication. Depending on your provider, you either need to specify username/password or, if your host uses POP-before-SMTP auth, you need to check your email first and that action adds you to an authenticated list for some time so you can send replies.
This error means you need to authenticate against your SMTP server before sending out emails.