(still no access via Horde or client) Re: How to setup IMAPS and SMTPS in Kolab?

[Advrk Aplmrkt]

I still can't Horde to send or receive emails in my installation of
Kolab 2.3.2. I've copied my
/kolab/etc/kolab/templates/master.cf.template to pastbin here:

http://pastebin.com/nJXq5QpX

If anyone can help that would be great, thank you!

(BTW, like a said before I have turned off my firewall but I still get
connection refused errors...)

On 14 June 2011 12:54, Advrk Aplmrkt <avkaplmkt at gmail.com> wrote:
> OK.
>
> 1. I've disabled kolab from starting in runlevel 2 and runlevel 4 (it
> also appears in my rc4.d), by removing their scripts in their
> respective /etc/rc.d/rc#.d/ folders
>
> 2. I chown'ed /var/lib/postfix to user kolab and group kolab
>
> A few problems:
>
> 1. I can't find the files to change from your instructions:
>
> /etc/sysconfig SMTPD_listen_remote must be 'yes'
> /etc/sysconfig Postfix_smtp_tls_server and client both set to
>
> For me, /etc/sysconfig is a directory and not a config file
>
> 2. I still get the following error when trying send mail using the
> built in Horde web interface:
>
> "failed to connect to [hostname]:587 [SMTP: failed to connect socket:
> connection refused]..."
>
> 3. I tried the following per Alain's suggestion:
>
> telnet 127.0.0.1 463
> telnet 127.0.0.1 993
>
> Port 993 worked, while port 463 gave me a connection refused error.
> Same thing happens if I try to connect from outside my local network.
>
> Again, I completely disabled my firewall to make sure it is not the
> issue, and I am running Scientific Linux 6, which is literally RHEL 6
> rebranded.
>
> If any one can help that would be great. I really like to get Kolab up
> an running, with both fat client, mobile, and web interface access.
> Thanks.
>
> 2011/6/12 Nicholas Moore <nicholas.moore at tsr-i.com>:
>> I am now able to send webmail successfully. For Opensuse at least, there are
>> some some configuration settings that need to be changed for 2.3.2 (but not
>> 2.3.2):
>>
>> 1) ensure kolab does not start in runl;evel 2
>> 2) /var/lib/postfix owned by kolab
>> 3) /etc/sysconfig SMTPD_listen_remote must be 'yes'
>> 4) /etc/sysconfig Postfix_smtp_tls_server and client both set to 'yes'
>>
>> Note I made the changes to 3) and 4) at the same time so they may not all be
>> necessary.
>>
>> Now I can send webmail from 2.3.2, which is progress, and can go on to test
>> other things.
>>
>> Nicholas
>>
>>
>> On 12/06/11 14:10, Nicholas Moore wrote:
>>
>> I forgot to mention that the postfix log now reports:
>>
>> "<critical> postfix/master[19401]: fatal: open lock file
>> /var/lib/postfix/master.lock: cannot open file: Permission denied"
>>
>> Not sure why it is looking to /var/lib/postfix, I tried deleting the
>> master.lock but it still reports the same error.
>>
>> Nicholas
>>
>> On 12/06/11 10:42, Nicholas Moore wrote:
>>
>> I have been getting the same problem, but it appears to be related to 2.3.2
>>
>> In my recent tests I have used a 64 bit machine with OpenSuse 11.4, on a box
>> in my office and within my lan, so no internet access issues.
>>
>> 1) fresh install of 2.3.0     - tested message sends, using webmail     -
>> all ok.
>> 2) upgrade to 2.3.1          - tested message sends, using webmail     - all
>> ok
>> 3) upgrade to 2.3.2          - tested message sends, using webmail     -
>> FAIL - with:
>>
>> "Failed to connect to localhost:587 [SMTP: Failed to connect socket:
>> Connection refused (code: -1, response: )]"
>>
>> The only difference I have noticed so far, which may be peculiar to OpenSuse
>> is that kolab is configured to start in runlevels 2,3 and 5 whereas previous
>> versions were configured only for 3 and 5. This seemed to disable kolab on
>> startup, so I have removed the runlevel 2 start.
>>
>> I have had no response to previous requests for help with this error message
>> posted 8/6/11.
>>
>> Cheers
>>
>> Nicholas
>>
>> On 12/06/11 04:36, Advrk Aplmrkt wrote:
>>
>> I have been able to access "telnet [hostname] 993" from outside my
>> network (i.e. from through the Internet).
>> However, I got the "Connection refused" error when connecting to
>> "telnet [hostname] 463".
>> On the other hand, Horde can be accessed from outside the network as
>> well. I was able to create calendars and contacts, but still can't
>> send and receive emails. Specifically, I still get the following
>> error:
>>
>> "Failed to connect to localhost:587 [SMTP: Failed to connect socket:
>> Connection refused (code: -1, response: )]"
>>
>> Any more ideas what's wrong? Thanks for bearing with me. I really hope
>> to get Kolab up and running soon...
>>
>> On 5 June 2011 08:32, Alain Abbas <alain.abbas at libertech.fr> wrote:
>>
>> Hello
>> Just go in the Admin GUI and Check Imaps and smtps
>> you can test if the port is opened by :
>> Telnet 127.0.0.1 463
>> telnet 127.0.0.1 993
>> or with netstat -anp
>> you dont have to touch to template because Kolabd will do for you ( when
>> kolab Ldap object is changed) some
>> variable in kolab.globals are changed and the services are automaticly
>> restarted.
>>
>> you can test after that you external connection
>> outside your network
>> telnet myhostname 463
>> telnet myhostname 993
>> if the first in our kolab system answer and not this one it is a firewall
>> problem.
>>
>> Alain Abbas
>> Regards
>> Advrk Aplmrkt a écrit :
>>
>> I've successfully installed Kolab 2.3.2 on my Linux machine, and have
>> been able to access the admin page, create a user, and login to Horde.
>> Right now, I am using a dynamic DNS hostname from DynDNS that's linked
>> to the dynamic IP provided by my ISP.
>> I tried to setup a test Thunderbird client to connect to my Kolab
>> server. But I don't know how to correctly setup the server to accept
>> such connections (IMAPS and SMTPS), and what domain/hostname I should
>> specify in Thunderbird's settings?
>> So far I tried to setup IMAPS as [hostname] at port 993, but
>> Thunderbird couldn't make the connection. I also have no idea how to
>> setup SMTPS. (I checked my server's firewall, its port 993 is open,
>> but I don't know which to open for SMTPS, and how to enable it in
>> Kolab).
>> Any specific instructions would be great. Thank you.