Cloud Services Thread, Redirecting emails from old provider to Office 365 in Technical; The issue is that the LEA servers, when set to redirect, send the email on as if it has come ...
3rd July 2013, 03:17 PM #16
The issue is that the LEA servers, when set to redirect, send the email on as if it has come from the original sender. Making it easier to reply to, and looks neat in your new inbox.
So email from firstname.lastname@example.org sent to b@LEA.net is actually sent by LEA.net to email@example.com
So when school.uk (in this case office 365) checks who has sent the message it finds it came from the IP of the LEA server. When it checks the DNS record for abc.com, the spf record doesn't mention the LEA servers IP address, so it treats the mail as suspicious.
I'm not sure I've explained that very well though.
It's good to have an spf record on your domain anyway, but it's the original senders spf records you'd need to update to get this working, which of cause we can't.
Thanks to IrritableTech from:
themightymrp (3rd July 2013)
IDG Tech News
3rd July 2013, 04:01 PM #17
It makes sense what you've said.
I found this page : http://community.office365.com/en-us...ur-domain.aspx
Do you think if I get them to modify the spf TXT record I asked them to create initially to actually contain the below it might work??:
v=spf1 ip4:18.104.22.168 ip4:22.214.171.124 include:spf.protection.outlook.com -all
3rd July 2013, 04:25 PM #18
Sorry @themightymrp I fairly sure it won't. Its the original senders spf record that needs adapting (or the LEAs) not your school domains.
3rd July 2013, 04:34 PM #19
Says it all really
4th July 2013, 09:09 AM #20
Just another thought I had... You've got spare space on your old email account right?
4th July 2013, 09:23 AM #21
Hell yeah! I cleared it all out - downloaded to a PST. I have the full 450Mb (woooo) available.
I don't know if its going to be possible to do this. Do you know of any way to forward an email but keep the original senders email address in there for reply purposes?
4th July 2013, 09:44 AM #22
Just chiming in with my two cents...
Rather than trying to configure any fancy forwarding etc. (although still a valid approach), have you looked at connected accounts?
Learn About Connected Accounts
Users can hook up their old account from their new mailbox; might be quicker/simpler to configure given that this would be a short-term solution regardless?
4th July 2013, 10:00 AM #23
The perfect solution, however our LEA don't allow pop/imap. It's a security risk they say... Thanks anyway James.
Originally Posted by jamesbmarshall
4th July 2013, 10:07 AM #24
Yep, just checked that with their service desk Geez I can't wait until we're shut of them!! USELESS
4th July 2013, 10:51 AM #25
If it helps build an argument, traffic is secured regardless of which protocol you use with Office 365:
Originally Posted by IrritableTech
Settings for POP and IMAP access - Outlook - Office.com
If not, oh well!
4th July 2013, 10:55 AM #26
argue with lln you may as well beat you head against a wall its less painful
Originally Posted by jamesbmarshall
4th July 2013, 01:08 PM #27
I've given up on this as a bad job. But I have a reasonable alternative fix.
I have changed the rule from 'Redirect' to 'Forward as an attachment' followed by a 'delete message' command. They seem to come through fine onto 365 and you can open the attached message and see the original perfectly - with the added bonus of you can reply to the original sender!!
It will do for now. It is also a good indicator of who still needs telling about your change of address and what website subscriptions need updating.
Cheers for all of the help guys
By zag in forum Cloud Services
Last Post: 13th June 2013, 09:43 PM
By pknet in forum Cloud Services
Last Post: 25th May 2013, 08:51 PM
By techie08 in forum Cloud Services
Last Post: 11th October 2012, 02:57 PM
By tj2419 in forum Cloud Services
Last Post: 6th October 2012, 04:25 AM
By FN-GM in forum Windows
Last Post: 16th December 2007, 01:56 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)