From time to time, our users will report that they are no longer able to receive e-mails from SingleOps, be it for their own registered users or for their customers who receive proposals and invoices by way of the SingleOps application.
Sometimes it's as simple as finding and correcting an incorrect e-mail address. But most often, we find that a user or customer of your service company has, at some earlier time, created what is referred to in the IT world as a suppression, i.e., they have taken some action to block, unsubscribe, or file a complaint against the SingleOps e-mail domain so that do not receive any further e-mails.
When this occurs, protocol dictates that we (SingleOps) can no longer send anything to this person - user or customer - because to do so would be considered 'spamming' the customer, i.e., sending them unwanted or unsolicited e-mails.
In order for e-mail communication to the person to continue, two things must occur:
• the user who requested the block/unsubscribe/complaint must first find the item which was marked as spam and remove it from his/her spam folder. If the item remains marked as spam, any/all future attempts from that e-mail address (or domain, depending on how the blacklist is determined) will cause it to fail;
• you must then notify SingleOps that the complaint has been removed so that we can remove the suppression from either our SingleOps 'do not send' list or from our third-party mail sender (or both)
Having us (SingleOps) perform the second step without first doing the first step will not resolve the issue, and will only trigger another suppression on our side.