I presume that would explain why my two attempts at submitting a problem ticket(not related to email issues) in Cerberus never showed up as open tickets. Are there other avenues by which to get support on other issues if Cerberus is affected by this email issue?
Thank you,
Gary Stadter
No its not - i received a similar error on 2 of my domains - one being MY business one.
Are you using DSPAM via the custom MX settings. If so, I recommend you delete them and wait for us to enable dspam globally, once we have this issue fixed
Testing is great - but how can you justify using the SUPPORT email/domain for testing ?? i was submitting a ticket - which did not go through…
This is happening very sporadically. Simply resending the email makes the issue disappear
i dont know what MX settings, but i made the changes a few weeks ago when we started testing it. In fact one of your support guys set them up for me - i didnt touch DNS settings.
so are you now saying that i must cancel this and STOP using Dspam ?
about spradically, and resending - i did in fact resend the email, and surprise surprise - it bounced back - again! at 3 AM last night (GMT+2) → so resending does NOT solve it.
and FYI, the said email is about ticket [RS #AKU-67314-245]: mail delays - which i am still waiting for a reply from support -for hours already.
Because you are using your helpdesk agent email to reply. We will not see them unless you change ticket status that is marked as dead. It is marked as dead because the first 2 posts on the ticket are just bounces from a postmaster email with no clues on what the actual issue is or if something is being reported.
Please always use a different email and create a ticket with [email protected], not your helpdesk.
That’s the problem… the MX record has already been globally assigned by Jodo. Each client and each domain have this setting. I have to go through each and every one to delete it and put a custom one in to bypass DSPAM.
If you want us to wait for you to enable dspam globally… shouldn’t you change ALL of the DNS records back yourself since you were able to turn it ON for everyone???
People still have all control they require. We have used dspam to extend the accuracy of our already available antispam system. If one doesnt wants to use our anti-spam system, they can simply turn it off in control panel.
Turning it off… you mean be deleting the MX record Jodo put there and then creating the custom one pointing to mail?.servicedomain.com? right?
If so that is my point. I did not turn this feature on. Jodo turned it on for everyone, but you are saying I can now turn it off due to problems. It probably should have been NOT enabled via DNS and given us the option to enable it so we could have tested it with a few of our accounts and NOT all of our customers.
If I am totally missing how this thing is enabled or disabled then please clear it up for me, but what I described above with the MX record is how I was told to disable it. And again, I didn’t have a choice in enabling it… it was just enabled for every client and every domain.
I think there is some confusion here then. I have a client that was getting the loopback issues and she did NOT have antispam turned on at the mailservices level. HOWEVER the account did have the new MX record Jodo changed a short while back.
I had asked this question in support “I need the instructions to COMPLETELY STOP DSPAM for a domain”. Her clients were getting bounce backs to them after sending mail to her giving the loopback error message. Support told me to remove the MX record and recreate it using mail?.servicedomain.com. They never mentioned simply turning off spam via the antispam setting you mentioned. BUT as I have stated she did not have the antispam setting on for her domain or mailboxes.
ok, its me who misunderstood then. Above instructions doesnt apply for her and support told you the correct steps. In this case the antispam gateway is just another hop for her mails. For mail bounce issue, i havent seen them in last 14 hours. This is why i’ve asked to talk to your client if they are seeing more bounces, because i probably have the issue resolved.
Ok… so what are your instructions suitable for correcting?
By doing those steps what does it accomplish in regards to DSPAM?
If it doesn’t stop DSPAM from processing mail what does it achieve?
Just trying to make sure I understand all the options now that DSPAM is in the picture.
I think the one thing I fully understand is if I want to take DSPAM OUT of the picture then do the MX change… but I want to make sure I know what your instructions achieve.
I had another client that got a bounce back to a client, but he had his anti-spam set to aggressive and remove which I believe why his client got the bounce back they received saying it looked like spam.
Not use DSPAM spam results.. You can do so by unchecking antispam in HSphere
Totally bypass DSPAM, use no anti-spam checking. Do this by changing MX records. Here, you will have no buffer incase the main mail server goes down. the dspam gateway queues emails.
I understand DSPAM had a serious issue, and some have lost faith. But I assure you we have put in alot of time and money into this, and we are going to make it a very capable anti-spam platform. We believe we isolated the loopback issue are are monitoring it
I personally am willing to give it a shake down, but there simply are clients that do NOT want the host providing anti-spam at all.
Now with option 1 above. Can you explain this a bit more?
What does it mean that it doesn’t use DSPAM results?
Does DSPAM not mark it with the word SPAM in the subject?
There is also a spam check level in HSPHERE… does this not have any effect now with DSPAM or does this set the DSPAM level.
I’m sure I am not the only one a bit confused with this… any additional information you could share to clearly lay out the full antispam solution at Jodo would be greatful!