Three block sending email using SMTP (TCP port 25) unless it is through their own server. Unfortunately I have found that with emails of more than a few kilobytes in size their SMTP server has a habit of dropping the connection. To work around this you can send to an SMTP server that listens on a different port. One way of doing this is through secure SMTP. If you have a Gmail account you can send email through Google’s server using your login credentials. Just bear in mind that Google’s server may rewrite the “reply to” address of the email to be your Gmail address, so be careful if trying to use this with another email address.
See http://mail.google.com/support/bin/answer.py?hl=en&answer=77689 for more info on configuring Outlook to use Gmail’s SMTP server.
I have been trying to reach a holy grail. Well, not a big holy grail and to some people this will seem silly, but I have been longing to be able to use VOIP in Linux and until I discovered SIP Communicator it wasn’t viable.
Ekiga the default VOIP soft phone in Ubuntu just doesn’t cut the mustard. It crashes is difficult to setup and just plain doesn’t work properly for me (I have a mobile broadband connection so jitter is an issue).
As for Twinkle I couldn’t even get it to work. Qutecom was the best soft phone I had used. It crashed a lot on start up, would crash sometimes in calls but at least it was easy to setup and worked up to a point. And then, while trying to help somebody on the Ubuntu forums, the poster, after tearing his hair out trying to find something that just works recommended SIP Communicator. I thought I would give it a try and it was and is a revelation.
Continue reading SIP Communicator the only show in town for VOIP in Linux
To get a more open source experience I changed from Chrome to Chromium for Linux. It left me without my bookmarks, etc. though. The user data for Chrome is stored in ~/.config/google-chrome. To get my data into Chromium I simple moved the files from there into ~/.config/chromium. Job done.