Erol wrote:
> Hi,
>
> What should I do to setup LDAP objects on oes to setup a mail server?
>
> Thanks

Need some more information please:

OpenLDAP or eDirectory?
What kind of access do you want? (POP3, IMAP, Webmail)


For most mailservers, you don't need to do any fancy LDAP setup. I
usually recommend Postfix for the MTA (which comes by default on OES).
An MTA is the part that accepts the messages via SMTP and delivers the
mail locally (or reroutes it/rewrites it, postfix is very powerful). You
can also later integrate spamassassin and clamav (or your favorites) for
spam and antivirus filtering via amavis-new.

For mail retrieval, I usually go with Dovecot for POP3/IMAP access, and
IMP from the horde package (horde.org) for webmail.

Postfix can generally handle the local delivery for you (I recommend
Maildir format to home dirs if small scale, otherwise a dedicated
directory on a SAN-mounted disk or database storage to
MySQL/PostGre/Oracle).

On OES, assuming you're using eDirectory and not OpenLDAP, you really
don't need to touch the LDAP objects unless you have more than 65,000
individual users on a single machine. Just set up the users for Linux
User Management (LUM) and they'll show up as local users in PAM, and you
just set up the package as if you had created them all locally.

Let me know if you have a more specific reason why you need to use LDAP.

--
Justin Grote
Network Architect
JWG Networks

Erol wrote:
> Hi,
>
> What should I do to setup LDAP objects on oes to setup a mail server?
>
> Thanks

Need some more information please:

OpenLDAP or eDirectory?
What kind of access do you want? (POP3, IMAP, Webmail)


For most mailservers, you don't need to do any fancy LDAP setup. I
usually recommend Postfix for the MTA (which comes by default on OES).
An MTA is the part that accepts the messages via SMTP and delivers the
mail locally (or reroutes it/rewrites it, postfix is very powerful). You
can also later integrate spamassassin and clamav (or your favorites) for
spam and antivirus filtering via amavis-new.

For mail retrieval, I usually go with Dovecot for POP3/IMAP access, and
IMP from the horde package (horde.org) for webmail.

Postfix can generally handle the local delivery for you (I recommend
Maildir format to home dirs if small scale, otherwise a dedicated
directory on a SAN-mounted disk or database storage to
MySQL/PostGre/Oracle).

On OES, assuming you're using eDirectory and not OpenLDAP, you really
don't need to touch the LDAP objects unless you have more than 65,000
individual users on a single machine. Just set up the users for Linux
User Management (LUM) and they'll show up as local users in PAM, and you
just set up the package as if you had created them all locally.

Let me know if you have a more specific reason why you need to use LDAP.

--
Justin Grote
Network Architect
JWG Networks

Hi,

First of all thanks for the answer.. I have 2 sles based oes servers, I
have edirectory on one and I am trying to install a mail server to the other
one which will use the edirectory users. I have installed the
yast2-mail-server module to configure and when I try to use it, it says that
I need to run LDAP client module and enable the 'create default
configuration objects' option and Enable "LDAP Support Active" in the DNS
Server module. As far as I understand from your reply I don't need to
install yast2-mail-server module but how will I configure postfix with yast
then?

Thanks

Erol



"Justin Grote" <rastan@junkmail.com> wrote in message
news:OzJef.123$Pe3.87@prv-forum2.provo.novell.com...
> Erol wrote:
>> Hi,
>>
>> What should I do to setup LDAP objects on oes to setup a mail server?
>>
>> Thanks
>
> Need some more information please:
>
> OpenLDAP or eDirectory?
> What kind of access do you want? (POP3, IMAP, Webmail)
>
>
> For most mailservers, you don't need to do any fancy LDAP setup. I usually
> recommend Postfix for the MTA (which comes by default on OES). An MTA is
> the part that accepts the messages via SMTP and delivers the mail locally
> (or reroutes it/rewrites it, postfix is very powerful). You can also later
> integrate spamassassin and clamav (or your favorites) for spam and
> antivirus filtering via amavis-new.
>
> For mail retrieval, I usually go with Dovecot for POP3/IMAP access, and
> IMP from the horde package (horde.org) for webmail.
>
> Postfix can generally handle the local delivery for you (I recommend
> Maildir format to home dirs if small scale, otherwise a dedicated
> directory on a SAN-mounted disk or database storage to
> MySQL/PostGre/Oracle).
>
> On OES, assuming you're using eDirectory and not OpenLDAP, you really
> don't need to touch the LDAP objects unless you have more than 65,000
> individual users on a single machine. Just set up the users for Linux User
> Management (LUM) and they'll show up as local users in PAM, and you just
> set up the package as if you had created them all locally.
>
> Let me know if you have a more specific reason why you need to use LDAP.
>
> --
> Justin Grote
> Network Architect
> JWG Networks