postfixadmin-tracker — Postfix Admin tracker notification - READ ONLY!

[postfixadmin:bugs] Re: #373 PostfixAdmin Problem with MySQL strict mode

[Mohammad m. <mo...@us...>]

Thank you my problem was same as Oliver and now it is solved. ;D


---

** [bugs:#373] PostfixAdmin Problem with MySQL strict mode**

**Status:** closed-fixed
**Group:** SVN (please specify revision!)
**Created:** Sun Apr 24, 2016 09:12 AM UTC by Oliver Busch
**Last Updated:** Sat Apr 13, 2019 06:11 PM UTC
**Owner:** nobody


Hi,

I use Postfixadmin 2.93 and PHP 7 with MySQL 5.7. If I open setup.php I have these errors:


DEBUG INFORMATION:
Invalid query: Duplicate column name 'interval_time'

DEBUG INFORMATION:
Invalid query: Invalid default value for 'created' 



updating to version 1 (MySQL)...

CREATE TABLE IF NOT EXISTS admin ( `username` varchar(255) NOT NULL default '', `password` varchar(255) NOT NULL default '', `created` datetime NOT NULL default '0000-00-00 00:00:00', `modified` datetime NOT NULL default '0000-00-00 00:00:00', `active` tinyint(1) NOT NULL default '1', PRIMARY KEY (`username`) ) ENGINE=MyISAM COMMENT='Postfix Admin - Virtual Admins';

CREATE TABLE IF NOT EXISTS config ( `id` int(11) not null auto_increment primary key, `name` VARCHAR(20) /*!40100 CHARACTER SET latin1 */ NOT NULL DEFAULT '', `value` VARCHAR(20) /*!40100 CHARACTER SET latin1 */ NOT NULL DEFAULT '', UNIQUE name ( `name` ) ) ENGINE = MYISAM COMMENT = 'PostfixAdmin settings'

Updating database:

- old version: 0; target version: 1795


Where is my mistake? I hope you can help me! At the moment I have no mailflow

Best regards,

Oliver


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:bugs] Re: #373 PostfixAdmin Problem with MySQL strict mode

[Klaus <mos...@us...>]

Sry, its updated and running but I have anoter installation where I'll try the git version but can take a while till I'm doing this upgrade


---

** [bugs:#373] PostfixAdmin Problem with MySQL strict mode**

**Status:** closed-fixed
**Group:** SVN (please specify revision!)
**Created:** Sun Apr 24, 2016 09:12 AM UTC by Oliver Busch
**Last Updated:** Sat Apr 13, 2019 09:45 AM UTC
**Owner:** nobody


Hi,

I use Postfixadmin 2.93 and PHP 7 with MySQL 5.7. If I open setup.php I have these errors:


DEBUG INFORMATION:
Invalid query: Duplicate column name 'interval_time'

DEBUG INFORMATION:
Invalid query: Invalid default value for 'created' 



updating to version 1 (MySQL)...

CREATE TABLE IF NOT EXISTS admin ( `username` varchar(255) NOT NULL default '', `password` varchar(255) NOT NULL default '', `created` datetime NOT NULL default '0000-00-00 00:00:00', `modified` datetime NOT NULL default '0000-00-00 00:00:00', `active` tinyint(1) NOT NULL default '1', PRIMARY KEY (`username`) ) ENGINE=MyISAM COMMENT='Postfix Admin - Virtual Admins';

CREATE TABLE IF NOT EXISTS config ( `id` int(11) not null auto_increment primary key, `name` VARCHAR(20) /*!40100 CHARACTER SET latin1 */ NOT NULL DEFAULT '', `value` VARCHAR(20) /*!40100 CHARACTER SET latin1 */ NOT NULL DEFAULT '', UNIQUE name ( `name` ) ) ENGINE = MYISAM COMMENT = 'PostfixAdmin settings'

Updating database:

- old version: 0; target version: 1795


Where is my mistake? I hope you can help me! At the moment I have no mailflow

Best regards,

Oliver


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:bugs] #373 PostfixAdmin Problem with MySQL strict mode

[GingerDog <gin...@us...>]

Please can you try the latest version from https://github.com/postfixadmin/postfixadmin - or at least one of the recent releases - https://github.com/postfixadmin/postfixadmin/releases



---

** [bugs:#373] PostfixAdmin Problem with MySQL strict mode**

**Status:** closed-fixed
**Group:** SVN (please specify revision!)
**Created:** Sun Apr 24, 2016 09:12 AM UTC by Oliver Busch
**Last Updated:** Fri Apr 12, 2019 10:41 PM UTC
**Owner:** nobody


Hi,

I use Postfixadmin 2.93 and PHP 7 with MySQL 5.7. If I open setup.php I have these errors:


DEBUG INFORMATION:
Invalid query: Duplicate column name 'interval_time'

DEBUG INFORMATION:
Invalid query: Invalid default value for 'created' 



updating to version 1 (MySQL)...

CREATE TABLE IF NOT EXISTS admin ( `username` varchar(255) NOT NULL default '', `password` varchar(255) NOT NULL default '', `created` datetime NOT NULL default '0000-00-00 00:00:00', `modified` datetime NOT NULL default '0000-00-00 00:00:00', `active` tinyint(1) NOT NULL default '1', PRIMARY KEY (`username`) ) ENGINE=MyISAM COMMENT='Postfix Admin - Virtual Admins';

CREATE TABLE IF NOT EXISTS config ( `id` int(11) not null auto_increment primary key, `name` VARCHAR(20) /*!40100 CHARACTER SET latin1 */ NOT NULL DEFAULT '', `value` VARCHAR(20) /*!40100 CHARACTER SET latin1 */ NOT NULL DEFAULT '', UNIQUE name ( `name` ) ) ENGINE = MYISAM COMMENT = 'PostfixAdmin settings'

Updating database:

- old version: 0; target version: 1795


Where is my mistake? I hope you can help me! At the moment I have no mailflow

Best regards,

Oliver


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:bugs] #373 PostfixAdmin Problem with MySQL strict mode

[Klaus <mos...@us...>]

Issue still there (just upgraded from 14.04 to 16.04) - disable strict mode made it for me (https://www.linode.com/community/questions/17070/how-can-i-disable-mysql-strict-mode)


---

** [bugs:#373] PostfixAdmin Problem with MySQL strict mode**

**Status:** closed-fixed
**Group:** SVN (please specify revision!)
**Created:** Sun Apr 24, 2016 09:12 AM UTC by Oliver Busch
**Last Updated:** Tue Mar 13, 2018 10:04 AM UTC
**Owner:** nobody


Hi,

I use Postfixadmin 2.93 and PHP 7 with MySQL 5.7. If I open setup.php I have these errors:


DEBUG INFORMATION:
Invalid query: Duplicate column name 'interval_time'

DEBUG INFORMATION:
Invalid query: Invalid default value for 'created' 



updating to version 1 (MySQL)...

CREATE TABLE IF NOT EXISTS admin ( `username` varchar(255) NOT NULL default '', `password` varchar(255) NOT NULL default '', `created` datetime NOT NULL default '0000-00-00 00:00:00', `modified` datetime NOT NULL default '0000-00-00 00:00:00', `active` tinyint(1) NOT NULL default '1', PRIMARY KEY (`username`) ) ENGINE=MyISAM COMMENT='Postfix Admin - Virtual Admins';

CREATE TABLE IF NOT EXISTS config ( `id` int(11) not null auto_increment primary key, `name` VARCHAR(20) /*!40100 CHARACTER SET latin1 */ NOT NULL DEFAULT '', `value` VARCHAR(20) /*!40100 CHARACTER SET latin1 */ NOT NULL DEFAULT '', UNIQUE name ( `name` ) ) ENGINE = MYISAM COMMENT = 'PostfixAdmin settings'

Updating database:

- old version: 0; target version: 1795


Where is my mistake? I hope you can help me! At the moment I have no mailflow

Best regards,

Oliver


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:bugs] #386 Alias CSV Export

[GingerDog <gin...@us...>]

try https://github.com/postfixadmin/postfixadmin/commit/a981ff81723e90814396ef27f88ddcc9a21e0332 then.


---

** [bugs:#386] Alias CSV Export**

**Status:** open
**Group:** v3.0
**Created:** Sat Nov 05, 2016 10:17 PM UTC by Rob
**Last Updated:** Tue Jul 10, 2018 07:59 AM UTC
**Owner:** nobody


From the virtual-list.php if I click to Download List as CSV postfixadmin/list.php?table=alias&output=csv
The CSV is not the expected data.

I get this:

" ";Alias;To;"Deliver to the local mailbox.";"Auto Response";"Last modified";Active
"<span style='background-color:tomato'>  </span>          ";ab...@ex...;Array;0;0;2016-10-12;1




---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:bugs] #386 Alias CSV Export

[GingerDog <gin...@us...>]

CSV -> **comma** seperated values ... ;-) 
fputcsv defaults to a ',' between fields, and I see no advantage to choosing e.g. ';' 

You can safely put ',' within fields, they just get quoted. I'd use a ',' as it is a list afterall.


---

** [bugs:#386] Alias CSV Export**

**Status:** open
**Group:** v3.0
**Created:** Sat Nov 05, 2016 10:17 PM UTC by Rob
**Last Updated:** Tue Jul 10, 2018 01:13 AM UTC
**Owner:** nobody


From the virtual-list.php if I click to Download List as CSV postfixadmin/list.php?table=alias&output=csv
The CSV is not the expected data.

I get this:

" ";Alias;To;"Deliver to the local mailbox.";"Auto Response";"Last modified";Active
"<span style='background-color:tomato'>  </span>          ";ab...@ex...;Array;0;0;2016-10-12;1




---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:bugs] #386 Alias CSV Export

[Christian B. <chr...@us...>]

The CSV delimiter is completely unrelated, and I'll revert the commit in a minute to avoid a superfluous behaviour / file format change ;-)

The problem is that AliasHandler returns an array with the alias targets, and when writing the CSV file, that array gets written as literal "Array" instead of writing the array content (= the list of alias targets) into the CSV.

The solution is to convert the array to a string using join(). A good place is probably list.php around line 117, where we'll need an if condition to check for the field type.

I'm a bit unsure what character I should use as delimiter between multiple alias targets - candidates are "," or a space. Opinions?


---

** [bugs:#386] Alias CSV Export**

**Status:** open
**Group:** v3.0
**Created:** Sat Nov 05, 2016 10:17 PM UTC by Rob
**Last Updated:** Mon Jul 09, 2018 07:23 PM UTC
**Owner:** nobody


From the virtual-list.php if I click to Download List as CSV postfixadmin/list.php?table=alias&output=csv
The CSV is not the expected data.

I get this:

" ";Alias;To;"Deliver to the local mailbox.";"Auto Response";"Last modified";Active
"<span style='background-color:tomato'>  </span>          ";ab...@ex...;Array;0;0;2016-10-12;1




---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:bugs] #386 Alias CSV Export

[GingerDog <gin...@us...>]

I think the problem is just that someone chose ';' to be the record delimiter - rather than the more standard ',' - see https://github.com/postfixadmin/postfixadmin/commit/c5c42cfbe88904ee9b7682fb6dd6b9cebc28130d which might fix it for you


---

** [bugs:#386] Alias CSV Export**

**Status:** open
**Group:** v3.0
**Created:** Sat Nov 05, 2016 10:17 PM UTC by Rob
**Last Updated:** Fri Jun 29, 2018 03:04 PM UTC
**Owner:** nobody


From the virtual-list.php if I click to Download List as CSV postfixadmin/list.php?table=alias&output=csv
The CSV is not the expected data.

I get this:

" ";Alias;To;"Deliver to the local mailbox.";"Auto Response";"Last modified";Active
"<span style='background-color:tomato'>  </span>          ";ab...@ex...;Array;0;0;2016-10-12;1




---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:bugs] #386 Alias CSV Export

[nicthequick <nic...@us...>]

This is still an issue.


---

** [bugs:#386] Alias CSV Export**

**Status:** open
**Group:** v3.0
**Created:** Sat Nov 05, 2016 10:17 PM UTC by Rob
**Last Updated:** Sat Nov 05, 2016 10:17 PM UTC
**Owner:** nobody


From the virtual-list.php if I click to Download List as CSV postfixadmin/list.php?table=alias&output=csv
The CSV is not the expected data.

I get this:

" ";Alias;To;"Deliver to the local mailbox.";"Auto Response";"Last modified";Active
"<span style='background-color:tomato'>  </span>          ";ab...@ex...;Array;0;0;2016-10-12;1




---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:feature-requests] #119 OTP Authentication Web-Interface

[James B. <jlb...@us...>]

Yes! Please add this.

Have just setup TOTP with Roundcube Mail - they have a plugin (https://plugins.roundcube.net/packages/alexandregz/twofactor_gauthenticator). Something like that for Postfix Admin would be perfect.


---

** [feature-requests:#119] OTP Authentication Web-Interface**

**Status:** open
**Group:** SVN (please specify revision!)
**Created:** Tue Mar 10, 2015 08:54 AM UTC by jbacksch
**Last Updated:** Tue Mar 10, 2015 08:54 AM UTC
**Owner:** Christian Boltz


Add (T)OTP Authentication to Web-Interface based on RFC 6238 e.g. working with FreeOTP


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:patches] #121 multiple hash algorithms using system's crypt in pacrypt

[Christian B. <chr...@us...>]

- **status**: open --> closed-fixed
- **Comment**:

PostfixAdmin 3.2 (which we just released) supports $CONF['encrypt'] = 'php_crypt:$METHOD'



---

** [patches:#121] multiple hash algorithms using system's crypt in pacrypt**

**Status:** closed-fixed
**Group:** SVN (please specify revision!)
**Created:** Fri Aug 30, 2013 11:34 AM UTC by Magnus Stenman
**Last Updated:** Tue Mar 07, 2017 01:24 AM UTC
**Owner:** nobody
**Attachments:**

- [functions.inc.php.patch](https://sourceforge.net/p/postfixadmin/patches/121/attachment/functions.inc.php.patch) (2.8 kB; text/x-diff)


This patch adds another $CONF['encrypt'] type, 'php_crypt', which uses the PHP crypt() function, which in turn uses the system's crypt() (much like the current 'system' type in postfixadmin-2.3.6)

The difference to the current 'system' type is that you can choose which hash type you want to use for new passwords. (currently DES, MD5, Blowfish, SHA256, SHA512; defaults to )

The current 'system' type only generates MD5 hashes with 2-character salt.


I do not have 'dovecotpw' on my system so that was not an option.

It does not interfere with existing 'encrypt' types, but could be incorporated into the 'system' type.
Tested on CentOS 5 and 6, Dovecot 2 and Postfix.


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/patches/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/patches/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:bugs] #280 Several issues with pacrypt() [remaining: part 1.]

[Christian B. <chr...@us...>]

- **status**: open --> closed-fixed



---

** [bugs:#280] Several issues with pacrypt() [remaining: part 1.]**

**Status:** closed-fixed
**Group:** v2.3.5
**Labels:** Core 
**Created:** Wed Oct 10, 2012 11:20 AM UTC by Martijn
**Last Updated:** Wed May 02, 2018 11:09 PM UTC
**Owner:** nobody


I would like to bring to your attention what I think are several \(related\) issues with pacrypt\(\). Simply skip to "Issues" if you're in a hurry ;-\)

Situation: currently I'm working on a virtual mail system based on
\- Postfix \(2.7.x\) as SMTP only, no LDA
\- Dovecot \(1.x\) as LDA / POP3 / IMAP
\- Postfixadmin for simple mailbox management

The data on this system will be coming from an older platform, which uses crypt-md5 \($1$...\) salted hashed passwords. For newly made accounts we intent to use the superiour SHA-512 \($6$...\) instead. Together with the $version$-strings in crypt\(\)'s hashes, this provides for an excellent way to gradually upgrade everyone to the stronger hash:
\- Accounts with older passwords are still able to log in.
\- New accounts or account that have their password changed will be given the stronger SHA-512 hash and profit from better hashing.

Now, let's see about the availability of SHA-512 in the surrounding systems:
\- Dovecot 1.x password scheme 'CRYPT' will support all the hashing methods available to crypt\(\) from glibc on the system, according to http://wiki.dovecot.org/Authentication/PasswordSchemes - For a system with glibc v2.7+, this usually means SHA-256 \($5$...\) and \(our choice\) SHA-512 are available.

\- For upgraders, Dovecot 2.x will support 'SHA512-CRYPT' - http://wiki2.dovecot.org/Authentication/PasswordSchemes

\- For PHP it's pretty much the same thing: http://php.net/manual/en/function.crypt.php - for PHP < 5.3.0 it can use what's available in glibc, and for > 5.3.0 it uses it's own implementation if glibc lacks support.

\- Postfix is a bit of a question mark for me. I've seen examples that used MySQL's encrypt\(\) to match the password, which makes for a 30+ year old Standard DES hash... I figured the same could work with a non-crypt non-salted MD5\(\) in MySQL. I've also seen hashmaps built from plaintext. None of those options are very encouraging imho. In our case however, it won't matter since SMTP-AUTH on Postfix can use "smtpd\_sasl\_type = dovecot". In other words: Postfix will ask Dovecot if the SMTP-AUTH password is correct and not even try to figure it out by itself ;-\)

Summing it up, this looks like we're pretty much safe to use SHA-512 hashes on the main software, now what about Postfixadmin? I've set up my 2.3.5 installation and configured my $CONF\['crypt'\] to be 'system' as that seemed like the closest option to crypt\(\) for me.

Issues:
1\. The config mentions that 'system' is 'whatever you have set as your PHP system default'. But PHP doesn't really have a system default for that, or at least not one that can be set by the user. What PHP's crypt\(\) will be using automatically seems to be defined by what's likely to be compatible, instead of what's safe. And before actually generating a hash, I don't believe it's possible to see which of the hashing methods crypt\(\) is going to choose. In my tests on a modern Ubuntu system with PHP 5.3.x, calling crypt\(\) without pre-setup \(like '$6$rounds=5000$\[...salt...\]$\) salt provides me with a Standard DES hash, just the least it can do.

To force PHP crypt\(\) to generate a \(new\) SHA-512 password we must provide it with a pre-setup version string and salt. This has to be configurable in Postfixadmin. The configured hashing method should only be forced on hashes we're newly creating, and not on password checking: crypt\(\) will already take care of that \(see my second point below\).

This way, 'system' is compatible with checking all versions of crypt\(\) hashes in the database, and chooses the preferred hashing method for new accounts.

2\. After putting some SHA-512 hashes into the database, I noticed Postfixadmin has trouble reading the passwords although it is using crypt\(\) to check. I had a look at the loop that's used for 'system' but I can't figure out what it's supposed to do exactly. For what I can tell, it can only do crypt-md5, which would make it equal to the seperately configurable 'crypt-md5' in config.inc.php.

If you want to check a password with PHP crypt\(\), just feed it the entire password from the database. crypt\(\) will extract the salt automatically and then use it to hash the provided password from the first function argument. This would make all the code needed just for checking a password for 'system' like this:

if \(strlen\($pw\_db\) \!== 0\) \{
$password = crypt\($pw, $pw\_db\);
\} \[...\]
return $password;

For generating a new password with a specific hash method, a setting should be used.

Summing up 1 and 2, a start for a backwards compatible patch is included. It could use some more refining. I haven't tested it thoroughly, but it does work well on my data. It currently misses support for extended DES \(old\) and blowfish \(recommended\), and also I don't check on the variables indicating whether or not a hashing method is available in PHP since I didn't see an easy way to bring that error to the user. But it's a start.

3\. Please do not escape passwords before hashing them ;-\) I noticed this was reported and also reported fixed so no need to get into that.

Unrelated:
4\. The minimum password length seems to be enforced when changing the password only, not when creating an admin or mailbox. Is this intended behaviour?


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:bugs] #280 Several issues with pacrypt() [remaining: part 1.]

[Christian B. <chr...@us...>]

PostfixAdmin 3.2 (which we just released) supports $CONF['encrypt'] = 'php_crypt:$METHOD'


---

** [bugs:#280] Several issues with pacrypt() [remaining: part 1.]**

**Status:** open
**Group:** v2.3.5
**Labels:** Core 
**Created:** Wed Oct 10, 2012 11:20 AM UTC by Martijn
**Last Updated:** Thu Aug 21, 2014 11:19 PM UTC
**Owner:** nobody


I would like to bring to your attention what I think are several \(related\) issues with pacrypt\(\). Simply skip to "Issues" if you're in a hurry ;-\)

Situation: currently I'm working on a virtual mail system based on
\- Postfix \(2.7.x\) as SMTP only, no LDA
\- Dovecot \(1.x\) as LDA / POP3 / IMAP
\- Postfixadmin for simple mailbox management

The data on this system will be coming from an older platform, which uses crypt-md5 \($1$...\) salted hashed passwords. For newly made accounts we intent to use the superiour SHA-512 \($6$...\) instead. Together with the $version$-strings in crypt\(\)'s hashes, this provides for an excellent way to gradually upgrade everyone to the stronger hash:
\- Accounts with older passwords are still able to log in.
\- New accounts or account that have their password changed will be given the stronger SHA-512 hash and profit from better hashing.

Now, let's see about the availability of SHA-512 in the surrounding systems:
\- Dovecot 1.x password scheme 'CRYPT' will support all the hashing methods available to crypt\(\) from glibc on the system, according to http://wiki.dovecot.org/Authentication/PasswordSchemes - For a system with glibc v2.7+, this usually means SHA-256 \($5$...\) and \(our choice\) SHA-512 are available.

\- For upgraders, Dovecot 2.x will support 'SHA512-CRYPT' - http://wiki2.dovecot.org/Authentication/PasswordSchemes

\- For PHP it's pretty much the same thing: http://php.net/manual/en/function.crypt.php - for PHP < 5.3.0 it can use what's available in glibc, and for > 5.3.0 it uses it's own implementation if glibc lacks support.

\- Postfix is a bit of a question mark for me. I've seen examples that used MySQL's encrypt\(\) to match the password, which makes for a 30+ year old Standard DES hash... I figured the same could work with a non-crypt non-salted MD5\(\) in MySQL. I've also seen hashmaps built from plaintext. None of those options are very encouraging imho. In our case however, it won't matter since SMTP-AUTH on Postfix can use "smtpd\_sasl\_type = dovecot". In other words: Postfix will ask Dovecot if the SMTP-AUTH password is correct and not even try to figure it out by itself ;-\)

Summing it up, this looks like we're pretty much safe to use SHA-512 hashes on the main software, now what about Postfixadmin? I've set up my 2.3.5 installation and configured my $CONF\['crypt'\] to be 'system' as that seemed like the closest option to crypt\(\) for me.

Issues:
1\. The config mentions that 'system' is 'whatever you have set as your PHP system default'. But PHP doesn't really have a system default for that, or at least not one that can be set by the user. What PHP's crypt\(\) will be using automatically seems to be defined by what's likely to be compatible, instead of what's safe. And before actually generating a hash, I don't believe it's possible to see which of the hashing methods crypt\(\) is going to choose. In my tests on a modern Ubuntu system with PHP 5.3.x, calling crypt\(\) without pre-setup \(like '$6$rounds=5000$\[...salt...\]$\) salt provides me with a Standard DES hash, just the least it can do.

To force PHP crypt\(\) to generate a \(new\) SHA-512 password we must provide it with a pre-setup version string and salt. This has to be configurable in Postfixadmin. The configured hashing method should only be forced on hashes we're newly creating, and not on password checking: crypt\(\) will already take care of that \(see my second point below\).

This way, 'system' is compatible with checking all versions of crypt\(\) hashes in the database, and chooses the preferred hashing method for new accounts.

2\. After putting some SHA-512 hashes into the database, I noticed Postfixadmin has trouble reading the passwords although it is using crypt\(\) to check. I had a look at the loop that's used for 'system' but I can't figure out what it's supposed to do exactly. For what I can tell, it can only do crypt-md5, which would make it equal to the seperately configurable 'crypt-md5' in config.inc.php.

If you want to check a password with PHP crypt\(\), just feed it the entire password from the database. crypt\(\) will extract the salt automatically and then use it to hash the provided password from the first function argument. This would make all the code needed just for checking a password for 'system' like this:

if \(strlen\($pw\_db\) \!== 0\) \{
$password = crypt\($pw, $pw\_db\);
\} \[...\]
return $password;

For generating a new password with a specific hash method, a setting should be used.

Summing up 1 and 2, a start for a backwards compatible patch is included. It could use some more refining. I haven't tested it thoroughly, but it does work well on my data. It currently misses support for extended DES \(old\) and blowfish \(recommended\), and also I don't check on the variables indicating whether or not a hashing method is available in PHP since I didn't see an easy way to bring that error to the user. But it's a start.

3\. Please do not escape passwords before hashing them ;-\) I noticed this was reported and also reported fixed so no need to get into that.

Unrelated:
4\. The minimum password length seems to be enforced when changing the password only, not when creating an admin or mailbox. Is this intended behaviour?


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:patches] #136 Vacation.pl relies upon deprecated Mail::Sender

[Christian B. <chr...@us...>]

- **status**: open --> closed-fixed



---

** [patches:#136] Vacation.pl relies upon deprecated Mail::Sender**

**Status:** closed-fixed
**Group:** SVN (please specify revision!)
**Created:** Fri Dec 02, 2016 03:06 PM UTC by Sylvain Tissot
**Last Updated:** Thu Dec 28, 2017 10:35 AM UTC
**Owner:** nobody


The `Mail::Sender` Perl module used to send the vacation email is [deprecated](http://matrix.cpantesters.org/?dist=Mail-Sender) and should be replacd by `Email::Sender::Simple`


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/patches/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/patches/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:bugs] #373 PostfixAdmin Problem with MySQL strict mode

[Alexey <vol...@us...>]

Well, it doesn't work for me even with v3.1. The same error still exists. Any advices?


---

** [bugs:#373] PostfixAdmin Problem with MySQL strict mode**

**Status:** closed-fixed
**Group:** SVN (please specify revision!)
**Created:** Sun Apr 24, 2016 09:12 AM UTC by Oliver Busch
**Last Updated:** Tue Nov 01, 2016 08:34 PM UTC
**Owner:** nobody


Hi,

I use Postfixadmin 2.93 and PHP 7 with MySQL 5.7. If I open setup.php I have these errors:


DEBUG INFORMATION:
Invalid query: Duplicate column name 'interval_time'

DEBUG INFORMATION:
Invalid query: Invalid default value for 'created' 



updating to version 1 (MySQL)...

CREATE TABLE IF NOT EXISTS admin ( `username` varchar(255) NOT NULL default '', `password` varchar(255) NOT NULL default '', `created` datetime NOT NULL default '0000-00-00 00:00:00', `modified` datetime NOT NULL default '0000-00-00 00:00:00', `active` tinyint(1) NOT NULL default '1', PRIMARY KEY (`username`) ) ENGINE=MyISAM COMMENT='Postfix Admin - Virtual Admins';

CREATE TABLE IF NOT EXISTS config ( `id` int(11) not null auto_increment primary key, `name` VARCHAR(20) /*!40100 CHARACTER SET latin1 */ NOT NULL DEFAULT '', `value` VARCHAR(20) /*!40100 CHARACTER SET latin1 */ NOT NULL DEFAULT '', UNIQUE name ( `name` ) ) ENGINE = MYISAM COMMENT = 'PostfixAdmin settings'

Updating database:

- old version: 0; target version: 1795


Where is my mistake? I hope you can help me! At the moment I have no mailflow

Best regards,

Oliver


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:patches] #10 simple python vacation script

[Christian B. <chr...@us...>]

- **status**: open --> closed-rejected
- **Group**:  --> SVN (please specify revision!)
- **Comment**:

Given there was no reaction to the SQL injection comment since years, I'll reject this.

I'm not completely opposed to a python-based vacation script (actually I prefer python over perl), but it has to be a full replacement so that we can drop vacation.pl (we are not bored enough to maintain two vacation scripts). If you or someone else has such a python script, feel free to open a pull request on github.



---

** [patches:#10] simple python vacation script**

**Status:** closed-rejected
**Group:** SVN (please specify revision!)
**Created:** Sat Aug 18, 2007 08:53 AM UTC by Thomas Witzenrath
**Last Updated:** Wed Jan 23, 2013 12:48 PM UTC
**Owner:** nobody


Hi,

since the vacation.pl distributed with postfixadmin is broken, i rewrote the whole thing in python.

Features:

\* loop detection
\* Uses Sender:-Header if present
\* rejects multiple Adresses in From:-Header, but replies to Sender: or Reply-To: if present
\* Does not answer to Spam-Messages \(checks for X-Spam-Status\)
\* Does not answer to Precedence: \[bulk|list|junk\]
\* Does not send notifications to people that have been notified in the last week
\* writes messages to logfile
\* logs errors to errorlog, or if all else fails, tries to send a message to an administrator


Limits:

\* So far only support for Postgres, but changing this to MySQL should be as easy as changing two lines of code \(line 20 and 40\).
\*relies on postfix handing in the recipients e-mail address, so you have to change master.cf like this:

vacation                unix    -       n       n       -       -       pipe
flags=DRhu user=vacation argv=/var/spool/vacation/vacation.py $\{user\}


\* based on the gentoo-wiki tablelayout, which I am not sure is the same as is propagated through postfixadmin \(but I think it should\):

Table "public.vacation"
Column  |           Type           |               Modifiers
\----------+--------------------------+----------------------------------------
email    | character varying\(255\)   | not null default ''::character varying
subject  | character varying\(255\)   | not null default ''::character varying
body     | text                     | not null
cache    | text                     |
domain   | character varying\(255\)   | not null default ''::character varying
created  | timestamp with time zone | default now\(\)
modified | timestamp with time zone | default now\(\)
active   | boolean                  | not null default true
Indexes:
"vacation\_key" PRIMARY KEY, btree \(email\)


Table "public.vacation\_notification"
Column    |           Type           |       Modifiers
\-------------+--------------------------+------------------------
on\_vacation | character varying\(255\)   | not null
notified    | character varying\(255\)   | not null
notified\_at | timestamp with time zone | not null default now\(\)
Indexes:
"vacation\_notification\_pkey" PRIMARY KEY, btree \(on\_vacation, notified\)
Foreign-key constraints:
"vacation\_notification\_on\_vacation\_fkey" FOREIGN KEY \(on\_vacation\) REFERENCES vacation\(email\) ON DELETE CASCADE



only limited testing has been done, friendly bug reports are welcome\!





---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/patches/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/patches/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:patches] #9 simple PHP vacation script

[Christian B. <chr...@us...>]

- **status**: open --> closed-rejected
- **Group**:  --> SVN (please specify revision!)
- **Comment**:

Given the limitations, I'm afraid that this script has no chances to replace vacation.pl - and we aren't bored enough to maintain multiple vacation scripts ;-)



---

** [patches:#9] simple PHP vacation script**

**Status:** closed-rejected
**Group:** SVN (please specify revision!)
**Labels:** Vacation 
**Created:** Thu Jul 12, 2007 12:19 AM UTC by John Seifarth
**Last Updated:** Mon Aug 25, 2014 07:35 AM UTC
**Owner:** nobody


This is a simplistic vacation script for postfixadmin, written in PHP. 

Since postfix has already figured out who the sender is, and who the recipient is, we can use 
these values passed via the command line from the postfix pipe daemon process when our script 
is called. This avoids having to parse the email message itself, and vastly simplifies the 
program logic. It does impose some limitations, described below.

This version only supports the postgres backend database. It should be easy to adapt to mysql, 
by someone familiar with that database. Ideally, it should be database-independent.

The main design goal is extreme simplicity, with decent error checking, 
to avoid sending inappropriate vacation notifications.
It is much simpler than the vacation.pl script included with postfixadmin, since it does not 
have to parse the email headers to extract the sender and recipient.

However, it should be easily modifiable by anyone reasonably familiar with PHP.


Features:

\- Written entirely in simple, linear PHP. 

\- Error checking: at each step, if an error is encountered, the error is logged and the program exits

\- Relies on postfix for the sender and recipient address

\- Allows a time-based repeat policy for re-sending notifications. For example, it can be set to notify 
every 10 days, every day, or even every 1 second if you want a notification sent for each incoming 
mail from each sender.


Limits:

\* Postgres only, because I do not have a Mysql test DB.
I previously had the vacation-psql.pl script running when I was using postfix 2.2, but it stopped 
working when I upgraded to postfix 2.3 \(which I needed for working with dovecot SASL auth\). This 
vacation-psql.pl uses the vacation\_notification table to keep track of which senders have already 
received a vacation notification. I did not see this table used in the mysql vacation.pl script.

\* Does not attempt to find the actual address to which the mail was sent, it just uses the $\{recipient\} 
macro from the postfix pipe interface to find the recipient mailbox. Therefore, the return address of 
the vacation notification is that of the user's mailbox, not necessarily the address to which the 
sender originaly sent the email, which may well be an alias to that mailbox. My workaround for 
this limitation for users who have ab...@wh...d type addresses is to suggest that they put their 
usual address or their name in the subject line.




---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/patches/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/patches/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:patches] #136 Vacation.pl relies upon deprecated Mail::Sender

[Christoph L. <ib...@us...>]

Thanks!
I found out about that new vacation.pl an hour after my comment here, but I wasn't sure yet wether that replaces Sender.pm (and it was really late).
So this patch issue is obsolete now.


---

** [patches:#136] Vacation.pl relies upon deprecated Mail::Sender**

**Status:** open
**Group:** SVN (please specify revision!)
**Created:** Fri Dec 02, 2016 03:06 PM UTC by Sylvain Tissot
**Last Updated:** Thu Dec 28, 2017 09:12 AM UTC
**Owner:** nobody


The `Mail::Sender` Perl module used to send the vacation email is [deprecated](http://matrix.cpantesters.org/?dist=Mail-Sender) and should be replacd by `Email::Sender::Simple`


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/patches/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/patches/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:patches] #136 Vacation.pl relies upon deprecated Mail::Sender

[GingerDog <gin...@us...>]

see https://github.com/postfixadmin/postfixadmin/pull/61 - already fixed on github.


---

** [patches:#136] Vacation.pl relies upon deprecated Mail::Sender**

**Status:** open
**Group:** SVN (please specify revision!)
**Created:** Fri Dec 02, 2016 03:06 PM UTC by Sylvain Tissot
**Last Updated:** Wed Dec 27, 2017 09:10 PM UTC
**Owner:** nobody


The `Mail::Sender` Perl module used to send the vacation email is [deprecated](http://matrix.cpantesters.org/?dist=Mail-Sender) and should be replacd by `Email::Sender::Simple`


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/patches/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/patches/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:patches] #136 Vacation.pl relies upon deprecated Mail::Sender

[Christoph L. <ib...@us...>]

Unfortunately, in Debian stretch (comes with postfixadmin 3.0.2) the -X is not satisfying any more.
Our current "workaround" was to comment out some lines in Sender.pm.
Maybe I'll take on this task, but no promises yet.


---

** [patches:#136] Vacation.pl relies upon deprecated Mail::Sender**

**Status:** open
**Group:** SVN (please specify revision!)
**Created:** Fri Dec 02, 2016 03:06 PM UTC by Sylvain Tissot
**Last Updated:** Wed Feb 08, 2017 08:24 PM UTC
**Owner:** nobody


The `Mail::Sender` Perl module used to send the vacation email is [deprecated](http://matrix.cpantesters.org/?dist=Mail-Sender) and should be replacd by `Email::Sender::Simple`


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/patches/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/patches/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:feature-requests] #104 Drop support of Vacation in favor of SIEVE

[Mohammed Al-M. <eng...@us...>]

Hi,

Will this feature be supported soon? because we really need it.

All the best,
Mohammed


---

** [feature-requests:#104] Drop support of Vacation in favor of SIEVE **

**Status:** open
**Group:** 
**Labels:** Core 
**Created:** Fri Mar 02, 2012 04:42 PM UTC by Alexander
**Last Updated:** Tue Feb 03, 2015 08:18 AM UTC
**Owner:** nobody


I propose to drop support of "Vacation" in favor of standardized SIEVE \(RFC 3028, RFC 5230, RFC 5804, RFC 5435\) that support vacations auto-responder in addition to very powerful filtering mechanism.

SIEVE already supported in major email's clients \(Thunderbird, RoundCube, Horde and etc\) and allow much more flexibility to assign Vacation response\(it could be special rules to avoid respond to robots, or other auto-responders/notificators\)
SIEVE supported very well by well known Dovecot, Courier for a long time and actually it will be better to leave actual mail delivery to primary servers instead of custom, non standard Perl's spike.

So, IMHO it would be a good step forward in 3.x development to drop custom, non standard Vacation support in favor of supporting SIEVE language.

Since postfixadmin allows regular users to manage own settings, it will be good to implement in a future web based SIEVE's rules management via postfixadmin in manner as it done in INGO application from Horde framework for example that bring a lot of power to users and administrators to manage Vacation, Spam filtering, forwarding, black/white listing  and much more without actual need to learn SIEVE language...



---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:bugs] #300 Unable to connect on remote Mysql

[Erik <er...@us...>]

I think another solution could be to change following line in functions.inc.php (Version 3.1)

1274c1274
<             $link = @mysqli_connect ($CONF['database_host'], $CONF['database_user'], $CONF['database_password'], $CONF['database_name'], $CONF['database_port']) or $error_text .= ("<p />DEBUG INFORMATION:<br />Connect: " .  mysqli_connect_error () . "$DEBUG_TEXT");
---
>             $link = @mysqli_connect ($CONF['database_host'], $CONF['database_user'], $CONF['database_password']) or $error_text .= ("<p />DEBUG INFORMATION:<br />Connect: " .  mysqli_connect_error () . "$DEBUG_TEXT");

and use 

$CONF['database_type'] = 'mysqli';
$CONF['database_host'] = '127.0.0.1';
$CONF['database_port'] = '3308';

instead.


---

** [bugs:#300] Unable to connect on remote Mysql**

**Status:** open
**Group:** v2.3.6
**Created:** Mon Aug 05, 2013 06:31 PM UTC by Debux
**Last Updated:** Sat Aug 23, 2014 02:26 PM UTC
**Owner:** nobody


Hi everyone,

I try to connect postfixadmin on remote Mysql, but this error appears:

Error: Can't connect to database
Please edit the $CONF['database_*] parameters in config.inc.php

DEBUG INFORMATION:
Connect: Unknown MySQL server host '10.0.0.40:3308' (2) 

My config.inc.php:

$CONF['database_type'] = 'mysqli';
$CONF['database_host'] = '10.0.0.40:3308';
$CONF['database_user'] = 'postfixadmin';
$CONF['database_password'] = 'password';
$CONF['database_name'] = 'postfix';

When i try on shell with mysql command (mysql -h 10.0.0.40 -u postfixadmin -ppassword -D postfix -P 3308) the access works, someone know what might be happening?


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:bugs] Re: #319 dovecot:CRYPT-METHOD does not work

[Mario Y. <mar...@us...>]

Thank you very much. I did not realize there is a newer virsion.

Best regards,

On May 5, 2017 01:45, "Christian Boltz" <chr...@us...>
wrote:

> There's an easier solution - update to PostfixAdmin 3.0.x which already
> uses the '-t' option and is therefore able to handle most dovecot hashing
> methods (except a few where the username is mixed into the hash) ;-)
> ------------------------------
>
> * [bugs:#319] <https://sourceforge.net/p/postfixadmin/bugs/319/>
> dovecot:CRYPT-METHOD does not work*
>
> *Status:* closed-invalid
> *Group:* v2.91 (3.0 beta1)
> *Created:* Fri May 30, 2014 11:05 PM UTC by Paul
> *Last Updated:* Thu May 04, 2017 01:57 PM UTC
> *Owner:* nobody
>
> I have not been able to get dovecot:CRYPT-METHOD to work (tried
> SHA512-CRYPT, SHA256-CRYPT, MD5-CRYPT, and BLF-CRYPT, which I learned isn't
> supported in my OS). Using one results in the following error message when
> setting up admin account with setup.php:
>
> can't encrypt password with dovecotpw, see error log for details
>
> This is what the logs state:
> 1624#0: *6 FastCGI sent in stderr: "PHP message: dovecotpw password
> encryption failed.
>
> PHP message: STDERR output: sh: 1: /usr/sbin/doveadm: not found" while
> reading response header from upstream <...> upstream:
> "fastcgi://unix:/var/run/php5-fpm.sock:" <...>
>
> In config.inc.php I see:
>
> // If you use the dovecot encryption method: where is the dovecotpw binary
> located?
> // for dovecot 1.x
> // $CONF['dovecotpw'] = "/usr/sbin/dovecotpw";
> // for dovecot 2.x (dovecot 2.0.0 - 2.0.7 is not supported!)
> $CONF['dovecotpw'] = "/usr/sbin/doveadm pw";
>
> A couple quick checks:
> # ll /usr/sbin/doveadm
> -rwxr-xr-x 1 root root 423264 Feb 13 23:23 /usr/bin/doveadm*
>
> # doveadm pw -l
> CRYPT MD5 MD5-CRYPT SHA SHA1 SHA256 SHA512 SMD5 SSHA SSHA256 SSHA512 PLAIN
> CLEAR CLEARTEXT PLAIN-TRUNC CRAM-MD5 SCRAM-SHA-1 HMAC-MD5 DIGEST-MD5
> PLAIN-MD4 PLAIN-MD5 LDAP-MD5 LANMAN NTLM OTP SKEY RPA SHA256-CRYPT
> SHA512-CRYPT
>
> Using Dovecot 2.2, PHP 5.5, MariaDB 10, Postfix 2.11.
> ------------------------------
>
> Sent from sourceforge.net because you indicated interest in
> https://sourceforge.net/p/postfixadmin/bugs/319/
>
> To unsubscribe from further messages, please visit
> https://sourceforge.net/auth/subscriptions/
>



---

** [bugs:#319] dovecot:CRYPT-METHOD does not work**

**Status:** closed-invalid
**Group:** v2.91 (3.0 beta1)
**Created:** Fri May 30, 2014 11:05 PM UTC by Paul
**Last Updated:** Thu May 04, 2017 04:45 PM UTC
**Owner:** nobody


I have not been able to get dovecot:CRYPT-METHOD to work (tried SHA512-CRYPT, SHA256-CRYPT, MD5-CRYPT, and BLF-CRYPT, which I learned isn't supported in my OS). Using one results in the following error message when setting up admin account with setup.php:

can't encrypt password with dovecotpw, see error log for details

This is what the logs state:
1624#0: *6 FastCGI sent in stderr: "PHP message: dovecotpw password encryption failed.

PHP message: STDERR output: sh: 1: /usr/sbin/doveadm: not found" while reading response header from upstream <...> upstream: "fastcgi://unix:/var/run/php5-fpm.sock:" <...>

In config.inc.php I see:

// If you use the dovecot encryption method: where is the dovecotpw binary located?
// for dovecot 1.x
// $CONF['dovecotpw'] = "/usr/sbin/dovecotpw";
// for dovecot 2.x (dovecot 2.0.0 - 2.0.7 is not supported!)
$CONF['dovecotpw'] = "/usr/sbin/doveadm pw";

A couple quick checks:
\# ll /usr/sbin/doveadm
-rwxr-xr-x 1 root root 423264 Feb 13 23:23 /usr/bin/doveadm*

\# doveadm pw -l
CRYPT MD5 MD5-CRYPT SHA SHA1 SHA256 SHA512 SMD5 SSHA SSHA256 SSHA512 PLAIN CLEAR CLEARTEXT PLAIN-TRUNC CRAM-MD5 SCRAM-SHA-1 HMAC-MD5 DIGEST-MD5 PLAIN-MD4 PLAIN-MD5 LDAP-MD5 LANMAN NTLM OTP SKEY RPA SHA256-CRYPT SHA512-CRYPT


Using Dovecot 2.2, PHP 5.5, MariaDB 10, Postfix 2.11.


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:bugs] #319 dovecot:CRYPT-METHOD does not work

[Christian B. <chr...@us...>]

There's an easier solution - update to PostfixAdmin 3.0.x which already uses the '-t' option and is therefore able to handle most dovecot hashing methods (except a few where the username is mixed into the hash) ;-)


---

** [bugs:#319] dovecot:CRYPT-METHOD does not work**

**Status:** closed-invalid
**Group:** v2.91 (3.0 beta1)
**Created:** Fri May 30, 2014 11:05 PM UTC by Paul
**Last Updated:** Thu May 04, 2017 01:57 PM UTC
**Owner:** nobody


I have not been able to get dovecot:CRYPT-METHOD to work (tried SHA512-CRYPT, SHA256-CRYPT, MD5-CRYPT, and BLF-CRYPT, which I learned isn't supported in my OS). Using one results in the following error message when setting up admin account with setup.php:

can't encrypt password with dovecotpw, see error log for details

This is what the logs state:
1624#0: *6 FastCGI sent in stderr: "PHP message: dovecotpw password encryption failed.

PHP message: STDERR output: sh: 1: /usr/sbin/doveadm: not found" while reading response header from upstream <...> upstream: "fastcgi://unix:/var/run/php5-fpm.sock:" <...>

In config.inc.php I see:

// If you use the dovecot encryption method: where is the dovecotpw binary located?
// for dovecot 1.x
// $CONF['dovecotpw'] = "/usr/sbin/dovecotpw";
// for dovecot 2.x (dovecot 2.0.0 - 2.0.7 is not supported!)
$CONF['dovecotpw'] = "/usr/sbin/doveadm pw";

A couple quick checks:
\# ll /usr/sbin/doveadm
-rwxr-xr-x 1 root root 423264 Feb 13 23:23 /usr/bin/doveadm*

\# doveadm pw -l
CRYPT MD5 MD5-CRYPT SHA SHA1 SHA256 SHA512 SMD5 SSHA SSHA256 SSHA512 PLAIN CLEAR CLEARTEXT PLAIN-TRUNC CRAM-MD5 SCRAM-SHA-1 HMAC-MD5 DIGEST-MD5 PLAIN-MD4 PLAIN-MD5 LDAP-MD5 LANMAN NTLM OTP SKEY RPA SHA256-CRYPT SHA512-CRYPT


Using Dovecot 2.2, PHP 5.5, MariaDB 10, Postfix 2.11.


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[postfixadmin:bugs] #319 dovecot:CRYPT-METHOD does not work

[Mario Y. <mar...@us...>]

It may be too late to respond this question. I had the same problem, and found a solution.
There seems to be incompatibilty to deal with dovecotpw in functions.inc.php. Although doveadm generates  password hashes with random salt, they offers verified function with '-t' option.  You need few modification on functions.inc.php.  If you need the source code, I am more than willing to share. 
(Postfix version 2.3.3/Dovecot version 2.2.10)


---

** [bugs:#319] dovecot:CRYPT-METHOD does not work**

**Status:** closed-invalid
**Group:** v2.91 (3.0 beta1)
**Created:** Fri May 30, 2014 11:05 PM UTC by Paul
**Last Updated:** Sun May 22, 2016 05:22 PM UTC
**Owner:** nobody


I have not been able to get dovecot:CRYPT-METHOD to work (tried SHA512-CRYPT, SHA256-CRYPT, MD5-CRYPT, and BLF-CRYPT, which I learned isn't supported in my OS). Using one results in the following error message when setting up admin account with setup.php:

can't encrypt password with dovecotpw, see error log for details

This is what the logs state:
1624#0: *6 FastCGI sent in stderr: "PHP message: dovecotpw password encryption failed.

PHP message: STDERR output: sh: 1: /usr/sbin/doveadm: not found" while reading response header from upstream <...> upstream: "fastcgi://unix:/var/run/php5-fpm.sock:" <...>

In config.inc.php I see:

// If you use the dovecot encryption method: where is the dovecotpw binary located?
// for dovecot 1.x
// $CONF['dovecotpw'] = "/usr/sbin/dovecotpw";
// for dovecot 2.x (dovecot 2.0.0 - 2.0.7 is not supported!)
$CONF['dovecotpw'] = "/usr/sbin/doveadm pw";

A couple quick checks:
\# ll /usr/sbin/doveadm
-rwxr-xr-x 1 root root 423264 Feb 13 23:23 /usr/bin/doveadm*

\# doveadm pw -l
CRYPT MD5 MD5-CRYPT SHA SHA1 SHA256 SHA512 SMD5 SSHA SSHA256 SSHA512 PLAIN CLEAR CLEARTEXT PLAIN-TRUNC CRAM-MD5 SCRAM-SHA-1 HMAC-MD5 DIGEST-MD5 PLAIN-MD4 PLAIN-MD5 LDAP-MD5 LANMAN NTLM OTP SKEY RPA SHA256-CRYPT SHA512-CRYPT


Using Dovecot 2.2, PHP 5.5, MariaDB 10, Postfix 2.11.


---

Sent from sourceforge.net because pos...@li... is subscribed to https://sourceforge.net/p/postfixadmin/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/postfixadmin/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.