Re: RE; Migration Assistance

Hi David,

Actually, the output of the ldapsearch specifying '(objectClass=*)' pulled
everything needed.

Everything on the new server works nicely with the exception of SASL
authentication for Postfix.  This prevents me from sending mail with
authentication.  I can use squirrelmail because I have configured
squirrelmail to use the local postfix binary rather than an SMTP
connection to the server.

SASL is set up to use LDAP as an auth mechanism, and my saslauthd.conf has:

ldap_servers: ldap://127.0.0.1
ldap_port: 389
ldap_search_base: o=hosting,dc=example,dc=com
ldap_filter:
(&(objectClass=JammMailAccount)(mail=%u)(accountActive=TRUE)(delete=FALSE))

my smtpd.conf for SASL has:

pwcheck_method: saslauthd
#mech_list: AUTH LOGIN PLAIN DIGEST-MD5
mech_list: LOGIN AUTH

my main.cf for postfix has:

# SASL support start new
smtpd_sasl_auth_enable = yes
smtpd_sasl_local_domain =
smtpd_recipient_restrictions = permit_mynetworks,
permit_sasl_authenticated, check_relay_domains, reject_unauth_destination
smtpd_sasl_security_options = noanonymous
smtp_sasl_auth_enable = no
# end sasl new


The following works fine:

testsaslauthd -u <email> -p <passwd>


However, attempting to authenticate when sending mail via smtp, my logs
reports "SASL LOGIN authentication failed:

Aug 17 11:20:17 myhost postfix/smtpd[12866]: connect from
remote.host.com[1.1.1.1]
Aug 17 11:20:17 myhost postfix/smtpd[12866]: setting up TLS connection
from remote.host.com[1.1.1.1]
Aug 17 11:20:18 myhost postfix/smtpd[12866]: TLS connection established
from remote.host.com[1.1.1.1]: TLS
v1 with cipher RC4-SHA (128/128 bits)
Aug 17 11:20:18 myhost postfix/smtpd[12866]: warning:
remote.host.com[1.1.1.1]: SASL LOGIN authentication failed
Aug 17 11:20:18 myhost postfix/smtpd[12866]: lost connection after AUTH
from remote.host.com[1.1.1.1]
Aug 17 11:20:18 myhost postfix/smtpd[12866]: disconnect from
remote.host.com[1.1.1.1]

Any idea what I may have missed?

Thanks,
Yash

> You should be able to export your old ldap tree by running slapcat as
> root on the old machine and writing it to a text file:
> #slapcat > tree.ldif
>
> check the man page for slapcat to be sure, but it basically spits out
> all the ldif entries for your ldap setup.  You can then move this file
> to your new machine.
>
> I think you can then import them to the new machine with ldapadd, again
> check the man page.
> _________________________________________
> David Greenberg, M.Ed.
> Director of Technology
> Mohawk Trail Regional School District
> 24 Ashfield Rd.
> Shelburne Falls, MA 01370
> Ph.: 413.625.0192 x13
> Fax: 413.625.0196
> [email protected]
>
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Jamm-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jamm-users
>



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf