- From capability:
QUOTA NAMESPACE AUTH=CRAM-MD5 AUTH=NTLM AUTH=DIGEST-MD5 IDLE UIDPLUS
IMAP4REV1
To capability:
QUOTA NAMESPACE IDLE THREAD=ORDEREDSUBJECT AUTH=LOGIN ACL UNSELECT
SORT CHILDREN IMAP4
IMAP4REV1
Hi Harald,
in /etc/dbmail.conf you find/could add:
capability = IMAP4 IMA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I tried this few days ago, but thsi did not work
"capability" was published to imapsync as written in config-file but no success
I have stroed my passwords as cleartext for some other reasons
This time i am playing with dovecot, but i can not get thi
I tried this few days ago, but thsi did not work
"capability" was published to imapsync as written in config-file but
no success
I have stroed my passwords as cleartext for some other reasons
Hi there,
you are sure that your dbmail/dbmail-imap is giving out the correct
capabilities? I m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes i'm sure, imapsync shows something like the following while connecting
IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE
CHILDREN
NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1 STARTTLS AUTH=LOGIN
AUTH=PLAI
> Yes i'm sure, imapsync shows something like the following while
> connecting
> IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL
> + IDLE CHILDREN
> NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1 STARTTLS
> AUTH=LOGIN AUTH=PLAIN
> AUTH=CRAM-MD5 AUTH=DIGEST-M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I jump out of the window now
We patched the dbmail-source to allow mailadress with '@' or '%' as password
because this
f**g fallback is set by the most customers because problems with @-char years
ago
dovecot runs well BUT after debug on:
Aug 10 22
I jump out of the window now
That isn´t a solution ^^
We patched the dbmail-source to allow mailadress with '@' or '%' as
password because this
f**g fallback is set by the most customers because problems with @-
char years ago
dovecot runs well BUT after debug on:
Aug 10 22:22:15 localho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I know :-(
No i try to run dbmail only at localhost and use dovecot as imap-proxy
So auth-mechanisms are working
I tested on local machine with db form liveserver and proxy to liveserver
All worked well, im ade the change and seen the first md5-logi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thats all not the problem with dovecot
Here the Patch to allow % in Username
But this all would not be needed if dbmail supports MD5-Auth native as every
webscript
like horde and most php-libraries do
What i really do not undertand is that there man
> I know :-(
>
> No i try to run dbmail only at localhost and use dovecot as imap-proxy
> So auth-mechanisms are working
>
> I tested on local machine with db form liveserver and proxy to
> liveserver
> All worked well, im ade the change and seen the first md5-logins
> BUT i could not login mysel
Reindl Harald wrote:
> But why in the world dbamil-imapd/dbmail-pop3d only supports plaintext-login?
Because those are the only ones required by the IMAP rfcs.
CRAM-MD5 in itself would be very simple to add (esp. on the 2.3
codebase). However, since both CRAM-MD5 and DIGEST-MD5 require storing
p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul J Stevens schrieb:
> Because those are the only ones required by the IMAP rfcs.
OK - But do we only want the minimal requirements even if they are unsecure?
Our problem for the migration was that we never ever thought that any
mailsoftware on
On Dienstag 11 August 2009 Reindl Harald wrote:
> Please do not missunderstand me: Because of this things i got as
> nearly no sleep searching and patching things that should work out of
> the box while our customers are standing with a loaded gun behind me
By shouting at people you won't get more
Michael Monnerie wrote:
> On Dienstag 11 August 2009 Reindl Harald wrote:
>> Please do not missunderstand me: Because of this things i got as
>> nearly no sleep searching and patching things that should work out of
>> the box while our customers are standing with a loaded gun behind me
>
> By shou
> Not *that* simple, but I did it nonetheless. My GIT master tree now
> supports AUTH=CRAM-MD5.
>
> This will however *only* work for people using authsql and plaintext
> passwords.
Thanks very much Paul!
___
DBmail mailing list
DBmail@dbmail.org
http:/
On Mittwoch 12 August 2009 Paul J Stevens wrote:
> Not *that* simple, but I did it nonetheless. My GIT master tree now
> supports AUTH=CRAM-MD5.
>
> This will however *only* work for people using authsql and plaintext
> passwords.
Thank you. Is that dbmail-2.3 only I guess?
BTW, you should be cal
16 matches
Mail list logo
