, but had lots of issues. This time he
> decided
> > to use pam_mysql and now can't finish.
> >
I've never used cyrus pam_mysql and exim (I'm using cyrus pam_mysql and
postfix), but you could look at web-cyradm tutorial where you can find an
excellent howto (particularly
onsultant to help with the final
> configuration for a new server? A consulting system admin has had to give up
> getting this running and I need it in within the day. This consultant
> successfully did my last move, but had lots of issues. This time he decided
> to use pam_mysql and
Jerry,
I can't help you with pam_mysql, however I was able to setup Cyrus to
auth against mysql with the auxprop plugin from SASL, which should be
easier to configure than pam_mysql. Here is what you should have in your
imap.conf:
sasl_mech_list: PLAIN LOGIN
sasl_pwcheck_method: au
to use pam_mysql and now can't finish.
I can manage the migration, mysql, and cyrus management, but I have now
stuggle through google and the archives, but it is not working yet.
It is likely a configuration issue.
As a desperate attempt, here is what we currently have in
/etc/pam.d/imap
On Tue, 2007-04-17 at 12:50 +0530, ram wrote:
> I have a pam_mysql setup with a simple mysql table
> and saslauthd is running with the "-r" option on
> If I test with a user on the primary domain it works fine , but for a
> user on any other domain th
I have a pam_mysql setup with a simple mysql table
and saslauthd is running with the "-r" option on
If I test with a user on the primary domain it works fine , but for a
user on any other domain there is an auth failure
---
cat /etc/pam.d/imap
#%PAM-1.0
auth sufficient pa
>>> sender: "Simon Matter" date: "Thu, Jun 29, 2006 at 03:13:13PM +0200" << > sql_select: SELECT password FROM popusers WHERE alias='%u' and
> > domain='%r';
> ^^^
> I'm not sure you need this one.
>
> And then, from examples I found on the net I think you need the sasl_
> prefix like
sys
>>sql_user: someuser
>>sql_passwd: fubar
>>sql_select: SELECT password FROM users WHERE name='%u' and
>> domain='%r';
>
> Ok. I've dropped PAM+pam_mysql out of the equation.
> Now I've got a plain Cyrus+
wd: fubar
>sql_select: SELECT password FROM users WHERE name='%u' and domain='%r';
Ok. I've dropped PAM+pam_mysql out of the equation.
Now I've got a plain Cyrus+SASL, unsing auxprop & mysql.
Read all the
On 2006-06-27 at 19:25 +0300, Alexandru E. Ungur wrote:
> I'm having a bit of a hard time doing a migration of cyrus from this:
> anyway, on the old server it is a cyrus+saslauthd+pam+pam_mysql+mysql
> On the new server I got saslauthd working pretty much ok (I think).
Using PAM,
>>> sender: "Simon Matter" date: "Wed, Jun 28, 2006 at 08:38:02PM +0200" << Hm, I may have been wrong... While it's okay to remove the auxprop lines
> from the config, it has likely not been the cause for the logs. Your
> config really uses pam_mysq
>>>> sender: "Simon Matter" date: "Wed, Jun 28, 2006 at 07:59:12PM +0200"
>>>> <<> Sorry, I can not help you at all with the mysql stuff because I have
>> never
>> used it with cyrus. However, you want to use pam_mysql but your
&g
>>> sender: "Simon Matter" date: "Wed, Jun 28, 2006 at 07:59:12PM +0200" << Sorry, I can not help you at all with the mysql stuff because I have never
> used it with cyrus. However, you want to use pam_mysql but your
> cyrus-imapd tries to use the mysq
>>>> sender: "Simon Matter" date: "Wed, Jun 28, 2006 at 07:13:40PM +0200"
>>>> <<> Make that 'cyradm -user cyrus -auth login localhost'
>
> Thank you! :)
> I did that, here's what happened:
>
> FIRST,
>>> sender: "Simon Matter" date: "Wed, Jun 28, 2006 at 07:13:40PM +0200" << Make that 'cyradm -user cyrus -auth login localhost'
Thank you! :)
I did that, here's what happened:
FIRST, I used the old pam_mysql 0.4.5 that was on the old se
ns. However, user and domain are two separate
> fields in the table and I don't really understand how pam_mysql is
> supposed to work with them like that...
> Furthermore, I checked the logs on the old server:
> ===
with Cyrus-IMAPd? If not, then appending
> the realm isn't necessary. Else you too have to run saslauthd with
> parameter "-r". Your database and SQL statements do not indicate
> [EMAIL PROTECTED] usage.
Yes, we use virtual domains. However, user and domain are two sepa
Am Di, den 27.06.2006 schrieb Alexandru E. Ungur um 18:25:
> 3. [EMAIL PROTECTED] lib]# testsaslauthd -u cyrus -p PASSWORD -s imap
>0: OK "Success."
>
> So I think I got the sasl+pam+mysql part working (but I could be wrong,
> I'm pretty new to the whole cyrus world :D)
>
> Now, my problem i
oll
anyway, on the old server it is a cyrus+saslauthd+pam+pam_mysql+mysql
On the new server I got saslauthd working pretty much ok (I think).
1. it is run like this:
# ps ax|grep sasl
32293 ?Ss 0:00 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam
-n 0
so it uses pam,
2. pam
Simon Matter wrote:
Could you try "cyradm [EMAIL PROTECTED] --auth=login localhost"
Same error :( saslauthd/pam authenticate (and log success) but then
imap complains about a cross-realm login.
-jim
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.
-
> saslauthd[19088]: SELECT pass FROM accounts WHERE user='[EMAIL PROTECTED]'
> saslauthd[19088]: sqlLog called.
> saslauthd[19088]: insert into log (msg, user, host, pid, time)
> values('AUTH SUCCESSFUL', '[EMAIL PROTECTED]'
TH SUCCESSFUL', '[EMAIL PROTECTED]', '', '19088', NOW())
saslauthd[19088]: Returning 0
saslauthd[19088]: returning 0 .
saslauthd[19088]: returning 0.
saslauthd[19088]: pam_mysql: acct_mgmt called but not implemented. Dont
panic though :)
imap[19170]: cross-realm log
I'm trying to implement a virtual-domain/virtual-user setup where
'[EMAIL PROTECTED]' and '[EMAIL PROTECTED]' are separate users/accounts/mailboxes.
I'm using RHEL4 and all its official RPMs except for pam_mysql which
comes from a third party that rebuilds FC3
why pam_mysql dont log the host ip? my /var/log/auth says:
---
Jan 17 17:06:43 linares saslauthd[22506]: returning 0.
Jan 17 17:06:43 linares
STION(s):
(a) web-cyradm's HOWTO instructs that pam_mysql be used with SASL2 for
authentication.
however, i've found
<http://groups.google.com/groups?hl=en&lr=&threadm=bvvqjf%2425rh%241%40FreeBSD.csie.NCTU.edu.tw&rnum=2&prev=/groups%3Fq%3Dpam_mysql%253A%2520MySQ
:25:34 cougar saslauthd[67928]: logpidcolumn changed.
> May 25 02:25:34 cougar saslauthd[67928]: logtimecolumn changed.
> May 25 02:25:34 cougar saslauthd[67928]: db_connect called.
> May 25 02:25:34 cougar saslauthd[67928]: returning 0 .
> May 25 02:25:34 cougar saslauthd[67928]: db_checkpas
saslauthd[67928]: db_checkpasswd called.
May 25 02:25:34 cougar saslauthd[67928]: pam_mysql: where clause =
May 25 02:25:34 cougar saslauthd[67928]: SELECT password FROM accountuser
WHERE username='rls0001'
May 25 02:25:34 cougar saslauthd[67928]: sqlLog called.
May 25 02:25:34 cougar saslauth
Does web-cyradm + mysql + pam_mysql +
cyrus-imapd-2.2.3-4 combination work anymore, or
should I change the authentication mechanism? Any help
would be greatly appreciated.
Thanks
Khan
__
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http
Zitat von Temp <[EMAIL PROTECTED]>:
> when after I login imap account, there is so much logs,
> and how to get rid of them ??
> I seach google, but no exact answer for it.
>
> Mar 14 08:55:19 mx saslauthd[13604]: pam_mysql: error: sqllog set but
> logmsgcolumn not
when after I login imap account, there is so much logs,
and how to get rid of them ??
I seach google, but no exact answer for it.
Mar 14 08:55:19 mx saslauthd[13604]: pam_mysql: error: sqllog set but
logmsgcolumn not set
Mar 14 08:55:19 mx saslauthd[13604]: pam_mysql: error: sqllog set but
Hello!
Am Wed, 12 Mar 2003 15:01:36 -0500 schrieb John Alton Tamplin:
> >eta saslauthd[982]: pam_mysql: where clause =
> >eta saslauthd[982]: SELECT password FROM accountuser WHERE username='karl'
> >eta saslauthd[982]: pam_mysql: select returned more than one
Andreas Meyer wrote:
eta saslauthd[982]: pam_mysql: where clause =
eta saslauthd[982]: SELECT password FROM accountuser WHERE username='karl'
eta saslauthd[982]: pam_mysql: select returned more than one result
eta saslauthd[982]: returning 7 after db_checkpasswd.
eta saslauthd[982]
thd[983]: db_connect called.
eta saslauthd[983]: returning 0 .
eta saslauthd[983]: db_checkpasswd called.
eta saslauthd[983]: pam_mysql: where clause =
eta saslauthd[983]: SELECT password FROM accountuser WHERE username='cyrus'
eta saslauthd[983]: sqlLog called.
eta saslauthd[983]: pa
OK, there was an extra line in /etc/impad.conf
removed it in vi.
killall master ; /usr/cyrus/bin/master
still no mysql connection recorded in mysql log (tail -f ).
sudo pam is still making a mysql connection and querying the
mysql database though.
Ramiro Morales wrote:
> Vincent:
>
> I do no
Vincent:
I do not remember if you said you use Cyrus 2.0.16
in your original post. But if it is the case
perhaps you may want to be sure you do not have
extra trailing spaces in the lines of /etc/impad.conf
2.0.16 has this bug. It is now fixed in CVS
(file is imap/config.c just if you want to p
OK, tried that and added the extra mysql parameters
even though according to the pam docs, they are only necessary
if you need to change the defaults.
Still no joy.
:-(
Nick Ustinov wrote:
> I'd change it to
>
> auth optional /lib/security/pam_mysql.so ...
>
> is user cyr without password?
I'm sorry if i wasn't 100% clean on the subject.
The point is that - in un*x - usernames starting with anything else than
a letter [a-z] will not work properly.
The first time i read this i was thinking about pam_smb... right now i
see that we are talking about pam_mysql. Anyway,
On Thu, 10 May 2001, Nuno Silva wrote:
>
> I'm sorry if i wasn't 100% clean on the subject.
> The point is that - in un*x - usernames starting with anything else than
> a letter [a-z] will not work properly.
not true here either ... the University that I work at, since before I
ever got there, h
st my $0.02,
> Nuno Silva
>
> Nick Ustinov wrote:
>
> > is there anyone using pam_mysql for auth? it seems to not accept usernames
> > consisting only of numerals. Let's say there is a user 00100 and then when I
> > try to do auth it just dies and that's it
ted :)
Try to login as 0 (zero) and give as password the root password (user
root must exist in the PDC/windows box).
Just my $0.02,
Nuno Silva
Nick Ustinov wrote:
> is there anyone using pam_mysql for auth? it seems to not accept usernames
> consisting only of numerals. Let's say t
is there anyone using pam_mysql for auth? it seems to not accept usernames
consisting only of numerals. Let's say there is a user 00100 and then when I
try to do auth it just dies and that's it. Can it possibly be because of
sprinf it is using has %s ? I am not into C much. Could anyone
Paul Dekkers wrote:
>
> Hi
>
> I tried pam_mysql instead of sasldb, and I am now able to log in to imap
> (and even a simple login shell) with the data specified from the database,
> but pop3 isn't working - what can be wrong? When I change from
> sasl_pwcheck_method:
Hi
I tried pam_mysql instead of sasldb, and I am now able to log in to imap
(and even a simple login shell) with the data specified from the database,
but pop3 isn't working - what can be wrong? When I change from
sasl_pwcheck_method: PAM to sasl_pwcheck_method: sasldb
both systems (as well
43 matches
Mail list logo
