IMSP Authentication issue
Good Morning All,
i'm currently migrating my system to a new server and unfortunately i have
to recompile all the stuff. Happily it went quite well with one exception.
The authentication mechanism for IMSPd is no longer working. I'm using
saslauthd which connects to a MYSQL databse. This works for all other
daemons without any problem including Cyrus IMAPd. When i try to log in to
IMSPd saslauthd returns a successfull authentication but IMSPd says, that
there is no such user on this server. On my old server i have exactly the
same configuration running without problems for years now. Please find all
the details below.
I would be very happy if someone could point my into the right direction
before i'm going mad.
Thank you!
Cheers, Martin
BTW: In the meantime is there a working virtdomain patch available for
IMSPd?
-
cyrus-imspd-v1.7b
./configure --prefix=/opt/cyrus/imsp --with-sasl=/opt --with-auth=unix
ldd imspd:
libsasl2.so.2 => /opt/lib/libsasl2.so.2 (0xb7efb000)
libdl.so.2 => /lib/libdl.so.2 (0xb7ef8000)
libresolv.so.2 => /lib/libresolv.so.2 (0xb7ee6000)
libdb-4.0.so => /usr/lib/libdb-4.0.so (0xb7e1c000)
libc.so.6 => /lib/libc.so.6 (0xb7ce2000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xb7f2e000)
cyrus-sasl-2.1.20.tar.gz
./configure \
--prefix=/opt \
--enable-anon \
--enable-plain \
--enable-login \
--disable-krb4 \
--disable-otp \
--disable-cram \
--disable-digest \
--with-saslauthd=/var/run/saslauthd \
--with-pam=/lib/security \
--with-dblib=berkeley \
--with-bdb-libdir=/usr/lib \
--with-bdb-incdir=/usr/include \
--with-openssl=/opt/openssl \
--with-plugindir=/opt/lib/sasl2
-
cat /opt/lib/sasl2/imspd.conf
pwcheck_method: saslauthd
--
testsaslauthd -u -p -s imsp
0: OK "Success."
May 29 09:09:34 h1391047 saslauthd[4333]: pam_sm_authenticate called.
May 29 09:09:34 h1391047 saslauthd[4333]: dbuser changed.
May 29 09:09:34 h1391047 saslauthd[4333]: dbpasswd changed.
May 29 09:09:34 h1391047 saslauthd[4333]: host changed.
May 29 09:09:34 h1391047 saslauthd[4333]: database changed.
May 29 09:09:34 h1391047 saslauthd[4333]: table changed.
May 29 09:09:34 h1391047 saslauthd[4333]: usercolumn changed.
May 29 09:09:34 h1391047 saslauthd[4333]: passwdcolumn changed.
May 29 09:09:34 h1391047 saslauthd[4333]: crypt changed.
May 29 09:09:34 h1391047 saslauthd[4333]: logtable changed.
May 29 09:09:34 h1391047 saslauthd[4333]: logmsgcolumn changed.
May 29 09:09:34 h1391047 saslauthd[4333]: logusercolumn changed.
May 29 09:09:34 h1391047 saslauthd[4333]: loghostcolumn changed.
May 29 09:09:34 h1391047 saslauthd[4333]: logpidcolumn changed.
May 29 09:09:34 h1391047 saslauthd[4333]: logtimecolumn changed.
May 29 09:09:34 h1391047 saslauthd[4333]: db_connect called.
May 29 09:09:34 h1391047 saslauthd[4333]: returning 0 .
May 29 09:09:34 h1391047 saslauthd[4333]: db_checkpasswd called.
May 29 09:09:34 h1391047 saslauthd[4333]: pam_mysql: where clause =
May 29 09:09:34 h1391047 saslauthd[4333]: SELECT password FROM accountuser
WHERE username=''
May 29 09:09:34 h1391047 saslauthd[4333]: sqlLog called.
May 29 09:09:34 h1391047 saslauthd[4333]: insert into log (msg, user, host,
pid, time) values('AUTH SUCCESSFUL', '', '', '4333', NOW())
May 29 09:09:34 h1391047 saslauthd[4333]: Returning 0
May 29 09:09:34 h1391047 saslauthd[4333]: returning 0 .
May 29 09:09:34 h1391047 saslauthd[4333]: returning 0.
Log in to IMSPd:
May 29 09:11:38 h1391047 saslauthd[4332]: pam_sm_authenticate called.
May 29 09:11:38 h1391047 saslauthd[4332]: dbuser changed.
May 29 09:11:38 h1391047 saslauthd[4332]: dbpasswd changed.
May 29 09:11:38 h1391047 saslauthd[4332]: host changed.
May 29 09:11:38 h1391047 saslauthd[4332]: database changed.
May 29 09:11:38 h1391047 saslauthd[4332]: table changed.
May 29 09:11:38 h1391047 saslauthd[4332]: usercolumn changed.
May 29 09:11:38 h1391047 saslauthd[4332]: passwdcolumn changed.
May 29 09:11:38 h1391047 saslauthd[4332]: crypt changed.
May 29 09:11:38 h1391047 saslauthd[4332]: logtable changed.
May 29 09:11:38 h1391047 saslauthd[4332]: logmsgcolumn changed.
May 29 09:11:38 h1391047 saslauthd[4332]: logusercolumn changed.
May 29 09:11:38 h1391047 saslauthd[4332]: loghostcolumn changed.
May 29 09:11:38 h1391047 saslauthd[4332]: logpidcolumn changed.
May 29 09:11:38 h1391047 saslauthd[4332]: logtimecolumn changed.
May 29 09:11:38 h1391047 saslauthd[4332]: db_connect called.
May 29 09:11:38 h1391047 saslauthd[4332]: returning 0 .
May 29 09:11:38 h1391047 saslauthd[4332]: db_checkpasswd called.
May 29 09:11:38 h1391047 saslauthd[4332]: pam_mysql: where clause =
May 29 09:11:38 h1391047 saslauthd[4332]: SELECT password FROM accountuser
WHERE username=''
May 29 09:11:38 h1391047 saslauthd[4332]: sqlLog called.
May 29 09:11:38 h1391047 saslauthd[4332]: insert into log (msg, user, host,
pid, time) values('AUTH SUCCESSFUL', '', '', '4332', NOW())
May 29 09:11:38 h1391047 saslauthd[4332]: Returning 0
May 29 09:11:38 h1391047 saslau
Re: IMSP Authentication issue
Anyone please?
I need to go online with my new system this afternoon and IMSPd is driving
me crazy.
Thanks in advance!
--On Donnerstag, 29. Mai 2008 11:28 +0200 Martin Ziegler
<[EMAIL PROTECTED]> wrote:
> Good Morning All,
>
> i'm currently migrating my system to a new server and unfortunately i have
> to recompile all the stuff. Happily it went quite well with one exception.
> The authentication mechanism for IMSPd is no longer working. I'm using
> saslauthd which connects to a MYSQL databse. This works for all other
> daemons without any problem including Cyrus IMAPd. When i try to log in to
> IMSPd saslauthd returns a successfull authentication but IMSPd says, that
> there is no such user on this server. On my old server i have exactly the
> same configuration running without problems for years now. Please find all
> the details below.
>
> I would be very happy if someone could point my into the right direction
> before i'm going mad.
>
> Thank you!
>
> Cheers, Martin
>
> BTW: In the meantime is there a working virtdomain patch available for
> IMSPd?
>
> -
> cyrus-imspd-v1.7b
>
> ./configure --prefix=/opt/cyrus/imsp --with-sasl=/opt --with-auth=unix
>
> ldd imspd:
> libsasl2.so.2 => /opt/lib/libsasl2.so.2 (0xb7efb000)
> libdl.so.2 => /lib/libdl.so.2 (0xb7ef8000)
> libresolv.so.2 => /lib/libresolv.so.2 (0xb7ee6000)
> libdb-4.0.so => /usr/lib/libdb-4.0.so (0xb7e1c000)
> libc.so.6 => /lib/libc.so.6 (0xb7ce2000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xb7f2e000)
>
>
> cyrus-sasl-2.1.20.tar.gz
> ./configure \
> --prefix=/opt \
> --enable-anon \
> --enable-plain \
> --enable-login \
> --disable-krb4 \
> --disable-otp \
> --disable-cram \
> --disable-digest \
> --with-saslauthd=/var/run/saslauthd \
> --with-pam=/lib/security \
> --with-dblib=berkeley \
> --with-bdb-libdir=/usr/lib \
> --with-bdb-incdir=/usr/include \
> --with-openssl=/opt/openssl \
> --with-plugindir=/opt/lib/sasl2
>
> -
> cat /opt/lib/sasl2/imspd.conf
> pwcheck_method: saslauthd
> --
>
> testsaslauthd -u -p -s imsp
> 0: OK "Success."
>
> May 29 09:09:34 h1391047 saslauthd[4333]: pam_sm_authenticate called.
> May 29 09:09:34 h1391047 saslauthd[4333]: dbuser changed.
> May 29 09:09:34 h1391047 saslauthd[4333]: dbpasswd changed.
> May 29 09:09:34 h1391047 saslauthd[4333]: host changed.
> May 29 09:09:34 h1391047 saslauthd[4333]: database changed.
> May 29 09:09:34 h1391047 saslauthd[4333]: table changed.
> May 29 09:09:34 h1391047 saslauthd[4333]: usercolumn changed.
> May 29 09:09:34 h1391047 saslauthd[4333]: passwdcolumn changed.
> May 29 09:09:34 h1391047 saslauthd[4333]: crypt changed.
> May 29 09:09:34 h1391047 saslauthd[4333]: logtable changed.
> May 29 09:09:34 h1391047 saslauthd[4333]: logmsgcolumn changed.
> May 29 09:09:34 h1391047 saslauthd[4333]: logusercolumn changed.
> May 29 09:09:34 h1391047 saslauthd[4333]: loghostcolumn changed.
> May 29 09:09:34 h1391047 saslauthd[4333]: logpidcolumn changed.
> May 29 09:09:34 h1391047 saslauthd[4333]: logtimecolumn changed.
> May 29 09:09:34 h1391047 saslauthd[4333]: db_connect called.
> May 29 09:09:34 h1391047 saslauthd[4333]: returning 0 .
> May 29 09:09:34 h1391047 saslauthd[4333]: db_checkpasswd called.
> May 29 09:09:34 h1391047 saslauthd[4333]: pam_mysql: where clause =
> May 29 09:09:34 h1391047 saslauthd[4333]: SELECT password FROM accountuser
> WHERE username=''
> May 29 09:09:34 h1391047 saslauthd[4333]: sqlLog called.
> May 29 09:09:34 h1391047 saslauthd[4333]: insert into log (msg, user,
> host, pid, time) values('AUTH SUCCESSFUL', '', '', '4333',
> NOW()) May 29 09:09:34 h1391047 saslauthd[4333]: Returning 0
> May 29 09:09:34 h1391047 saslauthd[4333]: returning 0 .
> May 29 09:09:34 h1391047 saslauthd[4333]: returning 0.
>
>
>
> Log in to IMSPd:
> May 29 09:11:38 h1391047 saslauthd[4332]: pam_sm_authenticate called.
> May 29 09:11:38 h1391047 saslauthd[4332]: dbuser changed.
> May 29 09:11:38 h1391047 saslauthd[4332]: dbpasswd changed.
> May 29 09:11:38 h1391047 saslauthd[4332]: host changed.
> May 29 09:11:38 h1391047 saslauthd[4332]: database changed.
> May 29 09:11:38 h1391047 saslauthd[4332]: table changed.
> May 29 09:11:38 h1391047 saslauthd[4332]: usercolumn changed.
> May 29 09:11:38 h1391047 saslauthd[4332]: passwdcolumn changed.
> May 29 09:11:38 h1391047 saslauthd[4332]: crypt changed.
> May 29 09:11:38 h1391047 saslauthd[4332]: logtable changed.
> May 29 09:11:38 h1391047 saslauthd[4332]: logmsgcolumn changed.
> May 29 09:11:38 h1391047 saslauthd[4332]: logusercolumn c
Re: IMSP Authentication issue
Hi Simon, yes, it is also the same than on the old server. cat /etc/pam.d/imsp auth sufficient pam_mysql.so user=mail passwd=Paiste88 host=localhost db=mail table=accountuser usercolumn=username passwdcolumn=password crypt=0 logtable=log logmsgcolumn=msg logusercolumn=user loghostcolumn=host logpidcolumn=pid logtimecolumn=time account required pam_mysql.so user=mail passwd=Paiste88 host=localhost db=mail table=accountuser usercolumn=username passwdcolumn=password crypt=0 logtable=log logmsgcolumn=msg logusercolumn=user loghostcolumn=host logpidcolumn=pid logtimecolumn=time Any other ideas? Thanks, Martin --On May 30, 2008 10:47:17 AM +0200 Simon Matter <[EMAIL PROTECTED]> wrote: >> Anyone please? >> >> I need to go online with my new system this afternoon and IMSPd is >> driving me crazy. > > I have never used IMSPd nor MySQL authentication with saslauthd. > But, from what I understand your authentication goes via PAM. If yes, do > you have the same PAM configuration on your new server, most likely in > /etc/pam.d/? > > Simon > >> >> Thanks in advance! >> >> --On Donnerstag, 29. Mai 2008 11:28 +0200 Martin Ziegler >> <[EMAIL PROTECTED]> wrote: >> >>> Good Morning All, >>> >>> i'm currently migrating my system to a new server and unfortunately i >>> have >>> to recompile all the stuff. Happily it went quite well with one >>> exception. >>> The authentication mechanism for IMSPd is no longer working. I'm using >>> saslauthd which connects to a MYSQL databse. This works for all other >>> daemons without any problem including Cyrus IMAPd. When i try to log in >>> to >>> IMSPd saslauthd returns a successfull authentication but IMSPd says, >>> that >>> there is no such user on this server. On my old server i have exactly >>> the >>> same configuration running without problems for years now. Please find >>> all >>> the details below. >>> >>> I would be very happy if someone could point my into the right direction >>> before i'm going mad. >>> >>> Thank you! >>> >>> Cheers, Martin >>> >>> BTW: In the meantime is there a working virtdomain patch available for >>> IMSPd? >>> >>> - >>> cyrus-imspd-v1.7b >>> >>> ./configure --prefix=/opt/cyrus/imsp --with-sasl=/opt --with-auth=unix >>> >>> ldd imspd: >>> libsasl2.so.2 => /opt/lib/libsasl2.so.2 (0xb7efb000) >>> libdl.so.2 => /lib/libdl.so.2 (0xb7ef8000) >>> libresolv.so.2 => /lib/libresolv.so.2 (0xb7ee6000) >>> libdb-4.0.so => /usr/lib/libdb-4.0.so (0xb7e1c000) >>> libc.so.6 => /lib/libc.so.6 (0xb7ce2000) >>> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xb7f2e000) >>> >>> >>> cyrus-sasl-2.1.20.tar.gz >>> ./configure \ >>> --prefix=/opt \ >>> --enable-anon \ >>> --enable-plain \ >>> --enable-login \ >>> --disable-krb4 \ >>> --disable-otp \ >>> --disable-cram \ >>> --disable-digest \ >>> --with-saslauthd=/var/run/saslauthd \ >>> --with-pam=/lib/security \ >>> --with-dblib=berkeley \ >>> --with-bdb-libdir=/usr/lib \ >>> --with-bdb-incdir=/usr/include \ >>> --with-openssl=/opt/openssl \ >>> --with-plugindir=/opt/lib/sasl2 >>> >>> - >>> cat /opt/lib/sasl2/imspd.conf >>> pwcheck_method: saslauthd >>> -- >>> >>> testsaslauthd -u -p -s imsp >>> 0: OK "Success." >>> >>> May 29 09:09:34 h1391047 saslauthd[4333]: pam_sm_authenticate called. >>> May 29 09:09:34 h1391047 saslauthd[4333]: dbuser changed. >>> May 29 09:09:34 h1391047 saslauthd[4333]: dbpasswd changed. >>> May 29 09:09:34 h1391047 saslauthd[4333]: host changed. >>> May 29 09:09:34 h1391047 saslauthd[4333]: database changed. >>> May 29 09:09:34 h1391047 saslauthd[4333]: table changed. >>> May 29 09:09:34 h1391047 saslauthd[4333]: usercolumn changed. >>> May 29 09:09:34 h1391047 saslauthd[4333]: passwdcolumn changed. >>> May 29 09:09:34 h1391047 saslauthd[4333]: crypt changed. >>> May 29 09:09:34 h1391047 saslauthd[4333]: logtable changed. >>> May 29 09:09:34 h1391047 saslauthd[4333]: logmsgcolumn changed. >>> May 29 09:09:34 h1391047 saslauthd[4333]: logusercolumn changed. >>> May 29 09:09:34 h1391047 saslauthd[4333]: loghostcolumn changed. >>> May 29 09
Re: IMSP Authentication issue
Any other ideas please? Thanks and enjoy the rest of the weekend. --On May 30, 2008 6:42:05 PM +0200 Martin Ziegler <[EMAIL PROTECTED]> wrote: > Hi Simon, > > yes, it is also the same than on the old server. > > cat /etc/pam.d/imsp > > auth sufficient pam_mysql.so user=mail passwd=Paiste88 host=localhost > db=mail table=accountuser usercolumn=username passwdcolumn=password > crypt=0 logtable=log logmsgcolumn=msg logusercolumn=user > loghostcolumn=host logpidcolumn=pid logtimecolumn=time > > account required pam_mysql.so user=mail passwd=Paiste88 host=localhost > db=mail table=accountuser usercolumn=username passwdcolumn=password > crypt=0 logtable=log logmsgcolumn=msg logusercolumn=user > loghostcolumn=host logpidcolumn=pid logtimecolumn=time > > Any other ideas? > > Thanks, Martin > > > --On May 30, 2008 10:47:17 AM +0200 Simon Matter <[EMAIL PROTECTED]> > wrote: > >>> Anyone please? >>> >>> I need to go online with my new system this afternoon and IMSPd is >>> driving me crazy. >> >> I have never used IMSPd nor MySQL authentication with saslauthd. >> But, from what I understand your authentication goes via PAM. If yes, do >> you have the same PAM configuration on your new server, most likely in >> /etc/pam.d/? >> >> Simon >> >>> >>> Thanks in advance! >>> >>> --On Donnerstag, 29. Mai 2008 11:28 +0200 Martin Ziegler >>> <[EMAIL PROTECTED]> wrote: >>> >>>> Good Morning All, >>>> >>>> i'm currently migrating my system to a new server and unfortunately i >>>> have >>>> to recompile all the stuff. Happily it went quite well with one >>>> exception. >>>> The authentication mechanism for IMSPd is no longer working. I'm using >>>> saslauthd which connects to a MYSQL databse. This works for all other >>>> daemons without any problem including Cyrus IMAPd. When i try to log in >>>> to >>>> IMSPd saslauthd returns a successfull authentication but IMSPd says, >>>> that >>>> there is no such user on this server. On my old server i have exactly >>>> the >>>> same configuration running without problems for years now. Please find >>>> all >>>> the details below. >>>> >>>> I would be very happy if someone could point my into the right >>>> direction before i'm going mad. >>>> >>>> Thank you! >>>> >>>> Cheers, Martin >>>> >>>> BTW: In the meantime is there a working virtdomain patch available for >>>> IMSPd? >>>> >>>> - >>>> cyrus-imspd-v1.7b >>>> >>>> ./configure --prefix=/opt/cyrus/imsp --with-sasl=/opt --with-auth=unix >>>> >>>> ldd imspd: >>>> libsasl2.so.2 => /opt/lib/libsasl2.so.2 (0xb7efb000) >>>> libdl.so.2 => /lib/libdl.so.2 (0xb7ef8000) >>>> libresolv.so.2 => /lib/libresolv.so.2 (0xb7ee6000) >>>> libdb-4.0.so => /usr/lib/libdb-4.0.so (0xb7e1c000) >>>> libc.so.6 => /lib/libc.so.6 (0xb7ce2000) >>>> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xb7f2e000) >>>> >>>> >>>> cyrus-sasl-2.1.20.tar.gz >>>> ./configure \ >>>> --prefix=/opt \ >>>> --enable-anon \ >>>> --enable-plain \ >>>> --enable-login \ >>>> --disable-krb4 \ >>>> --disable-otp \ >>>> --disable-cram \ >>>> --disable-digest \ >>>> --with-saslauthd=/var/run/saslauthd \ >>>> --with-pam=/lib/security \ >>>> --with-dblib=berkeley \ >>>> --with-bdb-libdir=/usr/lib \ >>>> --with-bdb-incdir=/usr/include \ >>>> --with-openssl=/opt/openssl \ >>>> --with-plugindir=/opt/lib/sasl2 >>>> >>>> - >>>> cat /opt/lib/sasl2/imspd.conf >>>> pwcheck_method: saslauthd >>>> -- >>>> >>>> testsaslauthd -u -p -s imsp >>>> 0: OK "Success." >>>> >>>> May 29 09:09:34 h1391047 saslauthd[4333]: pam_sm_authenticate called. >>>> May 29 09:09:34 h1391047 saslauthd[4333]: dbuser changed. >>>> May 29 09:09:34 h1391047 saslauthd[4333]: dbpasswd changed. >>>> May 29 09:09:34 h1391047 saslauthd[4333]: host changed. >>>> May 29 09:09:34 h1391047 saslauthd[4333]: database changed. >>>> May 29 09:09:
Re: IMSP Authentication issue
There is no other syslog message than the ones i posted in my initial email (SASLAUTHd which says that the authentication was successfull and IMSP which says "user does not have an account on this server). The user does have an option file. The IMSPd option file looks like imsp.sasl.allowplaintext N + common.date R + common.delivery.hosts N common.domain N imsp.admin.all N imsp.admin.bboards N imsp.create.new.users N + imsp.create.policy N parent imsp.log.level N 2 imsp.proxy.authlevel N 1 imsp.proxy.authtype N PLAINTEXT As alerady mentioned this is exactly the same setup i used for years on the old server. Also the complete IMSP directory structure was copied from the old to the new server. Only IMSPd was compiled again due to a pathname that changed. On the old server IMSP was installed in /sys/cyrus/imsp/ and now it is installed in /opt/cyrus/imsp/. # pwd /opt/cyrus/imsp # ls -al total 16 drwxr-xr-x4 root root 4096 May 29 09:07 . drwxr-x---5 cyrusmail 4096 Jun 1 19:59 .. drwxr-xr-x2 root root 4096 May 29 09:05 bin drwxr-xr-x3 root root 4096 Jan 26 2005 var # ls -al bin/ total 84 drwxr-xr-x2 root root 4096 May 29 09:05 . drwxr-xr-x4 root root 4096 May 29 09:07 .. -rwxr-xr-x1 root root70320 May 29 09:05 imspd # ls -al var/ total 16 drwxr-xr-x3 root root 4096 Jan 26 2005 . drwxr-xr-x4 root root 4096 May 29 09:07 .. -rw---1 root root0 Jan 26 2005 abooks -rw-r--r--1 root root 322 Jan 26 2005 options drwx--4 root root 4096 Aug 25 2006 user # ls -al var/user/ total 16 drwx--4 root root 4096 Aug 25 2006 . drwxr-xr-x3 root root 4096 Jan 26 2005 .. drwx--2 root root 4096 May 28 23:25 drwx--2 root root 4096 Nov 5 2007 # lsa var/user/ total 28 drwx--2 root root 4096 Nov 5 2007 . drwx--4 root root 4096 Aug 25 2006 .. -rw-r--r--1 root root11465 Nov 5 2007 abook. -rw-r--r--1 root root4 Aug 7 2006 abooks -rw-r--r--1 root root 29 Nov 5 2007 options # cat var/user//options imsp.user.quota.usage R 5188 --On June 1, 2008 1:49:23 PM -0400 Wesley Craig <[EMAIL PROTECTED]> wrote: > --On Donnerstag, 29. Mai 2008 11:28 +0200 Martin Ziegler > <[EMAIL PROTECTED]> wrote: >> When i try to log in to IMSPd saslauthd returns a successfull >> authentication but IMSPd says, that there is no such user on this >> server. > > I presume you're also getting a syslog from imspd like this: > > badlogin:invalid user > > The message: > > User does not have an account on this server > > is associated with checks for the user's option database, i.e., > > does the user have an option database? > is imsp.create.new.users on? > can the user's option database be created? > > Databases are in /var/imsp. There doesn't appears to be any checking of > permissions, just presence (at least in v1.7b), so you can get odd > situations where early checks indicate no problem but attempts to access > a user's database get "file not found". For example, /var/imsp exists, > complete with a bunch of user DBs. However, the daemon can't read what's > under it. > > :wes > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: IMSP Authentication issue
Yes it's running as root. I didn't modified any of the code. I just passed the new PREFIX to configure. Thanks, Martin --On Sonntag, 1. Juni 2008 14:38 -0400 Wesley Craig <[EMAIL PROTECTED]> wrote: > On 01 Jun 2008, at 14:08, Martin Ziegler wrote: >> There is no other syslog message than the ones i posted in my >> initial email (SASLAUTHd which says that the authentication was >> successfull and IMSP which says "user does not have an account on >> this server). > > Perhaps your syslog isn't configured to record it. The code logs that > message directly before returning that code. > >> Only IMSPd was compiled again due to a pathname that changed. > > So you modified PREFIX in syncdb.c? > >> drwx--4 root root 4096 Aug 25 2006 user >> drwx--2 root root 4096 Nov 5 2007 > > So you're running imspd as root? > > :wes > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: IMSP Authentication issue
Just recognized that authenticating to SIEVE is also no longer working. SASLAUTHd is returning a successfull authentication but SIEVE says: sievelocal[14087]: badlogin: [127.0.0.1] PLAIN authentication failure Now i'm totally confused. Interestingly authenticating to IMAPd is working as it should. --On Montag, 2. Juni 2008 08:55 +0200 Martin Ziegler <[EMAIL PROTECTED]> wrote: > Yes it's running as root. I didn't modified any of the code. I just > passed the new PREFIX to configure. > > Thanks, Martin > > --On Sonntag, 1. Juni 2008 14:38 -0400 Wesley Craig <[EMAIL PROTECTED]> wrote: > >> On 01 Jun 2008, at 14:08, Martin Ziegler wrote: >>> There is no other syslog message than the ones i posted in my >>> initial email (SASLAUTHd which says that the authentication was >>> successfull and IMSP which says "user does not have an account on >>> this server). >> >> Perhaps your syslog isn't configured to record it. The code logs that >> message directly before returning that code. >> >>> Only IMSPd was compiled again due to a pathname that changed. >> >> So you modified PREFIX in syncdb.c? >> >>> drwx--4 root root 4096 Aug 25 2006 user >>> drwx--2 root root 4096 Nov 5 2007 >> >> So you're running imspd as root? >> >> :wes >> > > > > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ > Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: IMSP Authentication issue
No, for IMSP i'm currently not using SSL/TLS. I think SASLAUTHd wouldn't return a successfull authentication if there would be a configuration mismatch. Anyway, the versions didn't changed. All the software packages are exactly the same version than on the old server. Furthermore they were compiled with the same options except the changed PREFIX. --On Montag, 2. Juni 2008 13:05 +0200 Michael Menge <[EMAIL PROTECTED]> wrote: > Hi > > do you use SSL/TLS for Sieve/IMSP? > In 2.3.9 the dafaultvalue for allowplaintext changed to 0 > > > > > Quoting Martin Ziegler <[EMAIL PROTECTED]>: > >> Just recognized that authenticating to SIEVE is also no longer working. >> SASLAUTHd is returning a successfull authentication but SIEVE says: >> >> sievelocal[14087]: badlogin: [127.0.0.1] PLAIN authentication >> failure >> >> Now i'm totally confused. Interestingly authenticating to IMAPd is >> working as it should. >> >> --On Montag, 2. Juni 2008 08:55 +0200 Martin Ziegler <[EMAIL PROTECTED]> >> wrote: >> >>> Yes it's running as root. I didn't modified any of the code. I just >>> passed the new PREFIX to configure. >>> >>> Thanks, Martin >>> >>> --On Sonntag, 1. Juni 2008 14:38 -0400 Wesley Craig <[EMAIL PROTECTED]> >>> wrote: >>> >>>> On 01 Jun 2008, at 14:08, Martin Ziegler wrote: >>>>> There is no other syslog message than the ones i posted in my >>>>> initial email (SASLAUTHd which says that the authentication was >>>>> successfull and IMSP which says "user does not have an account on >>>>> this server). >>>> >>>> Perhaps your syslog isn't configured to record it. The code logs that >>>> message directly before returning that code. >>>> >>>>> Only IMSPd was compiled again due to a pathname that changed. >>>> >>>> So you modified PREFIX in syncdb.c? >>>> >>>>> drwx--4 root root 4096 Aug 25 2006 user >>>>> drwx--2 root root 4096 Nov 5 2007 >>>> >>>> So you're running imspd as root? >>>> >>>> :wes >>>> >>> >>> >>> >>> Cyrus Home Page: http://cyrusimap.web.cmu.edu/ >>> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki >>> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html >>> >> >> >> >> Cyrus Home Page: http://cyrusimap.web.cmu.edu/ >> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki >> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html >> > > > > - > --- > M.Menge Tel.: (49) 7071/29-70316 > Universitaet Tuebingen Fax.: (49) 7071/29-5912 > Zentrum fuer Datenverarbeitung mail: > [EMAIL PROTECTED] > Waechterstrasse 76 > 72074 Tuebingen Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: IMSP Authentication issue
Wesley, you've got it. A simple ln -s /opt/cyrus/imsp/var/ /var/imsp and eerything is working as it should. Many thanks for your help guys!!! --On June 2, 2008 2:24:32 PM -0400 Wesley Craig <[EMAIL PROTECTED]> wrote: > On 02 Jun 2008, at 02:55, Martin Ziegler wrote: >> Yes it's running as root. I didn't modified any of the code. I just >> passed the new PREFIX to configure. > > The --prefix that you pass to configure isn't utilized by syncdb.c. Per > notes/Setup-instructions for version 1.7b, you have to either use > /var/imsp or edit the PREFIX definition in syncdb.c. > > :wes > >> --On Sonntag, 1. Juni 2008 14:38 -0400 Wesley Craig <[EMAIL PROTECTED]> >> wrote: >>> So you modified PREFIX in syncdb.c? > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: IMSP Authentication issue
One last question. In the meantime is there a working virtdomain patch for IMSP? --On June 3, 2008 8:38:00 AM +0200 Martin Ziegler <[EMAIL PROTECTED]> wrote: > Wesley, you've got it. > > A simple > > ln -s /opt/cyrus/imsp/var/ /var/imsp > > and eerything is working as it should. > > Many thanks for your help guys!!! > > --On June 2, 2008 2:24:32 PM -0400 Wesley Craig <[EMAIL PROTECTED]> wrote: > >> On 02 Jun 2008, at 02:55, Martin Ziegler wrote: >>> Yes it's running as root. I didn't modified any of the code. I just >>> passed the new PREFIX to configure. >> >> The --prefix that you pass to configure isn't utilized by syncdb.c. Per >> notes/Setup-instructions for version 1.7b, you have to either use >> /var/imsp or edit the PREFIX definition in syncdb.c. >> >> :wes >> >>> --On Sonntag, 1. Juni 2008 14:38 -0400 Wesley Craig <[EMAIL PROTECTED]> >>> wrote: >>>> So you modified PREFIX in syncdb.c? >> > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Virtdomain question
Hi All, i'm running Cryus imapd for several years but now there's a need to support virtual domains. Just managed to get the latest imapd version running with mysql support. Unfortunately i'm not able to get the virtual domain suppport running properly. Is there any HOWTO available (didn't found any suitable HOWTO)? I configured virtdomain as described in the documentation but for any reason there are some problems. For example when i try to 'cm [EMAIL PROTECTED]' i get an 'invalid mailbox name" error. Thanks in advance Martin --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Virtdomain question
Hi Peter, does that mean that there must be a valid user account before i create the mailbox ?? To be honest i can't believe this because when i use imapd without virtdomains this is not the case. Thanks Martin --On Sonntag, 15. August 2004 19:39 +0200 Peter Markom <[EMAIL PROTECTED]> wrote: This means that imap does not find the user "[EMAIL PROTECTED]" - I had the same problem using auxprop/sasldb, but can't help you with mysql. hth peter Am Sun, 15 Aug 2004 13:17:30 +0200 hat Martin Ziegler <[EMAIL PROTECTED]> geschrieben: Hi All, i'm running Cryus imapd for several years but now there's a need to support virtual domains. Just managed to get the latest imapd version running with mysql support. Unfortunately i'm not able to get the virtual domain suppport running properly. Is there any HOWTO available (didn't found any suitable HOWTO)? I configured virtdomain as described in the documentation but for any reason there are some problems. For example when i try to 'cm [EMAIL PROTECTED]' i get an 'invalid mailbox name" error. Thanks in advance Martin --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Virtdomain question
Hi Michael, i already got it configured to authenticate users against a mysql database. It works fine. I have simply no experiences with the virtdomain features. I already read all the documentation stuff but to be honest from my point of view there are some things which are not covered. As already said currently the main problem is that i'm not able to create a mailbox for a user [EMAIL PROTECTED] Don't know why. Anyway i'll have a look at web-cyradm. Thanks Martin --On Sonntag, 15. August 2004 23:04 +0200 Michael Obster <[EMAIL PROTECTED]> wrote: Hi, as I know, virtual domains should be handled by a MTA, Cyrus is a MDA which only have the mailboxes itself. So you only have an user without any domain. That thing you perhaps want to have are logins with a realm, but this has nothing to do with the usernames, because duplicate usernames are also not possible. But I'm not sure about this point. A better more flexible solution would be a set of users which are mapped on the virtual domains. There is also a system with mysql support available which I'm using. See http://www.web-cyradm.org/docs.html A solution with Postfix is relative easy. Also other MTAs are supported. Perhaps you get a better insight of this topic by reading the documentations of this project. They are using PAM to authenticate, but that is not the only way you can do that. There is also a sql implementation in sasl itself (but I have no experience with it). A friend of me (who is running the sasl-sql thing) only said that this not very trivial to configure cause of spare documentation. But this also true for PAM on other operating system than Linux. Cheers, Michael Obster mailto:[EMAIL PROTECTED] -- Developer at ROCK Linux http://www.rocklinux.org Martin Ziegler wrote: I configured virtdomain as described in the documentation but for any reason there are some problems. For example when i try to 'cm [EMAIL PROTECTED]' i get an 'invalid mailbox name" error. --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Deliver to subfolder
Hi, i'm still trying to deliver mails to a specific subfolder. For example: i Want to deliver to the folder user.mz.test.test1 what i do is /sys/imap/bin/deliver -m test.test1 mz but unfortunately the mail will never arrives in the IMAP server. i also tried to specify the mailbox like "-m user.mz.test.test1" or "mz.test.test1" but without success. Can someone please bring me on the right way ? Thanx ! Martin === Network EngineerUUNET - A WorldCom Company EMEA Access & Backbone Networks Sebrathweg 20 mailto: [EMAIL PROTECTED] 44149 Dortmund, Germany Tel. +49 231 972 1143 Fax. +49 231 972 1188
Compiling ACAP
Not sure if this is the right list. If it's not...sorry for that ! I'm currently trying to compile the latest version of the ACAP server. Already in use is IMAPd 2.1.9 and SASL 2.1.9. ./configure --prefix=/sys --with-cyrus-prefix=/sys/imap --with-cyrus-user=cyrus --with-cyrus-group=cyrus --with-auth=unix make returns : ### Making all in /sys/src/a/cyrus-smlacapd-0.5/lib make[1]: Entering directory `/sys/src/a/cyrus-smlacapd-0.5/lib' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/sys/src/a/cyrus-smlacapd-0.5/lib' ### Making all in /sys/src/a/cyrus-smlacapd-0.5/api make[1]: Entering directory `/sys/src/a/cyrus-smlacapd-0.5/api' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/sys/src/a/cyrus-smlacapd-0.5/api' ### Making all in /sys/src/a/cyrus-smlacapd-0.5/frontend make[1]: Entering directory `/sys/src/a/cyrus-smlacapd-0.5/frontend' gcc -L/usr/lib -L/sys/lib -L/usr/local/lib -Wl,-rpath,/usr/local/lib -g -O2 -o frontend frontend.o -ldl ../lib/libcyrus.a frontend.o: In function `cmd_authenticate': /sys/src/a/cyrus-smlacapd-0.5/frontend/frontend.c:365: undefined reference to `sasl_server_start' /sys/src/a/cyrus-smlacapd-0.5/frontend/frontend.c:392: undefined reference to `sasl_errstring' /sys/src/a/cyrus-smlacapd-0.5/frontend/frontend.c:404: undefined reference to `sasl_getprop' /sys/src/a/cyrus-smlacapd-0.5/frontend/frontend.c:385: undefined reference to `sasl_server_step' frontend.o: In function `main': /sys/src/a/cyrus-smlacapd-0.5/frontend/frontend.c:646: undefined reference to `sasl_server_init' /sys/src/a/cyrus-smlacapd-0.5/frontend/frontend.c:651: undefined reference to `sasl_server_new' /sys/src/a/cyrus-smlacapd-0.5/frontend/frontend.c:657: undefined reference to `sasl_setprop' /sys/src/a/cyrus-smlacapd-0.5/frontend/frontend.c:659: undefined reference to `sasl_setprop' /sys/src/a/cyrus-smlacapd-0.5/frontend/frontend.c:660: undefined reference to `sasl_setprop' /sys/src/a/cyrus-smlacapd-0.5/frontend/frontend.c:667: undefined reference to `sasl_listmech' ../lib/libcyrus.a(prot.o): In function `prot_setsasl': /sys/src/a/cyrus-smlacapd-0.5/lib/prot.c:171: undefined reference to `sasl_getprop' /sys/src/a/cyrus-smlacapd-0.5/lib/prot.c:182: undefined reference to `sasl_getprop' ../lib/libcyrus.a(prot.o): In function `prot_fill': /sys/src/a/cyrus-smlacapd-0.5/lib/prot.c:356: undefined reference to `sasl_decode' /sys/src/a/cyrus-smlacapd-0.5/lib/prot.c:360: undefined reference to `sasl_errstring' ../lib/libcyrus.a(prot.o): In function `prot_flush': /sys/src/a/cyrus-smlacapd-0.5/lib/prot.c:466: undefined reference to `sasl_encode' collect2: ld returned 1 exit status make[1]: *** [frontend] Error 1 make[1]: Leaving directory `/sys/src/a/cyrus-smlacapd-0.5/frontend' make: *** [all] Error 1 Unfortunately i don't have any idea what's the reason for this error. Can yomeone please help me on this ? Thanx ! Martin
Re: Compiling ACAP
Just compiled IMSP and it's working fine. --On Mittwoch, 20. November 2002 16:07 +0100 Benjamin Zeiss <[EMAIL PROTECTED]> wrote: i think the latest acap version doesn't support sasl2. i wanted to try acap as well since i liked the idea very much. however, the server development has practically stopped. if i was you i would try the communigate acap server first. they told me the acap server is in no way limited in the trial version and it thus can be used 'freely'. otherwise, depending on what you want to do, try the cyrus imsp. thats what i ended up with. it works pretty well. --On Mittwoch, 20. November 2002 15:45 +0100 Martin Ziegler <[EMAIL PROTECTED]> wrote: Not sure if this is the right list. If it's not...sorry for that ! I'm currently trying to compile the latest version of the ACAP server. Already in use is IMAPd 2.1.9 and SASL 2.1.9. ./configure --prefix=/sys --with-cyrus-prefix=/sys/imap --with-cyrus-user=cyrus --with-cyrus-group=cyrus --with-auth=unix -- Benjamin Zeiss GPG Public Key: http://www.kellnerweg.de/~bzeiss/pubkey.asc
Re: Compiling ACAP
Since i have both SASL versions installed i'm not sure if it compiles with version 2. Martin --On Donnerstag, 21. November 2002 09:02 -0500 Rob Siemborski <[EMAIL PROTECTED]> wrote: On Thu, 21 Nov 2002, Mathieu Arnold wrote: -- Martin Ziegler <[EMAIL PROTECTED]> écrivait avec ses petits doigts : > Just compiled IMSP and it's working fine. is ISMP working with sasl 2 ? No. I have a totally untested patch lying around though. (as in, I'm not even sure if it compiles). -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper === Network EngineerUUNET - A WorldCom Company EMEA Access & Backbone Networks Sebrathweg 20 mailto: [EMAIL PROTECTED] 44149 Dortmund, Germany Tel. +49 231 972 1143 Fax. +49 231 972 1188
Re: Compiling ACAP
I would also like to test the patch...if it's possible. --On Donnerstag, 21. November 2002 15:08 +0100 Mathieu Arnold <[EMAIL PROTECTED]> wrote: --Le jeudi 21 novembre 2002 09:02 -0500, -- Rob Siemborski <[EMAIL PROTECTED]> écrivait avec ses petits doigts : On Thu, 21 Nov 2002, Mathieu Arnold wrote: -- Martin Ziegler <[EMAIL PROTECTED]> écrivait avec ses petits doigts : > Just compiled IMSP and it's working fine. is ISMP working with sasl 2 ? No. I have a totally untested patch lying around though. (as in, I'm not even sure if it compiles). If you can grab that patch, I'll test it :) -- Mathieu Arnold === Network EngineerUUNET - A WorldCom Company EMEA Access & Backbone Networks Sebrathweg 20 mailto: [EMAIL PROTECTED] 44149 Dortmund, Germany Tel. +49 231 972 1143 Fax. +49 231 972 1188
Signaled to death
Hi All, i'm using cyrus-imap 2.1.9 for several and until yesterday evening without problems. When i started my client this morning i was no longer able to login to my cyrus server. The log says process xyxy exited, signaled to deatch by 11 I already did a reconstruct on all mailboxes as suggested in the FAQ but unfortunately without success. Since i changed nothing on the system for a long time i'm wondering what caused this problem. Can someone please help me on this ( until this is fixed i'm quasi offline ;-/ ) Thanks Martin
Re: Signaled to death
Just to inform you that this is already resolved. After reconstructing the mailboxes _several_ times it worked again. Thanks Martin --On Montag, 27. Januar 2003 08:46 +0100 Martin Ziegler <[EMAIL PROTECTED]> wrote: Hi All, i'm using cyrus-imap 2.1.9 for several and until yesterday evening without problems. When i started my client this morning i was no longer able to login to my cyrus server. The log says process xyxy exited, signaled to deatch by 11 I already did a reconstruct on all mailboxes as suggested in the FAQ but unfortunately without success. Since i changed nothing on the system for a long time i'm wondering what caused this problem. Can someone please help me on this ( until this is fixed i'm quasi offline ;-/ ) Thanks Martin === Network EngineerUUNET - A WorldCom Company EMEA Data Systems Engineering Sebrathweg 20 mailto: [EMAIL PROTECTED] 44149 Dortmund, Germany Phone +49 231 972 1143 Fax +49 231 972 1188
Howto Question
Hi All, i'm wondering if there is a HOWTO to get a virtual doamin mail server working with the following features: - Cyrus imapd (virtdomain, SSL for imap and pop3) - Sendmail (virtdomain, SSL, support for procmail and spamassassin) - Mysql for authenticating users wihtout having local user accounts In general i'm not quite sure if this is realisable. Unfortunately i couldn't find any HOWTO which covers my requirements. Any help is strongly appreciated! Thanks Martin --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
imsp 1.7b requirements
Hi All, i'm trying to compile imsp 1.7b on a RedHat 9 box. Unfortunately i get a lot of error messages. Are there any special requirements for this release ? Please find below more details. Any help is highly appreciated. Thanks, Martin # Cyrus SASL 2.1.20 installed in /sys/lib --- configure --- ./configure \ --prefix=/sys/cyrus/imsp \ --exec-prefix=/sys/cyrus/imsp \ --disable-gssapi \ --with-sasl=/sys \ --without-ldap \ --with-auth=unix \ --without-krb \ ### disabling kerberos ### --without-krbdes --- make depend --- ### Making depend in /sys/src/cyrus-imspd-v1.7b/imsp make[1]: Entering directory `/sys/src/cyrus-imspd-v1.7b/imsp' makedepend -I.. -I. -I. -I./../lib -I/usr/local/include -DHAVE_CONFIG_H -DSETPROCTITLE -g -O2 *.c ./*.c makedepend: warning: /usr/include/gnu/stubs.h: non-portable whitespace encountered at line 7 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 72 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 73 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 74 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 75 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 79 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 80 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 81 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 82 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 83 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 86 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 87 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 88 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 89 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 90 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 92 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 93 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 94 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 95 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 96 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 136 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 138 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 158 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 159 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 160 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 161 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 162 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 2703 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 2704 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 2705 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 2706 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 2707 make[1]: Leaving directory `/sys/src/cyrus-imspd-v1.7b/imsp' ### Done with /sys/src/cyrus-imspd-v1.7b/imsp -- Why i get the Kerberos warnings allthough i disabled Kerberos support ? --- make --- imclient.c:1077: dereferencing pointer to incomplete type imclient.c:1078: dereferencing pointer to incomplete type imclient.c: At top level: imclient.c:1127: parse error before '*' token imclient.c: In function `make_secprops': imclient.c:1129: `sasl_security_properties_t' undeclared (first use in this function) imclient.c:1129: `ret' undeclared (first use in this function) imclient.c:1129: parse error before ')' token imclient.c: At top level: imclient.c:1143: parse error before '*' token imclient.c: In function `interaction': imclient.c:1147: `t' undeclared (first use in this function) imclient.c:1147: `SASL_CB_USER' undeclared (first use in this function) imclient.c:1147: `SASL_CB_AUTHNAME' undeclared (first use in this function) imclient.c:1148: `user' undeclared (first use in this function) imclient.c:1153: `SASL_CB_PASS' undeclared (first use in this function) imclient.c: At top level: imclient.c:1168: parse error before '*' token imclient.c: In function `fillin_interactions': imclient.c:1170: `tlist' undeclared (first use in this function) imcli
imsp 1.8 virtdomain patch
Hi again, i compiled imsp 1.8 and applied the patch from William K. Hardeman which enables support for virtdomain logins. Everything works fine with the exception of PLAIN logins. Is there any patch ot there which also works with PLAIN authentication ? Thanks, Martin --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: imsp 1.7b requirements
In the meantime i found a solution on the mailing archive. Copied lib/imclient.c from the current imap source, defined HAVE_STDARG_H and everything works fine. --On Mittwoch, 26. Januar 2005 09:22 +0100 Martin Ziegler <[EMAIL PROTECTED]> wrote: Hi All, i'm trying to compile imsp 1.7b on a RedHat 9 box. Unfortunately i get a lot of error messages. Are there any special requirements for this release ? Please find below more details. Any help is highly appreciated. Thanks, Martin # Cyrus SASL 2.1.20 installed in /sys/lib --- configure --- ./configure \ --prefix=/sys/cyrus/imsp \ --exec-prefix=/sys/cyrus/imsp \ --disable-gssapi \ --with-sasl=/sys \ --without-ldap \ --with-auth=unix \ --without-krb \ ### disabling kerberos ### --without-krbdes --- make depend --- ### Making depend in /sys/src/cyrus-imspd-v1.7b/imsp make[1]: Entering directory `/sys/src/cyrus-imspd-v1.7b/imsp' makedepend -I.. -I. -I. -I./../lib -I/usr/local/include -DHAVE_CONFIG_H -DSETPROCTITLE -g -O2 *.c ./*.c makedepend: warning: /usr/include/gnu/stubs.h: non-portable whitespace encountered at line 7 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 72 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 73 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 74 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 75 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 79 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 80 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 81 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 82 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 83 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 86 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 87 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 88 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 89 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 90 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 92 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 93 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 94 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 95 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 96 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 136 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 138 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 158 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 159 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 160 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 161 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 162 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 2703 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 2704 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 2705 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 2706 makedepend: warning: /usr/include/krb.h: non-portable whitespace encountered at line 2707 make[1]: Leaving directory `/sys/src/cyrus-imspd-v1.7b/imsp' ### Done with /sys/src/cyrus-imspd-v1.7b/imsp -- Why i get the Kerberos warnings allthough i disabled Kerberos support ? --- make --- imclient.c:1077: dereferencing pointer to incomplete type imclient.c:1078: dereferencing pointer to incomplete type imclient.c: At top level: imclient.c:1127: parse error before '*' token imclient.c: In function `make_secprops': imclient.c:1129: `sasl_security_properties_t' undeclared (first use in this function) imclient.c:1129: `ret' undeclared (first use in this function) imclient.c:1129: parse error before ')' token imclient.c: At top level: imclient.c:1143: parse error before '*' token imclient.c: In function `interaction': imclient.c:1147: `t' undeclared (first use in this function) imclient.c:1147: `SASL_CB_USER' undeclared (first use in this function) imclient.c:1147: `SASL_CB_AUTHNAME' undeclared (first use in this function) imclient.c:1148: `user'
Re: imsp 1.8 virtdomain patch
I was also surprised when browsing through the FTP server. As far as in can see there is no SSL/STARTTLS support. I have to find a way to let users log in as user.domain.tld because that's the way my users are logging in. Unfortunately this breaks the address book feature because IMSP will strip off the '.domain.tld'. --On Mittwoch, 26. Januar 2005 09:19 -0500 Scott Adkins <[EMAIL PROTECTED]> wrote: --On Wednesday, January 26, 2005 12:37 PM +0100 Martin Ziegler <[EMAIL PROTECTED]> wrote: Hi again, i compiled imsp 1.8 and applied the patch from William K. Hardeman which enables support for virtdomain logins. Everything works fine with the exception of PLAIN logins. Is there any patch ot there which also works with PLAIN authentication ? Thanks, Martin IMSP 1.8??? I didn't see an announcement on that... what changes are in this version? Is there integrated SSL/STARTTLS support? I see that the ftp site shows it was put there on Jan 10th... Just surprised I didn't see anything about it... Scott -- +---+ Scott W. Adkinshttp://www.cns.ohiou.edu/~sadkins/ UNIX Systems Engineer mailto:[EMAIL PROTECTED] ICQ 7626282 Work (740)593-9478 Fax (740)593-1944 +---+ PGP Public Key available at http://www.cns.ohiou.edu/~sadkins/pgp/ --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: imsp 1.8 virtdomain patch
Is there any chance to get it implemented that users like user.domain.tld can use the addressbook feature ? I believe that there is not too much to change to get it working. --On Mittwoch, 26. Januar 2005 18:24 -0500 Derrick J Brashear <[EMAIL PROTECTED]> wrote: On Wed, 26 Jan 2005, Alan Thew wrote: On Wed, 26 Jan 2005 15:51 , Martin Ziegler <[EMAIL PROTECTED]> said: I was also surprised when browsing through the FTP server. As far as in can see there is no SSL/STARTTLS support. There are patches in CMU's CVS which patch the 1.7b server, it's running on our imsp service. These are Cyrus Daboo's patches I believe. They are. I need to test them and pull them up, at which point we will make one more release. --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
