Jump to content

Recommended Posts

Posted
Yep, same problem here, no outbound mail. I looked at MailMarshall and the last outbound email to reach MailMarshall was at around 7:30 last night. I just logged a call with Capita and the lady on the helpdesk claimed it was a DNS issue with KCOM. She said they're looking into it.

 

Just called them back to chase this up. Spoke to someone else who transferred me to KCOM. They said they'll look into it.

 

Is anyone else having the same problems, surely it's not just the three of us that have mentioned it in this thread?

Posted
Just called them back to chase this up. Spoke to someone else who transferred me to KCOM. They said they'll look into it.

 

Is anyone else having the same problems, surely it's not just the three of us that have mentioned it in this thread?

Starting to get a bit annoyed now, nobody seems to know who is doing what! I've logged it with KCOM and Capita but no updates on either, really, other than they're working on it. I kind of thought they'd have a little more information available by now since they've been working on this since about 9am this morning.

Posted
Starting to get a bit annoyed now, nobody seems to know who is doing what! I've logged it with KCOM and Capita but no updates on either, really, other than they're working on it. I kind of thought they'd have a little more information available by now since they've been working on this since about 9am this morning.

 

Yeah I got the impression that neither really knew who was doing what. The Capita support seemed OK but with KCOM I spent ages explaining that my Exchange server couldn't ping or telnet the openhive relay and that it seems like it could be a DNS issue and the lady told me she didn't really know what any of that meant and asked me for the username of the email address that couldn't send! I then explained that we'd got our own server and it was affecting everyone and she still seemed confused.

 

I'm wondering how many people have actually noticed it's happening, with it being half term. I only noticed because a colleague happened to try to email his personal email address. Luckily there's been hardly anyone using email all day.

 

I'm assuming seeing as all the emails are sat on my Exchange server that when it does get fixed they'll all go through.

Posted

They should start to send, yes, although at which point they fail and get removed I'm not entirely sure. Probably depends on your setup.

 

We're not on half term here, and it's just stupid now. Surely it can't be that difficult to fix? I know those who chose the RM offering (supplied by KCOM directly) aren't having this issue... what a suprise.

Posted

They should start to send, yes, although at which point they fail and get removed I'm not entirely sure. Probably depends on your setup.

 

We're not on half term here, and it's just stupid now. Surely it can't be that difficult to fix? I know those who chose the RM offering (supplied by KCOM directly) aren't having this issue... what a suprise.

 

I wonder where we stand in terms in SLA because technically the service is working, it's just not accessible to us on emPSN.

Posted

Weve stuck with kcom for internet but are running all services ourselves (already ran most of them anyway). Noticed the dns (dns resolver, not the domain name host)had gone down last night for all websites (the old embc dns, havent seen any info if theres a new one) so changed to googles (8.8.8.8 and 8.8.4.4) and all was well (we go direct rather then through a proxy now).

 

At the moment we seem to have the opposite problem then everyone else, we can send email but not recieve it (waiting for firewall change request to go through).

Posted

There are a few things I would address in this response but rather than take it further OT I'll comment on one and ask that we take the rest to email and / or a separate thread.

My personal opinion on it is that I'm particularly unhappy about the LEA's lack of involvement. They have literally (although with plenty of time) issued a cut off date for their entire or partial funding, and determined that the schools are on their own without so much of a "If you're not sure what this means for you, please feel free to contact person X" Of course it's not entirely blameless, so many institutions would have ignored warnings when they came or didn't follow through to their relevant staff/contractors with "What do we do?". There was a late webpage put up this summer of course - but that information should have perhaps been there the very minute that these changes were agreed.

 

On pretty much all the LA communications about the changes, we have provided contact details for the team should schools wish to discuss things with us. We have made regular updates (monthly) via the Schools Factsheet, updates via the website and direct letters to schools. Many schools have contacted us, on an individual or cluster basis, and many schools have chosen not to, because they have stated that they have the relevant knowledge or expertise available to them (in-house, contracted in or via their new providers). We know that the ability to manage this will vary from school to school, but it has been made very clear from DfE advice that the responsibilty of this belongs to the school.

 

We are, as always, open to discussions with schools, their support providers and their service providers (as we have been previously) about any remaining issues.

 

All parties within the emPSN framework are in direct contact with one another and I know that emPSN staff, KCom and Capita are working on the present issue.

Posted (edited)

Just realised what I suggested wouldn't work. So really it is a waiting game!

 

Edit: Progress is being made though as an NSLOOKUP now works for Capita inthehive.net addresses.

Edited by Edu-IT
Posted

Mine still isn't working. I can telnet the relay but my connector is now showing as "The remote SMTP service rejected AUTH negotiation" which suggests it's now an authorisation problem. I'm using the username and password they emailed me though. Looks like another phonecall first thing.

 

Any chance anyone can check their connector and see if it's saying the same?

 

I've noticed incoming mail is very slow too, just emailed myself from home and it took 15 mins.

Posted

Have you tried sending out an email? I'm getting exchange bouncing back messages saying:

 

mx01.inthehive.net #550 Rule imposed mailbox access for [email protected] refused ##

 

The following organisation rejected your message: mx01.inthehive.net

 

So now it looks to be the MailMarshal side, not KCOM.

 

Are you sending with TLS or just basic? I had to disable TLS for it to even try to send.

Posted
I'm not getting anything bouncing back at all. I've not got TLS turned on and basic authentication (as it said in the setup instructions). All the messages are sat on the server queued up. Even tried setting up a brand new connector and that doesn't work either.
Posted
I'm not getting anything bouncing back at all. I've not got TLS turned on and basic authentication (as it said in the setup instructions). All the messages are sat on the server queued up. Even tried setting up a brand new connector and that doesn't work either.

My instructions said to use TLS. Which Exchange version?

 

Incoming mail seems fine, arrived instantly.

Posted
That's strange. I'm not getting anything bouncing back, I think my issue is with the authentication. Does your connector show as "active"/"ready" or "retry"?
Posted
That's strange. I'm not getting anything bouncing back, I think my issue is with the authentication. Does your connector show as "active"/"ready" or "retry"?

Where are you viewing that, sorry? Is it in queue viewer?

Posted

Yeah I've got 34 just sitting there. Looks like yours is connecting to the relay but mine isn't. If I force it, it goes active for a few seconds when it's presumably trying to authenticate and then fails.

 

Incidentally, earlier on in the additional information bit it said it couldn't resolve the relay in DNS, so that's fixed now.

Posted
Yes I tried it earlier with it on. I just tried it again though to check what it says in the additional info bit and it actually says "The remote SMTP service does not support TLS".
Posted
Well, good luck tomorrow, and be sure to keep us posted! Drop me a PM if you prefer to discuss it off forum but it'd be good to at least know how one another are getting on.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...