We would like to make a remote session with you to test TLS Auth and get the logs related with the problem. But, we would like to be sure that you will not be affected on our tests. That’s why; I have asked our development team to develop a script that we will be used during our session with you. The script will enable us send your emails later if we face any problem during our tests…
We will contact with you as soon as our scripts are developed and ready.
@dittoit the IP change should not make any difference to your email sending if it is configured correctly.
If configured correctly the ServiceDesk (SD) platform should be logging into your email using SMTP on port 587, so the IP is not important else you would never be able to use SMTP, OWA or RPC to access email without configuring the platform for each external IP you use.
With regards to SPF records, SD should not be listed at all as it is a client, only servers should be listed in the SPF record.
@StrobeTech I’m not using authentication, I’m sending directly to my MX record, I add the “from” IP so Office 365 allows the relay. I add the IP to my SPF as an authenticated sender.
This works perfectly until they start changing settings.
I see what you are doing; not the best way to have it setup and can cause the platform to be listed as a bad sender by MS meaning authenticated emails will be relayed out via HRDP and be caught in spam due to being on RBL lists.
the issues with Spam are down to the source (C1 platform) looking like it is a spammer which could be caused by people trying to use port 25 with it.
Because the source looks like a spammer MS sends the email to be delivered by the HRDP (MS bad outgoing email pool) instead of the safe pool. As it is the bad pool 99% of RBL lists have the IPs listed.
So the issue is not Comodo being blacklisted, but MS being blacklisted.
Comodo looks like spam so MS routes the message out via the spammy pool instead of the clean pool to make sure our normal connections on Outlook etc are not blacklisted.
Getting the Auth to work is easy, and I used to do this with the non-Comodo customised osTicket product; but at the moment we have special routing put in place for our spam filter to hide Comodo and route it differently.
We are developing a code to add fall-back mechanism to not cause any problem at your side while trying our solution. Nevertheless, we focused on our major release to be deployed this weekend. After the release, we will focus on this. Thank you for your patience.