-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul J Stevens wrote: > John Fawcett wrote: > >> @@ -4713,7 +4793,7 @@ >> - result = dm_sock_compare(clientsock, "", sockno); >> + result = dm_sock_compare(clientsock, sockok, sockno); > > don't do that. You won't be able to use the usermap's best-row-matches-best > weighing feature that determines which row to use for the actual mapping. > > The idea is that any match on a sock_deny will deny access, but the actual > usermapping used is determined by the row whose sock_allow matches best with > the > socket the client is connecting on. > > check out the patch in my other mail. > Paul thanks again, your patch is working fine.
here's a documentation patch too, if that helps. John -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHzsUrd4I3jTtt9EIRApUVAKDXQyee0CROv5fu+/HLOwJZn7KSeQCZAdvs Z2sPYEWNQBMWvwWQ4Bx49NQ= =LOm4 -----END PGP SIGNATURE-----
--- dbmail-2.2.9/README.usermap 2008-02-09 13:08:28.000000000 +0100 +++ dbmail-2.2.9-patch/README.usermap 2008-03-05 17:02:14.000000000 +0100 @@ -36,16 +36,19 @@ 3 |client | inet:10.1.1.1:143 | inet:10.1.1.1:110 | [EMAIL PROTECTED] 4 |ANY | inet:10.1.1.2:143 | | [EMAIL PROTECTED] 5 |client | | inet:0.0.0.0:0 | +6 |client | inet:127.0.0.1:143 | inet:0.0.0.0/0:110 | [EMAIL PROTECTED] row 1 will give you a simple 1-1 mapping irrespective of the IP address connected to. row 2 will allow [EMAIL PROTECTED] to login on a single IP address with imap. row 3 will allow [EMAIL PROTECTED] to login on a single IP address with imap but will reject -POP access. +POP access from that IP. row 4 will map all logins on a single IP address to an expanded form. row 5 will deny any kind of access to client. +row 6 will allow [EMAIL PROTECTED] to login on a single IP address with imap but will reject +POP access from any IP.
_______________________________________________ DBmail mailing list DBmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail
