similar to: [PATCH] add LOGIN authentication mechanism

Hello all, this patch add APOP authentication mechanism to dovecot 1.0-test23. Please take a look. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke at donpac.ru | PGP key: wwwkeys.pgp.net -------------- next part -------------- diff -udrpN -X /usr/share/dontdiff -x Makefile dovecot-1.0-test23.vanilla/src/auth/Makefile.am dovecot-1.0-test23/src/auth/Makefile.am ---

Add some const's. I think patch is self-explaining :) -- Andrey Panin | Linux and UNIX system administrator pazke at donpac.ru | PGP key: wwwkeys.pgp.net -------------- next part -------------- # HG changeset patch # User Andrey Panin <pazke at donpac.ru> # Date 1179812865 -14400 # Node ID a486a946dfa135e8c7d4083aacaef45d5386aa11 # Parent e1b3043c0d90cd346cc8cbfb6d1de3917dda5121

Hello all, attached patch implements Compuserve RPA athentication mechanism. Tested with: - Eudora 6 (uses Compuserve "Virtual Key" RPA software); - TheBat! 2.11 (uses it's own RPA implementation). I hope it can be useful for someone. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke at donpac.ru | PGP key: wwwkeys.pgp.net -------------- next part

I cooked this up while trying to figure out why thunderbird on Windows w/ SSPI was not working, but it turned out thunderbird does not use it, so I haven't been able to test it yet. I'm presenting it for discussion only, unless someone else can try it :) Modern versions of MIT kerberos support GSS-SPNEGO natively, but are only willing to negotiate for kerberos tickets and not NTLM

Hello Dovecot community, Below please find a patch that adds support to dovecot-1.2.11 for: - RFC 4467 - IMAP URLAUTH Extension - RFC 4468 - Submission BURL - RFC 4469 - IMAP CATENATE Extension URLAUTH URLAUTH is added as a plugin so it can be disabled to satisfy site security requirements. Each user's URLAUTH keys for all mailboxes are stored in a file named

Hello, looks like SASL capability reported by dovecot in response to POP3 CAPA command doesn't conforms with rfc2449 which says: Examples: C: CAPA S: +OK Capability list follows S: TOP S: USER S: SASL CRAM-MD5 KERBEROS_V4 S: RESP-CODES S: LOGIN-DELAY 900 S: PIPELINING

I was asked by my boss to do an analysis on a large data set, and I am trying to convince him to let me use R rather than SPSS. I think Sweave could make my life much much easier. To get me a little closer to this goal, I ran my analysis through R and SPSS and compared the resulting values. In all but one case, they were the same. Given the matrix [,1] [,2] [1,] 110 358 [2,] 71 312 [3,]

Hello, I found this in the logs of a Dovecot v1.0-test29 test server (OpenBSD 2.9, as mentioned in a previous email): Jul 24 05:37:47 myhostname dovecot: IMAP(username): mbox sync: UID inserted in the middle of mailbox /home/username/.mailbox (235 > 234) Jul 24 05:37:52 myhostname dovecot: IMAP(username): file mbox-sync-rewrite.c: line 357 (mbox_sync_read_and_move): assertion failed:

FreeBSD 4.10-RELEASE, dovecot-1.0-test29 crashes on sort and thread commands: Jul 25 15:12:08 owl dovecot: imap-login: Login: dima [81.19.64.101] Jul 25 15:12:26 owl dovecot: IMAP(dima): file index-mail-headers.c: line 408 (index_mail_get_header): assertion failed: (ret != 0) Jul 25 15:12:26 owl dovecot: child 20384 (imap) killed with signal 6 (gdb) bt #0 0x281e0fc4 in kill () from

Hello Everyone, I am trying to excess the inbuit .Fortran and .C codes of R. Can any one help me in that. For example in kmeans clustering the algorithms are written in .Fortran I want to access them and see the .Fortran syntax of the codes. Can any one help me how can I do that? Thanx, Nitin Kumar On Thu, Nov 27, 2008 at 12:00 PM, <r-help-request@r-project.org> wrote: > Send R-help

OpenBSD 3.6 -current (i386) dovecot-1.0-test51 I'm now getting this error message as soon as I start dovecot: "Authentication client 0 not compatible with this server (mixed old and new binaries?)" Here's the process I'm using: ./configure --sysconfdir=/etc \ --with-ssl=openssl \ --with-pam=NO \ --with-ldap=no \ --with-vpopmail=no \

See also the 32bit build failures on Debian: https://buildd.debian.org/status/package.php?p=dovecot There are some compiler warnings on 32bit architectures in test-mech.c test-mech.c: In function ?test_mechs?: test-mech.c:326:61: warning: format ?%lu? expects argument of type ?long unsigned int?, but argument 4 has type ?unsigned int? [-Wformat=] 326 | const char *testname =

The attached patch makes it possible for Kerberos principals to be associated with a password database entry by adding a new "k5principals" passdb setting. A client that successfully authenticates using GSSAPI will be able to log in as any user who has been associated with the client's Kerberos principal. This means that users can now use their Kerberos identities to access virtual

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Attached is a patch against current CVS that adds support for the GSSAPI SASL mechanism. It was written from scratch, after reading the patch from Colin Walters against a much older version of dovecot. Other then support for the 'GSSAPI' mechanism, it contains the following changes: - - Added 'auth_krb5_keytab' option for

Hi, I had successfully set up dovecot-1.0-test62 + ldap pass/user db, but now I'm encoutering a SIGSEV problem with a similar set up of a brand new dovecot-1.0-test65 installation. The auth process is killed by a SIGSEV as reported in the error log file : dovecot: Mar 30 17:06:59 Error: child 28291 (auth) killed with signal 11 To be precise, the problem occurs in the

Recently we changed Postfix to use Dovecot for our SASL authentication and we ran into trouble with some of our clients having extraneous spaces at the end of their usernames. The quick fix was to add a space to username_chars. The slightly longer fix was a pretty simple patch to Dovecot. I put the trimming in auth_request_fix_username. I didn't think it warranted a full strfuncs

http://dovecot.org/test/ Huh, I almost got stuck with this one. It's boring to do larger rewrites to things that already kind of work. This time it was rewriting how caching headers work. The old way was kind of ugly and it didn't really guarantee the order in which cached headers could be fetched. So there were a few theoretical problems that could have broken things. 0.99.10 didn't