is it also possible to have 2 tests in dbmail_usermap?
I'd like to reduce helpdesk traffic by both allowing users to logon with
1) userid
2) [EMAIL PROTECTED]
the users are in the database in the form "[EMAIL PROTECTED]"
i.e. would this work?:
| login | sock_allow | sock_d
Marc Dirix wrote:
> is it also possible to have 2 tests in dbmail_usermap?
>
> I'd like to reduce helpdesk traffic by both allowing users to logon with
> 1) userid
> 2) [EMAIL PROTECTED]
>
> the users are in the database in the form "[EMAIL PROTECTED]"
>
> i.e. would this work?:
>
> | login
Matthew,
I'm accepting this patch for svn-trunk (not for 2.2.0)
thanks,
Matthew White wrote:
> Hello Everyone,
>
> For those with somewhat complicated AD structures, it is benefitial to
> turn not follow LDAP referrals. I'd like to submit the following patch
> to authldap.c to create a configu
login,sock_allow,userid
userA,inet:10.0.0.1:110,[EMAIL PROTECTED]
userB,inet:10.0.0.1:110,[EMAIL PROTECTED]
userC,inet:10.0.0.1:110,[EMAIL PROTECTED]
that way your users can login with both userA, and with [EMAIL PROTECTED]
Does this work with 100.000 accounts per domain?
Marc
Marc Dirix wrote:
>>
>> login,sock_allow,userid
>> userA,inet:10.0.0.1:110,[EMAIL PROTECTED]
>> userB,inet:10.0.0.1:110,[EMAIL PROTECTED]
>> userC,inet:10.0.0.1:110,[EMAIL PROTECTED]
>>
>> that way your users can login with both userA, and with [EMAIL PROTECTED]
>>
>
> Does this work with 100.00
So *that* kept me busy for just over an hour or so!
Use --with-auth-ldap *not* --with-ldap.
Jochen Entenmann wrote:
> Hi Paul,
>
> The libs must be right.
> I have checked out new and compiled like this:
>
> autoreconf -i
> ./configure --with-pgsql --with-ldap --with-sieve --prefix=/usr
> --
Or make the matching work (a bit) like in the alias table...
login,userid
[EMAIL PROTECTED] [EMAIL PROTECTED]
ANY [EMAIL PROTECTED]
where the match first tries to match the largest and than reduces.
%s is replaced by ANY.
I'm not sure this is possible at all, just a su
OK, I spent last night trolling through the wiki and such about this dbmail
application. Looks pretty cool.
But as usual there are a few questions that I didn't quite resolve last night.
Authentication:
What authentication mechanisms are available? plain, login, cram-md5...
If I understand t
Tom Allison wrote:
> Authentication:
> What authentication mechanisms are available? plain, login, cram-md5...
plain and login.
>
> If I understand the RTFM, there's no IMAPS support as yet, just IMAP.
> And this might change in the next version, or I can patch something up
> with stunnel. D
I upgraded to Fedora 6, downloaded installed the most recent _2_2_branch.
I can't recieve emails and this is the dbmail.err file,
*** glibc detected *** dbmail-lmtpd: munmap_chunk(): invalid pointer:
0x007c56ec ***
=== Backtrace: =
/lib/libc.so.6(cfree+0x1bb)[0x17967b]
/lib/libglib
When running dbmail-util -by, during the envelope cache creation:
GLib-ERROR **: gmem.c:172: failed to allocate 536870912 bytes
top doesn't show the system especially low on swap at the time this
happens...
Repairing DBMAIL for cached envelopes...
Ok. Found [120614] missing envelope values.
GLi
On Wed, 2006-11-01 at 06:45 -0500, Tom Allison wrote:
> Is it safe to assume
> that every dbmail_phymessage is made up of at least two
> dbmail_messageblks
> (header & body).
I don't think so - I think if the email comes in as headers only, and
no message body, you only have one messageblk (i
I should mention this is the latest 2.2? svn from this morning (the
trunk, no branch specified)
On Wed, 2006-11-01 at 15:03 -0600, Ryan Butler wrote:
> When running dbmail-util -by, during the envelope cache creation:
>
> GLib-ERROR **: gmem.c:172: failed to allocate 536870912 bytes
>
>
> top d
Ryan Butler wrote:
> When running dbmail-util -by, during the envelope cache creation:
>
> GLib-ERROR **: gmem.c:172: failed to allocate 536870912 bytes
>
>
> top doesn't show the system especially low on swap at the time this
> happens...
>
> Repairing DBMAIL for cached envelopes...
> Ok. Foun
14 matches
Mail list logo
