Re: My sub-folder with Outlook work-around to date

[mj]

Hi,

What we do, on the dovecot side, is:

mail_location = maildir:~/Maildir:LAYOUT=fs:DIRNAME=mAildir

See: https://wiki2.dovecot.org/MailLocation/Maildir

This has been working out very nicely for many years.

I'm not sure though that there is a way to 'move' to that config without 
having to basically migrate all your mailboxes.


MJ

On 10/06/2017 04:08 AM, David.M.Clark wrote:

Hi All, please be kind, this is my first e-mail to the list :-)

I actively support CentOS based e-mail servers running Dovecot, 
Sendmail, Spammassassin and 3 x SOGo based setups.


Dovecot is my goto IMAP server and have used it and modifications to it 
to net excellent results for years.


Then we have people who insist on only using Outlook (and in some 
instances the MS Live Messenger thingy).


Some shenanigans in recent years have arose with using sub-folders in 
the Outlook clients (2013 and 2016).


Traditionally, placing a "/" after the name of a newly desired e-mail 
folder has netted the result of something like:


"Rentals/"

creating:

/u/home/someuser/mail/Rentals/

Under which users then create actual e-mail folders under the "Rentals" 
Linux directory as such.


With Outlook 2013 and 2016 this seems to have stopped working and so I 
implemented a work-around where the user creates a normal folder, 
example "Rentals++", and I have written a cron script that trawls the 
$HOMEs each minute and if it finds a folder with a "++" at the end, it 
creates the folder as a directory, so:


/u/home/someuser/mail/Rentals++

becomes:

/u/home/someuser/mail/Rentals/

and adds this new subscription to their .subscription folder. It also 
sends an e-mail to the user advising that the new folder is created and 
they can proceed to use the "Rentals" folder for adding sub-folders (as 
in real text based mail folders).


The script was a quick work-around one weekend in a mad flurry to get 
things working and to date works but is not 'user-proof'. So I am now 
looking at developing an internal web interface to do the same thing and 
hoping with more controls, has no or far less margin for user error. 
Long times of Outlook folder refreshes don't help and users sometimes 
end up with issues that require my Linux command line help.


I have been trawling e-mail forums for some time now and have not seen 
any other work-arounds (or perhaps I am living under a rock) but before 
I embark on this web interface adventure, I just wanted to make sure I 
had not missed some fundamental 'bit' that I should be observing.


All servers are either CentOS 6.9 (or slightly less) and CentOS 7 with 
the latest updates and for things like Thunderbird and Roundcube and 
SOGo, work well. I need to experiment with the whole "/" for these but I 
am currently driven by the enforced Outlook chains.


Any input from you guys on whether this is my best approach or 'hey 
mate, just do this', would be much appreciated.


I am happy to share my travels script/web-wise if this is the only 
option to date.

Re: moving from mysql to pgsql

[mws]

Hello Noel!


On 04.10.2017 23:42, Noel Butler wrote:

As a test, this is testing123 in sha512
$6$Z6I5oyWUed.tmNUs$0ScF2w3ejPWFAX/3F6DgMyWpbXLq0DD6blL8rwBpSHGWaZ9RiXlpo5PPZFoJPZWIuQMETELsXG2YtbsAc8K3q/


Again, after inserting this String as is into the pgsql database, I can 
authenticate with dovecot.


Now the next step for me would be to be able to generate such SHA512 
hashes with pgsql myself.

I made two attempts:

1) select digest('testing123','sha512');
result:
 
\x4120117b3190ba5e24044732b0b09aa9ed50eb1567705abcbfa78431a4e0a96b1152ed7f4925966b1c82325e186a8100e692e6d2fcb6702572765820d25c7e9e
login fails

2) select encode(digest('testing123','sha512'),'hex');
result:
 
4120117b3190ba5e24044732b0b09aa9ed50eb1567705abcbfa78431a4e0a96b1152ed7f4925966b1c82325e186a8100e692e6d2fcb6702572765820d25c7e9e
login fails

How did you generate your hash and how can I do the same with pgsql?

Thanks
Magnus

My sub-folder with Outlook work-around to date

[David.M.Clark]

Hi All, please be kind, this is my first e-mail to the list :-)

I actively support CentOS based e-mail servers running Dovecot, 
Sendmail, Spammassassin and 3 x SOGo based setups.


Dovecot is my goto IMAP server and have used it and modifications to it 
to net excellent results for years.


Then we have people who insist on only using Outlook (and in some 
instances the MS Live Messenger thingy).


Some shenanigans in recent years have arose with using sub-folders in 
the Outlook clients (2013 and 2016).


Traditionally, placing a "/" after the name of a newly desired e-mail 
folder has netted the result of something like:


"Rentals/"

creating:

/u/home/someuser/mail/Rentals/

Under which users then create actual e-mail folders under the "Rentals" 
Linux directory as such.


With Outlook 2013 and 2016 this seems to have stopped working and so I 
implemented a work-around where the user creates a normal folder, 
example "Rentals++", and I have written a cron script that trawls the 
$HOMEs each minute and if it finds a folder with a "++" at the end, it 
creates the folder as a directory, so:


/u/home/someuser/mail/Rentals++

becomes:

/u/home/someuser/mail/Rentals/

and adds this new subscription to their .subscription folder. It also 
sends an e-mail to the user advising that the new folder is created and 
they can proceed to use the "Rentals" folder for adding sub-folders (as 
in real text based mail folders).


The script was a quick work-around one weekend in a mad flurry to get 
things working and to date works but is not 'user-proof'. So I am now 
looking at developing an internal web interface to do the same thing and 
hoping with more controls, has no or far less margin for user error. 
Long times of Outlook folder refreshes don't help and users sometimes 
end up with issues that require my Linux command line help.


I have been trawling e-mail forums for some time now and have not seen 
any other work-arounds (or perhaps I am living under a rock) but before 
I embark on this web interface adventure, I just wanted to make sure I 
had not missed some fundamental 'bit' that I should be observing.


All servers are either CentOS 6.9 (or slightly less) and CentOS 7 with 
the latest updates and for things like Thunderbird and Roundcube and 
SOGo, work well. I need to experiment with the whole "/" for these but I 
am currently driven by the enforced Outlook chains.


Any input from you guys on whether this is my best approach or 'hey 
mate, just do this', would be much appreciated.


I am happy to share my travels script/web-wise if this is the only 
option to date.


--

As always, I remain at your service.

Kindest Regards,
David.M.Clark (Director - Senior Linux/UNIX Consultant)
E-mail: da...@davrom.com
=--=
 Specialising in: Linux (Fedora/RedHat/CentOS), UNIX, SCO, MikroTik,
  Networking/Internet, E-mail/Web Technologies
=--=

Re: dovecot: master: Warning: Sent SIGKILL to 100 imap-login processes

[Sami Ketola]

> On 5 Oct 2017, at 22.16, absolutely_f...@libero.it wrote:
> 
> Hi,
> 
> I am using Dovecot 2.2.32 (dfbe293d4)
> 
> I noticed lots of messages like:
> 
> dovecot: master: Warning: Sent SIGKILL to 100 imap-login processes
> 
> in /var/log/maillog
> 
> I commented out "process_limit"
> 
> 
> service imap {
> # Most of the memory goes to mmap()ing files. You may need to increase this
> # limit if you have huge mailboxes.
> #vsz_limit = $default_vsz_limit
> 
> # Max. number of IMAP processes (connections)
> process_limit = 1024
> }
> 
> 
> but it seems that value doesn't change (still 100).
> 
> Any suggestions?
> 
> Thank you very much!


So you just commented it out?

so then it’s using the default_process_limit:
# doveconf -d | grep default_process_limit
default_process_limit = 100

which is 100.

Sami

dovecot: master: Warning: Sent SIGKILL to 100 imap-login processes

[absolutely_free]

Hi,

I am using Dovecot 2.2.32 (dfbe293d4)

I noticed lots of messages like:

dovecot: master: Warning: Sent SIGKILL to 100 imap-login processes

in /var/log/maillog

I commented out "process_limit"


service imap {
# Most of the memory goes to mmap()ing files. You may need to increase this
# limit if you have huge mailboxes.
#vsz_limit = $default_vsz_limit

# Max. number of IMAP processes (connections)
process_limit = 1024
}


but it seems that value doesn't change (still 100).

Any suggestions?

Thank you very much!

v2.2.33 release candidate released

[Timo Sirainen]

https://dovecot.org/releases/2.2/rc/dovecot-2.2.33.rc1.tar.gz
https://dovecot.org/releases/2.2/rc/dovecot-2.2.33.rc1.tar.gz.sig 

There are a couple more small changes still coming, but this should be very 
close to the final release. I'm especially interested in hearing if there are 
any problems with doveadm log proxying or with director. We've improved our 
automated director tests quite a lot now, and fixed some rarely occurring bugs.

 * doveadm director commands wait for the changes to be visible in the
   whole ring before they return. This is especially useful in testing.
 * Environments listed in import_environment setting are now set or
   preserved when executing standalone commands (e.g. doveadm)

 + doveadm proxy: Support proxying logs. Previously the logs were
   visible only in the backend's logs.
 + Added %{if}, see https://wiki2.dovecot.org/Variables#Conditionals
 + Added a new notify_status plugin, which can be used to update dict
   with current status of a mailbox when it changes. See
   https://wiki2.dovecot.org/Plugins/NotifyStatus
 + Mailbox list index can be disabled for a namespace by appending
   ":LISTINDEX=" to location setting.
 + dsync/imapc: Added dsync_hashed_headers setting to specify which
   headers are used to match emails.
 + pop3-migration: Add pop3_migration_ignore_extra_uidls=yes to ignore
   mails that are visible in POP3 but not IMAP. This could happen if
   new mails were delivered during the migration run.
 + pop3-migration: Further improvements to help with Zimbra
 + pop3-migration: Cache POP3 UIDLs in imapc's dovecot.index.cache
   if indexes are enabled. These are used to optimize incremental syncs.
 + cassandra, dict-sql: Use prepared statements if protocol version>3.
 - sdbox: Mails were always opened when expunging, unless
   mail_attachment_fs was explicitly set to empty.
 - lmtp/doveadm proxy: hostip passdb field was ignored, which caused
   unnecessary DNS lookups if host field wasn't an IP
 - lmtp proxy: Fix crash when receiving unexpected reply in RCPT TO
 - quota_clone: Update also when quota is unlimited (broken in v2.2.31)
 - mbox, zlib: Fix assert-crash when accessing compressed mbox
 - doveadm director kick -f parameter didn't work
 - doveadm director flush  resulted flushing all hosts, if 
   wasn't an IP address.
 - director: Various fixes to handling backend/director changes at
   abnormal times, especially while ring was unsynced. These could have
   resulted in crashes, non-optimal behavior or ignoring some of the
   changes.
 - director: Use less CPU in imap-login processes when moving/kicking
   many users.
 - lmtp: Session IDs were duplicated/confusing with multiple RCPT TOs
   when lmtp_rcpt_check_quota=yes
 - doveadm sync -1 fails when local mailboxes exist that do not exist
   remotely. This commonly happened when lazy_expunge mailbox was
   autocreated when incremental sync expunged mails.

Re: Issue with imap folder structure

[absolutely_free]

Hi,

honestly, I don't know if I need that.. I simply copied settings from former 
server, but with unexpected results.

I wondering what is correct Dovecot settings according to maildir layout in my 
case:



drwx-- 5 postfix postfix 11 Jun 19 18:22 .Deleted Items
drwx-- 5 postfix postfix 11 Sep 29 09:27 .Drafts
drwx-- 5 postfix postfix 9 Oct 4 10:18 .INBOX.Drafts
drwx-- 5 postfix postfix 9 Oct 4 10:18 .INBOX.Sent
drwx-- 5 postfix postfix 9 Oct 3 18:01 .INBOX.Trash
drwx-- 5 postfix postfix 12 Sep 29 09:27 .Junk
drwx-- 5 postfix postfix 8 Dec 9 2014 .Junk E-mail
drwx-- 5 postfix postfix 9 Oct 2 14:18 .Posta indesiderata
drwx-- 5 postfix postfix 9 Jun 19 18:22 .Posta inviata
drwx-- 5 postfix postfix 10 Oct 4 12:27 .Sent
drwx-- 5 postfix postfix 10 Oct 5 00:23 .Trash
drwx-- 2 postfix postfix 217 Oct 5 13:09 cur
-rw--- 1 postfix postfix 53 Feb 16 2017 dovecot-keywords
-rw--- 1 postfix postfix 14028 Oct 5 13:09 dovecot-uidlist
-rw--- 1 postfix postfix 8 Oct 3 18:01 dovecot-uidvalidity
-r--r--r-- 1 postfix postfix 0 Nov 27 2015 dovecot-uidvalidity.5658162a
-r--r--r-- 1 postfix postfix 0 Sep 27 18:18 dovecot-uidvalidity.59cbcf5c
-rw--- 1 postfix postfix 7200 Sep 29 01:19 dovecot.index
-rw--- 1 postfix postfix 65740 Oct 5 18:07 dovecot.index.cache
-rw--- 1 postfix postfix 7932 Oct 5 13:46 dovecot.index.log
-rw--- 1 postfix postfix 216 Oct 3 18:01 dovecot.mailbox.log
drwx-- 2 postfix postfix 2 Oct 5 13:08 new
-rw--- 1 postfix postfix 96 Oct 3 18:01 subscriptions
drwx-- 2 postfix postfix 2 Oct 5 12:58 tmp


thank you very much

Those are my Roundcube settings

$config['default_folders'] = array('INBOX', 'Drafts', 'Sent', 'Junk', 'Trash');

> 
> Il 5 ottobre 2017 alle 11.57 "A.L.E.C"  ha scritto:
> 
> On 05.10.2017 00:24, absolutely_f...@libero.it wrote:
> 
> > > 
> > namespace {
> > inbox = yes
> > location =
> > prefix = INBOX.
> > separator = .
> > type = private
> > }
> > 
> > > 
> If you don't need INBOX.* folders then remove the above namespace
> definition. Roundcube adds automatically the personal namespace prefix
> to special folders.
> 
> --
> Aleksander 'A.L.E.C' Machniak
> Kolab Groupware Developer [http://kolab.org]
> 
> Roundcube Webmail Developer [http://roundcube.net]
> 
> 
> PGP: 19359DC1 # Blog: https://kolabian.wordpress.com
> 

Re: Issue with imap folder structure

[absolutely_free]

Hi Steffen,


sorry, in this case "duplicate" means that users have two folders in webmail 
(Roundcube) with same content.

I did not tried to move messages between folders yte.

I confirm that on previous server, this was Dovecot's settings:

namespace {
type = private
separator = .
prefix = INBOX.
inbox = yes
}

After migration to new server (as I said I copied spool at filesystem level), I 
noticed that namespace settings was different:


namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}


So, I used "INBOX" prefix:


namespace {
type = private
separator = .
prefix = INBOX.
inbox = yes
}


and restarted Dovecot, but it seems I created lots of issues..

Now I restored  the original configuration.. it seems ok

Is it a bit unclear how configure properly Roundcube AND Dovecot (regarding 
IMAP settings)


Thank you very much



> Il 5 ottobre 2017 alle 11.48 Steffen Kaiser  
> ha scritto:
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, 5 Oct 2017, absolutely_f...@libero.it wrote:
>
> > I just migrated spool from another server (by copying filesystem, I use 
> > maildir), this is an example of mailbox's content:
> >
> > drwx-- 5 postfix postfix 11 Sep 29 09:27 .Drafts
> > drwx-- 5 postfix postfix 9 Oct 4 10:18 .INBOX.Drafts
> > drwx-- 5 postfix postfix 9 Oct 4 10:18 .INBOX.Sent
> > drwx-- 5 postfix postfix 9 Oct 3 18:01 .INBOX.Trash
> > drwx-- 5 postfix postfix 12 Sep 29 09:27 .Junk
> > drwx-- 5 postfix postfix 8 Dec 9 2014 .Junk E-mail
> > drwx-- 5 postfix postfix 10 Oct 4 12:27 .Sent
> > drwx-- 5 postfix postfix 10 Oct 4 18:01 .Trash
>
> > -rw--- 1 postfix postfix 96 Oct 3 18:01 subscriptions
>
> > It seems I have duplicate folder (for example during webmail access, I use 
> > Roundcube).
>
> You did not explain, which folders are duplicate.
> Does "duplicate" mean, that they have the some content or just the same
> name? If copy one message into one folder, is it accessable through the
> other one?
>
> > What is wrong with my setup?
>
> Well, you mean "Sent" and "INBOX.Sent", which latter is a mailbox named
> "Sent" as subfolder of INBOX, then they are not duplicates, but have the
> same name. Eventually, your mail client strips the leading "INBOX" for
> convience for the user. Possibly, you had mailbox prefix configured in
> your setup ago, which hid all mailboxes except "INBOX" and below. Perhaps
> you have entries in your subscriptions files, which are no longer
> available, because of the other setup.
>
> - --
> Steffen Kaiser
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
>
> iQEVAwUBWdX/3Hz1H7kL/d9rAQIwlQf+N29DnENf2hcXxBiYJdf+/rFpOtHPg5u0
> ml7VhtQSBRYk85x0xR/x16FMTqXM/IHRsIjjHwPbFVJ4lHdDJ3LHI4jnLy39v9qX
> oWjtlWDB88r6/MifJDxkgZXxBbih4tyqI0MNQRObt7mjLSF2POwSU90QZdeFAgCO
> 3hSooauYMjKCDOfBJpPNa8Uhs1RKw+70YMcgdWKwRZqPgQu5NoudU/5StAFe3cAx
> Oj4YJSn3NQI7cNLdr6R8Kv2wUbOnPhGvEQcn9NfnpbIROb5pG6Wu2plFmWRNmG9V
> XeTwtAarIeOHHonW4LNfx4hFPOo2APrm/NcnqDYSFOh14hap3NFGkQ==
> =oXNE
> -END PGP SIGNATURE-

Re: Issue with imap folder structure

[A.L.E.C]

On 05.10.2017 00:24, absolutely_f...@libero.it wrote:
> namespace {
> inbox = yes
> location =
> prefix = INBOX.
> separator = .
> type = private
> }

If you don't need INBOX.* folders then remove the above namespace
definition. Roundcube adds automatically the personal namespace prefix
to special folders.

-- 
Aleksander 'A.L.E.C' Machniak
Kolab Groupware Developer [http://kolab.org]
Roundcube Webmail Developer   [http://roundcube.net]

PGP: 19359DC1 # Blog: https://kolabian.wordpress.com

Re: Issue with imap folder structure

[Steffen Kaiser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, 5 Oct 2017, absolutely_f...@libero.it wrote:


I just migrated spool from another server (by copying filesystem, I use 
maildir), this is an example of mailbox's content:

drwx-- 5 postfix postfix 11 Sep 29 09:27 .Drafts
drwx-- 5 postfix postfix 9 Oct 4 10:18 .INBOX.Drafts
drwx-- 5 postfix postfix 9 Oct 4 10:18 .INBOX.Sent
drwx-- 5 postfix postfix 9 Oct 3 18:01 .INBOX.Trash
drwx-- 5 postfix postfix 12 Sep 29 09:27 .Junk
drwx-- 5 postfix postfix 8 Dec 9 2014 .Junk E-mail
drwx-- 5 postfix postfix 10 Oct 4 12:27 .Sent
drwx-- 5 postfix postfix 10 Oct 4 18:01 .Trash



-rw--- 1 postfix postfix 96 Oct 3 18:01 subscriptions



It seems I have duplicate folder (for example during webmail access, I use 
Roundcube).


You did not explain, which folders are duplicate.
Does "duplicate" mean, that they have the some content or just the same 
name? If copy one message into one folder, is it accessable through the 
other one?



What is wrong with my setup?


Well, you mean "Sent" and "INBOX.Sent", which latter is a mailbox named 
"Sent" as subfolder of INBOX, then they are not duplicates, but have the 
same name. Eventually, your mail client strips the leading "INBOX" for 
convience for the user. Possibly, you had mailbox prefix configured in 
your setup ago, which hid all mailboxes except "INBOX" and below. Perhaps 
you have entries in your subscriptions files, which are no longer 
available, because of the other setup.


- -- 
Steffen Kaiser

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEVAwUBWdX/3Hz1H7kL/d9rAQIwlQf+N29DnENf2hcXxBiYJdf+/rFpOtHPg5u0
ml7VhtQSBRYk85x0xR/x16FMTqXM/IHRsIjjHwPbFVJ4lHdDJ3LHI4jnLy39v9qX
oWjtlWDB88r6/MifJDxkgZXxBbih4tyqI0MNQRObt7mjLSF2POwSU90QZdeFAgCO
3hSooauYMjKCDOfBJpPNa8Uhs1RKw+70YMcgdWKwRZqPgQu5NoudU/5StAFe3cAx
Oj4YJSn3NQI7cNLdr6R8Kv2wUbOnPhGvEQcn9NfnpbIROb5pG6Wu2plFmWRNmG9V
XeTwtAarIeOHHonW4LNfx4hFPOo2APrm/NcnqDYSFOh14hap3NFGkQ==
=oXNE
-END PGP SIGNATURE-

Re: moving from mysql to pgsql

[Aki Tuomi]

On 05.10.2017 00:42, Noel Butler wrote:
> On 05/10/2017 02:06, Magnus wrote:
>
>> Hello,
>>
>> I hope that this mailing list is "alive", since I am looking for a solution 
>> for my problem for a long time.
>>
>> I would like to migrate my existing dovecot installation from mysql to 
>> pgsql. But I have problems with the passwords when using pgsql.
>>
>> The existing and working mysql-based installation looks like this:
>>
>> dovecot-sql.conf.ext:
>>
>> driver = mysql
>> default_pass_scheme = SHA512-CRYPT

This only means the assumed credentials scheme, not the one that gets
created.

>> Users are created like this:
>>
>> INSERT INTO mls_user (idx,domain,password,email)
>> VALUES (1,99,ENCRYPT('Test'),'m...@alpenjodel.de');
>>
>> This setup is working, which I can verify like this:
>>
>> $ telnet localhost 143
>> * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID
>> ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5
>> AUTH=CRAM-MD5] Dovecot ready.
>>
>> a login m...@alpenjodel.de Test
>> OK
>>
>> Now let's take a look at the pgsql version of the setup:
>>
>> dovecot-sql.conf.ext:
>>
>> driver = pgsql
>> default_pass_scheme = SHA512-CRYPT
>>
>> Users are created like this:
>>
>> INSERT INTO mls_user (idx,domain,password,email)
>> VALUES (1,99,crypt('Test',gen_salt('des')),'m...@alpenjodel.de');

This does indeed generate a DES based password, which isn't SHA512-CRYPT.

>> This setup is not working:
>>
>> $ telnet localhost 143
>> * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID
>> ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5
>> AUTH=CRAM-MD5] Dovecot ready.
>>
>> a login m...@alpenjodel.de Test
>> a NO [AUTHENTICATIONFAILED] Authentication failed.
>>
>> Assumptions:
>>
>> - I believe that the mysql encrypt function uses the crypt system call,
>> which in turn uses the DES algorithm with a random salt.
>>
>> - I believe that the same is done with the pgsql function call
>> crypt('Test',gen_salt('des')).
>>
>> But obviously some of these assumptions must be wrong.
>>
>> Besides that, the variable "default_pass_scheme" is set to "SHA512-CRYPT" in 
>> both cases. But obviously, not SHA but DES is used by the working 
>> mysql-based setup. I don't understand that. Could someone please explain the 
>> relationship between the default_pass_scheme variable and the 
>> encryption/hashing algorithm used to store the user passwords?
>>
>> And finally: What can I do to migrate to pgsql?
>>
>> Thank you
>> Magnus
> Migrate? if the passwords are truly as designed already, it shouldnt
> matter, it should read them, be it for mail, ftp, or httpd, they all
> read the same thing mysql, or anything that reads sha512. 
>
> What are you using to insert users, php? perl? , what does the database
> entry look like? 
>
> We use a perl backend to add members and hosts, in mysql mypassword
> field is populated ascrypt($password, '$6$' . $salt) 
>
> I can't help you if its php, i'll leave that for someone who knows php
> and my php guru is off sick this week with the flu 
>
> But does your database password field entry start with $6$ ? 
> perhaps your mysql isnt using what you think? 
>
>  As a test, this istesting123 in sha512 
>
> $6$Z6I5oyWUed.tmNUs$0ScF2w3ejPWFAX/3F6DgMyWpbXLq0DD6blL8rwBpSHGWaZ9RiXlpo5PPZFoJPZWIuQMETELsXG2YtbsAc8K3q/
>
>
> copy and paste that into a test users mysql password field directly, and
> your pgsql directly and see if it works. 
>
> incidentally, we use
>
> default_pass_scheme = CRYPT 
This is good way to support various versions what crypt(3) produces.

> Which handles all the subsystems crypt options including sha's -
> providing your system is half modern, if its ten years old dont use
> that, it'll be likely using the old 8 char limited crypt :)   (and dont
> laugh the number of antique debian and RH boxes I've come across is
> scary) 
>
> anyway, so even as a fallback for testing you could insert even an md5
> hash into a password field and it will work as well, I wont tell you not
> to do this in production because of course you know better ;)
>
Aki