Messages

1

Installation and Upgrades / Re: File Share - With no user / password

« on: June 16, 2010, 03:30:55 pm »

I've seen that the latest 1.5.2 version of the ebox-samba module includes this feature from the web interface, but I cannot access the resulting share both guest and authenticated, the generated smb.conf section is this one:

Code: [Select]

[public]
 comment = public area
 path = /var/lib/samba/public
 guest only = yes
 guest ok = yes
 read only = No
 browseable = Yes
 force create mode = 0660
 force directory mode = 0660
 vfs objects = full_audit

2

Installation and Upgrades / best practices for hooks, stubs and templates

« on: March 23, 2010, 03:45:09 pm »

Hi, I've been doing some customizations on my eBox 1.4 install to setup the webmail on SSL with certificate authentication and more ideas to come next.

Currently what I'm doing is modifying directly the mason templates under /usr/share/ebox/stubs/ after making a backup of each, even if I now this is not a good practice as any update on the ebox modules affected could overwrite them as stated in the documentation at:
  http://doc.ebox-platform.com/en/develop.html#service-advanced-customization

Anyway, what could be a better approach using hooks? Should I backup and overwrite the files in /usr/share/ebox/stubs with my custom version at each module start in the preservice and postservice scripts or is there a better way?

Thanks for any suggestion.
  Marcello

3

Installation and Upgrades / Re: Creating a secure, https, 443, virtual host with the webserver

« on: March 22, 2010, 06:19:43 pm »

Is the implementation of this already available on SVN in trunk or some branch?
I've been trying to find it there but without success

Currently I have a working implementation of the stubs which at least avoids the warning and let me add a working SSL configuration in a custom default-ssl site even without any connection to the admin UI, if it can be useful I would be happy to contribute it

--m

4

Installation and Upgrades / Re: SMTP Authentication

« on: March 15, 2010, 08:10:14 pm »

solved also for me, it wasn't eBox fault but a problem in the CISCO firewall ahead of it:
  http://tomas.cat/blog/en/how-solve-smtp-auth-errors-postfix-or-any-other-mailserver-behind-cisco-pix-firewall
anyway I think the 25 port would be enough for both plain and TLS using STARTTLS as the output using telnet is exactly the same both using 25 and 465 port:

Code: [Select]

220 eBox ESMTP
EHLO client.example.com
250-mail.example.com
250-PIPELINING
250-SIZE 20971520
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN


5

Installation and Upgrades / Re: egroupware multiple virtual domains configuration

« on: March 13, 2010, 01:29:46 am »

I would also like to know about the solution you've found, especially if it was customizing eBox or going through another route. In eBox 1.4 I have virtual domains only for e-mail, not for users which share the same OU=Users in LDAP, so they must have a unique username, instead of being unique only in the context of a single virtual domain. I think it would be easy to enhance the system providing  OU subtrees under LDAP per virtual domain, I don't know if this creates problems with PDC, maybe this should be filed as an enhancement

6

Installation and Upgrades / Re: How to setup ebox with a different DC in ldap

« on: March 13, 2010, 12:44:14 am »

I installed eBox 1.4 and I got an LDAP base DN automatically derived from the fully qualified hostname which I would like to change.

By looking at the templates I can see that there is a $ldapBase variable for it, but I cannot understand where can I change it. I don't know if this should be files as an enhancement request, it would be useful to be able to change from the web ui in the System/General section

7

Installation and Upgrades / Re: Creating a secure, https, 443, virtual host with the webserver

« on: March 10, 2010, 07:42:13 pm »

Even with my working setup, I get warnings about "NameVirtualHost *:0 has no VirtualHosts." However, it all works with the warnings. They only exist because ebox creates VirtualHost definitions without the :PORT. I kind of get why they don't. As it stands now, if you change the ebox port, it just changes /etc/apache2/ports.conf. If they added the :PORT to all the virtual hosts, they'd have to regenerate all of the virtual host files, too. Although, it's done by a computer so how long could it take? 50ms? a whole second?

Also, I did get that same error that you're reporting while testing. I'm trying to remember the cause. Maybe you could post your configuration? I think it had to do with a misunderstanding on my part of how to use NameVirtualHost and VirtualHost.

In my last Ubuntu Server install I have the NameVirtualHost statements inside ports.conf specifying a port explicitly and I don't get that warning anymore, I guess it's the correct config that eBox should generate as the comment from Debian README states.

Code: [Select]

# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default
# This is also true if you have upgraded from before 2.2.9-3 (i.e. from
# Debian etch). See /usr/share/doc/apache2.2-common/NEWS.Debian.gz and
# README.Debian.gz

NameVirtualHost *:80
Listen 80

<IfModule mod_ssl.c>
    NameVirtualHost *:443
    Listen 443
</IfModule>

8

Installation and Upgrades / Re: SMTP Authentication

« on: March 09, 2010, 05:23:31 pm »

I am trying with Mail.app but without any success, I can only connect without authentication and send to addresses within the same domain, but anyway my internet gateway only allows port 25 in.
Requiring TLS means I need to open other ports from the internet besides 25? As far as I know it be possible to negotiate if plain or TLS and stay on the same port.
As an alternative would it be possible to have authentication without TLS and how?

thanks for any info