For GDPR compliance we have been using the email client feature, to ask our customers their permission to keep them in our database. Because of the format of the email and need for them to click on a link, some of our customers are reluctant to do it or have treated it as spam. This led to us, in one case, to getting blacklisted.
Have you a solution pending for this very important issue?
Hi @Melonline
I just want to confirm what emails you’re referring to here if that’s OK?
Am I right in thinking that these are the emails that are sent if you send an internal message to a client? What’s your current email setup - do you use the default QuickFile set up, or your own SMTP service?
It’s the default as I had problems using my service.
What was actually blacklisted in this case?
The default setting sends emails from a QuickFile email address and adds a ‘reply-to’ header, so any replies to the email itself are sent back to you (otherwise they come back to a non-existent inbox).
Some mail servers don’t like the reply-to header which can cause some issues. However, there are 2 options:
-
Set your reply to the same as our sending address. This does mean that your clients won’t be able to reply directly to your emails however.
-
Use your own SMTP Server.
The second option (the SMTP server) will be the better option as this still allows you to receive emails. What issues did you experience when you tried to set this up last time?
Hi!
Image Removed
Here is the message I get!
Thanks! I’ve removed the image from the public forum, but I have a copy for reference while dealing with this for you.
I ran a quick test and an error was returned:
The remote certificate is invalid according to the validation procedure.
I notice you’re using a custom SMTP address (smtp.your-domain.com); if this sits on top of another mail server, the SSL certificate could be set up as the primary domain rather than the one for your domain.
Do you have access to a generic one that your hosting provider has, like smtp.generic-domain.com?
[Edit]
I’ve just done a big more digging into this. Could you try the following as the SMTP server please?
Hi Mathew, I have changed the server setting. I got a thumbs up but the error message is still underneath, is it OK now?
I’m seeing a different error now:
The server response was: 5.7.1 : Relay access denied
This does appear to be on the mail server end however rather than QFs end. We can successfully connect, but the mail server is rejecting the request to send an email.
You may want to raise a support ticket with them, quoting the error above, and see if they can shed any light on it.
Here is the response.
There are couple of reasons for this error while sending an email, most commonly is when a user has not checked the option “Our server requires authentication” option while setting up the account. It is worth checking if the option “Our server requires authentication” while configuring the account is checked (or equivalent).
Alternatively you can try the following settings:
Hostname: us3.smtp.mailhostbox.com
Port: you can try either 25, 465 or 587
SSL/TLS: Enabled
STARTTLS: Disabled
There are no blocks or restrictions on your account that would prevent such a connection so it is just a case of getting the settings correct.
Best
This topic was automatically closed after 7 days. New replies are no longer allowed.