Hello,
well, I just tried it and confirm this happens with v.2.2.8
(set everything to UTF8), for POP and IMAP login.
on POP this happens:
+OK DBMAIL pop3 server ready to rock
user XXX
+OK Password required for XXX
pass äqwert1
-ERR your command does not compute
quit
+OK see ya later
on IMAP:
* OK dbmail imap (protocol version 4r1) server 2.2 ready to run
? login XXX äqwert1
? NO login rejected
so well, it would be nice if that could be fixed.
Kind regards,
Daniel
Robert Claeson schrieb:
On 25 Jan 2008, at 13:08, Michael Monnerie wrote:
On Freitag, 25. Januar 2008 Simon Lange wrote:
Well a-z and 0-9 should be all he needs.
We're hosting companies that we cannot control, nor would they want to
accept that.
"löl" is not a secure password anyway.
More secure than "jfhguieh" at least, because special chars are less
used in dictionary attacks. We always recommend using special chars for
passwords - so I'd like to have a fix.
Just tell him that special chars (which are öäüß) are not allowed in
a password as they are not allowed in the localpart.
That's an organisatoric solution, is there no technical fix?
I would also like to see a fix. We routinely recommend customers to use
characters outside the ASCII range for passwords as they have shown to
be much more secure than the usual ones.
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
