Koozali.org: home of the SME Server

Allow external IMAP access

ukoda

Allow external IMAP access
« on: December 29, 2005, 12:28:13 PM »
Under version 6.5 it was easy to allow external IMAP mail access.  However in version 7.0beta2 it appears that you can only have secure IMAP access externally.  While this is fine as a default the system administrator need to make this choice.  In my case I have an unhappy customer who Blackberrys and phones can no longer access email since I 'upgraded' them.

Offline mrjhb3

  • *
  • 1,188
  • +0/-0
    • John Bennett Services
Allow external IMAP access
« Reply #1 on: January 02, 2006, 04:47:43 AM »
Instead of putting this here, you should file a bug report.  It's possbile that it is available by setting some db settings, but just not documented.

JB
......

ukoda

Bug reported
« Reply #2 on: January 02, 2006, 05:28:49 AM »
I have reported it as bug 389 so I guess I will see what they make of it.  I did get a step further by entering "config set imap service access public status enabled TCPPort 143" at the command line, but there is still problems.

Offline gordonr

  • *
  • 646
  • +0/-0
    • http://www.smeserver.com.au/
Re: Bug reported
« Reply #3 on: January 02, 2006, 10:38:09 AM »
Quote from: "ukoda"
I have reported it as bug 389 so I guess I will see what they make of it.  I did get a step further by entering "config set imap service access public status enabled TCPPort 143" at the command line, but there is still problems.

I've followed up to the bug with what you need to do. We made a deliberate decision to remove the non-SSL protected username/password services from the external interface. They are still there, but need to be enabled from the command line.

BTW: Beta2 is a *long* time ago - please upgrade to Beta9.
............

ukoda

Thanks
« Reply #4 on: January 02, 2006, 11:12:18 AM »
That solved my problems, thanks.  With this posting I guessing anyone else with same issue sould now be able to find a solution too :-)

Offline gordonr

  • *
  • 646
  • +0/-0
    • http://www.smeserver.com.au/
Re: Thanks
« Reply #5 on: January 02, 2006, 11:16:55 AM »
Quote from: "ukoda"
That solved my problems, thanks.  With this posting I guessing anyone else with same issue sould now be able to find a solution too :-)

Well, we need to decide what to do with the bug report. At the very least, the change in behaviour needs to be properly documented.
............

ukoda

Bug follow up
« Reply #6 on: January 02, 2006, 11:39:46 AM »
Do I need to do anything with the bug report or will that be handled by the admin?

I think the key is that people like me can find the info need to configure for issues like this.  I made a fair effort to check the documentation and forums sections of this site for the info I needed before posting here.

Offline gordonr

  • *
  • 646
  • +0/-0
    • http://www.smeserver.com.au/
Re: Bug follow up
« Reply #7 on: January 02, 2006, 11:55:10 AM »
Quote from: "ukoda"
Do I need to do anything with the bug report or will that be handled by the admin?

No - nothing for you to do. Thanks for the report and follow-up.
Quote from: "ukoda"

I think the key is that people like me can find the info need to configure for issues like this.  I made a fair effort to check the documentation and forums sections of this site for the info I needed before posting here.

Agreed. The information needs to make it into the FAQ when SME7 gets ready for release.
............