Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 197
  • Last Modified:

Send emails from website triggered as spam

We have a function in our website, this function allow users to forward emails to other users. The forwarded email should show that the sender email is the sender user, not ours.
Apparently, this is triggered as spam since the sender server is different then the email.. so wondering what is the best practice for us not to be caught as spam at the same time keep the sender email is the sender user.

Thanks for any idea or input
0
NevinsLtd
Asked:
NevinsLtd
  • 3
  • 2
1 Solution
 
ideazinfiniteCommented:
Do you have a mail server? If you send using that, then the mails are not marked spam.
0
 
NevinsLtdAuthor Commented:
I do and I'm using that mail server which is hosted 127.0.0.1
I tried relay it to our exchange on a different location. I'm able to send emails, however, still not sure if that will take us off SPAMCANNIBAL spam list.

0
 
ideazinfiniteCommented:
Try including the user's name next to the sender's email in the From field
0
Put Machine Learning to Work--Protect Your Clients

Machine learning means Smarter Cybersecurity™ Solutions.
As technology continues to advance, managing and analyzing massive data sets just can’t be accomplished by humans alone. It requires huge amounts of memory and storage, as well as the high-speed power of the cloud.

 
NevinsLtdAuthor Commented:
can you be more specific please
0
 
jar3817Commented:
"The forwarded email should show that the sender email is the sender user, not ours."

You're forging the FROM address on the email, this is most likely a factor in your messages being seen as spam. Many sites publish SPF records that explicitly list the servers allowed to send from a certain domain. When you rewrite the FROM address using one of these domains, your server isn't on the list so the message is seen as spam.

Also webhosting servers are often not setup correctly for sending email. Does the server have valid reverse DNS (PTR record)? Is this PTR record generic looking (1-2-3-4.static.isp.com) or something more custom like mail.domain.com? Is it announcing itself as a valid DNS name in the HELO stage? What's the return-path on the emails this server is sending out? Most webhosts will fail on this one setting the return-path to something like "apache@1-2-3-4.static.isp.com" when that isn't a valid email address. You need set the return-path to something valid, if not the same email address as the FROM header.
0
 
NevinsLtdAuthor Commented:
I think it's a reverse DNS issue. We have changed the PTR record yesterday and it shows in most places, except for SPAMCANNIBAL. I guess will give it another 24 hours and see if they are able to resolve it.

thanks for the input.

0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now