One of our staff has got a Blackberry, thinking that it'd work 'out of the box' with our internal email system. It can browse the webmail interface fine, but of course it can't receive emails through the push email system on the unit.
I looked into setting up BES for hime (as it's free for 0-20 users). Of course, this requires an Exchange server, which we don't have. However, I found GMV Atlas which interfaces BES and Linux mail servers (we use Exim in a custom LEA provided configuration).
Unfortunately, Atlas does not work where IMAP uses SSL/TLS, it wants to connect on port 143 which is disabled.
I don't really want to give up on this one until I've exhausted my patience, as BES could be very handy for SLT in the future. Not massively keen on going for Exchange purely due to costs, but it's obviously the primary solution. Can anyone suggest a way of getting this to work? Either the required setting change on the email server (Slackware) to enable it to talk on 143 (not too worried about plaintext, as there's no off site mail access other than webmail, and all staff are set up with SSL anyway), or perhaps auto-forwarding the emails on to another server which I can connect to.
I'm not hugely familiar with the configuration for IMAP/Exim so I'm not sure if it's just a config file change, or a recompile job
It can pick up from IMAP through Atlas - but only through the (not enabled) port 143. It can only pick up POP3 through the web browser, and our county firewall doesn't allow pop3 and imap connections I believe.
Could you use an external server for Blackberry's service to connect to - have the external server pick up email from your internal system and make it available via IMAP?
1. Not sure what MS agreement you're on and what your budget is, but I'd go for the Exchange option, not only will you achieve you goal but the extra benefits you get will be a advantage over what you're using.
Also the Google Apps for Education should do this and comes with Blackberry admin control.
Don't know if google still allow you to use their mail servers as a grab and push service but I had that set up a few years back with the standard single user mail system. My ddns account would not let me send mail with standard ports from home mail server so I used google to fetch the mail and then grabbed the mail back out from google and into my other email server.
Your.domain that didn't go to a valid username would simply be dumped in the catch-all account. You can then use fetchmail or similar server-side to place your emails whereever you like - I use fetchmail at home to get emails from my ISP's account, place them in an IMAP server and read them from there with SquirrelMail as my web-based email client.
BES is horrible and I would rather set myself on fire than deal with it again. Avoid it if it is at all possible to. Set them up over IMAP and tell them to get a real device like a Nokia E series/Windows Phone 7/Android/iPhone if they want a decent experience.
A *BIG* warning about using random external servers to pick up emails from your in-house server to allow access to personal devices ... you then have *NO* control over the email, the contents and where it may go. You may end up in breach of DPA as well as introducing a risk to the school of misuse. As much as people will say that email is public, that is not always the case. User to User emails (eg Head to Bursar) is in house so when that spreadsheet of personnel data is being passed back and forward this is fine and secure ... but when it is pulled to an external box to allow it to be collected then you have no control.
Noted GD, I did think of this. However, this will happen using a Blackberry - with email totally inhouse, the BES still sends the data to RIM's servers which in turn send it to the device. There'll be an element of external connection here.
I have spoke to our LEA resident Linux guru. He has helped me install a second IMAP server on the email system which processes mail to port 143, so not touching the existing one on 993. Atlas can connect to this (though I'm not sure if imap idle is working). I'll report back on it.
I've not used BES yet to know how bad it is. There is a new version out - perhaps that's helped somewhat?
I have had to install and support one BES server through various versions and OSs, that idiot software is soul destroying, I was not kidding about the fire bit above. It is that bad.
Last edited by SYNACK; 11th May 2011 at 04:26 PM.
There's a number of benefits, dont know where to start. A simple one, redundacny. 2010 offer redundacny at the database level and hardware level. I've seen a few posts here where the school email server might go down. If you're school doesn't mind then fair enough, you can then use any free email system. WIth 2010 you can have multiple copies of your database across multiple servers, across multiple sites. Should a server failure occur, database failure or even a site failure, your email is still availalble.
There's a big performance improvement from 2003, in terms on IOPS, which leads to lower RPC latency and a better user experience.
You have transport rules which can be implemented, for e.g preventing staff of users sending out confidential information via email to their personal email accounts.
There are currently 1 users browsing this thread. (0 members and 1 guests)