Page 1 of 1
ALL HESK emails are detected as SPAM and don't reach custome
Posted: Fri Apr 23, 2010 2:01 pm
by FrenchMaster
Script URL:
Version of script: 2.1
Hosting company:
URL of phpinfo.php:
URL of session_test.php:
What terms did you try when SEARCHING for a solution:
Write your message below:
Hello !
we have massive problems since using Hesk : our customers don't get our emails ! they are all landing in customers spam-directories.
sending "per hand" like we did befor = no problem. butt almost ALL emails sended through HESK are recognised as SPAM
how to solve the problem ?
Posted: Fri Apr 23, 2010 3:25 pm
by Klemen
I remember someone having such problems before with a translated version. Are you using English language or some other? If it's a translated version you should translate the email files (inside language folder) again and make sure you don't enter any words inside that would trigger spam filters.
Also make sure the "Noreply" e-mail in the settings is a valid and existing e-mail address. I would recommend having it @yourdomain.com where yourdomain.com is the domain where Hesk is hosted.
Posted: Tue Jun 15, 2010 7:30 am
by DigiMon
I just wanted to chime in with a comment and say that I've been using "licensed" Hesk for a couple years now, and I didn't start experiencing this problem until I just upgraded from 2.1 to 2.2
I'm using the standard default "English" language file with no added translation files.
I submitted a test ticket tonight from my spare Gmail account after upgrading to 2.2 and Google is putting the automated replies into the Spam folder and giving the scary warning that "this message may not be from who it says it's from" which these days is enough to scare any user away from going any further or clicking links in the email.
I have used the Hesk FAQ / KnowledgeBase and this forum to research any possible things I should check and everything seems to check out OK with my Hesk. I've also made sure that my "NoReply" address is an email address configured on the same domain (albeit, a forwarder) as my Hesk.
I realize this post doesn't help much but I just wanted to confirm that this is happening on a Hesk that I've been using for quite sometime within which the issue never occurred before upgrading to 2.2
Guess I'll toy with the wording in the /language/en/emails/ files to see if it helps...