Re: [courier-users] migrating from old postfix system accounts md5 passwd to courier-mta

> Hello All!
>
>> I'm have alot of problems migrating from an old postfix using systems
>> >acounts>> to courier-mta. Initialy mi plan is build a mysql database with the md5
>> system password and authenticate the users with authdaemon. I succesfully
>> authenticated the pop3 users but when triing the smtp auth courier return
>> user unknow.
>> prova@test.com $1$DfIYVyvM$YCj7/iXeVDAf0.up0HoQW/
>> >1501 101> /var/spool/postfix/
> >virtual/test.com/prova@test.com/Maildir/>> prova@test.comthis is the content of the database for test user.
>>
>> When triing the smtp auth the mysql querys was the following:
>>
>> May 31 19:33:47 pelotron courieresmtpd: EHLO pelotron.local
>> May 31 19:33:47 pelotron courieresmtpd: AUTH PLAIN
>> May 31 19:33:47 pelotron courieresmtpd: MAIL FROM:<prova@test.com>
>> BODY=8BITMIME SIZE=303May 31 19:33:47 pelotron courieresmtpd: RCPT
>> TO:<prova@test.com>
>> 050531 19:33:47 118 Query SELECT id, crypt, "", uid, gid, home,
>> maildir, "", name, "" FROM users WHERE id = "prova@test.com"
>> 118 Query SELECT id, crypt, "", uid, gid, home,
>> "", "", name, "" FROM users WHERE id = "prova"
>> May 31 19:33:55 pelotron courieresmtpd:
>> error,relay=::ffff:127.0.0.1,from=<prova@test.com> ,to=<prova@test.com>:
>> 550 User unknown.May 31 19:33:55 pelotron courieresmtpd: DATA
>> May 31 19:33:55 pelotron courieresmtpd:
>> error,relay=::ffff:127.0.0.1,msg="502 ESMTP command error",cmd: DATA

>You show two queries above. One is looking for an account called "prova",
>the second one is looking for an account called "prova@test.com".
>
>However you set up the database, the login ID must match the account ID,
>obviously.

this is the sql entry for the user...

prova@test.com prova@test.com $1$DfIYVyvM$YCj7/iXeVDAf0.up0HoQW/ 1501 101
/var/spool/postfix/ >virtual/test.com/prova@test.com/Maildir/

Yes, the login ID, match the Account ID. This is my esmtpd config file,
anyone can se something strange ?




PATH=/usr/bin:/bin:/usr/bin:/usr/local/bin
SHELL=/bin/sh
ULIMIT=4096
BOFHCHECKDNS=1
BOFHNOEXPN=1
BOFHNOVRFY=0
NOADDMSGID=1
NOADDDATE=1
ESMTP_LOG_DIALOG=1
AUTH_REQUIRED=1
COURIERTLS=/usr/bin/couriertls
TLS_PROTOCOL=TLS1
TLS_CERTFILE=/etc/courier/esmtpd.pem
TLS_VERIFYPEER=NONE
MAILUSER=daemon
MAILGROUP=daemon
ADDRESS=127.0.0.1
PORT=smtp

BLACKLISTS=""
ACCESSFILE=${sysconfdir}/smtpaccess
MAXDAEMONS=40
MAXPERC=5
MAXPERIP=5
PIDFILE=/var/run/courier/esmtpd.pid
TCPDOPTS="-nodnslookup -noidentlookup -stderrlogger=/usr/sbin/courierlogger"
AUTHMODULES="authdaemon"
ESMTPAUTH="PLAIN LOGIN CRAM-MD5 CRAM-SHA1"
ESMTPAUTH_WEBADMIN="PLAIN LOGIN CRAM-MD5"
ESMTPAUTH_TLS="PLAIN LOGIN CRAM-MD5"
ESMTPAUTH_TLS_WEBADMIN="PLAIN LOGIN CRAM-MD5"
ESMTPDSTART=YES








-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users

Why don't you just deploy perdition, and trap the passwords in a log
file? I think courier-imap can also log passwords with the right
configuration. Obviously this would introduce a delay to your
migration, but may be you have not considered this route?

How many users are there? It cannot be more than a few tens of
thousands, so not really vary many.

Bimble