vmm-users — The main list for general vmm discussion

[vmm-users] Version 0.7.0 released

[Pascal V. <use...@lo...>]

vmm-0.7.0 is available for download:
https://sourceforge.net/projects/vmm/files/vmm/0.7.0/vmm-0.7.0.tar.gz/download
https://sourceforge.net/projects/vmm/files/vmm/0.7.0/vmm-0.7.0.tar.gz.sig/download

What's new:
	* This release is mainly a rewrite from Py2 to Py3.
	* New translations:
	  + Serbian
	  + Spanish
	  * Swedish
	+ userpassword accepts hashed passwords
	+ domainservices/userservices can be enabled `-e SERVICE' or
	  disabled `-d SERVICE' separately (by grindhold).
	- Dropped pyPgSQL support


Regards,
Pascal

[vmm-users] Alias not recognized by Postfix (550 Recipient address rejected: User unknown in local recipient table)

[Paul M. <pau...@us...>]

Dear vmm users,


using Debian 7 (wheezy/oldstable) with vmm 0.6.2 from Debian 8
(jessie/stable), a user alias is not recognized, so no messages can be
sent to that address.

```
# vmm version
vmm, version 0.6.2 (from 02/01/2014)
Python 2.7.3 on Linux

Copyright (c) 2007-2014 Pascal Volk <use...@lo...
>
vmm is free software and comes with ABSOLUTELY NO WARRANTY.
```

The error is below.

```
<** 550 5.1.1 <jo...@ma...>: Recipient address rejected: User unknown in local recipient table
```

There is an alias domain mail.example.net for example.net.

```
# vmm aliasdomaininfo mail.example.net
Alias domain information
------------------------
        The alias domain mail.example.net belongs to:
            * example.net
```

The user jo...@ex... exists and works.

```
# vmm userinfo jo...@ex...
Account information
-------------------
        Address..........: jo...@ex...
[…]
```

The alias jo...@ma... does not work though.

```
# vmm aliasinfo jo...@ma...
Error: The domain 'mail.example.net' is an alias domain.
```

In IRC I was asked to provide the output below. Unfortunately `postmap`
returns an error.

```
# postmap -q jo...@ma... `postconf -h virtual_alias_maps`
po
stmap: fatal: open database ${proxysql}pgsql-virtual_alias_maps.cf.db:
No such file or directory
# postconf -h virtual_alias_maps
${proxysql}pgsql-virtual_alias_maps.cf
# grep -Ri virtual_alias_map
postfix/pgsql-virtual_alias_maps.cf:query = SELECT destination FROM postfix_virtual_alias_map('%u', '%d')
postfix/main.cf:virtual_alias_maps = ${proxysql}pgsql-virtual_alias_maps.cf
```

The behavior is the same for all the other users created after the same
scheme.

Strangely, the alias <joe...@ma...> works.
<joe...@ex...> is an alias for <jo...@ex...>.

Do you know how this can be corrected?


Thanks,

Paul

Re: [vmm-users] /srv/mail in section System Preparation of Installation Guide

[Paul M. <pau...@us...>]

Am Montag, den 24.02.2014, 20:54 +0000 schrieb Pascal Volk:
> On 02/24/2014 08:06 PM Pascal Volk wrote:
> > /srv/mail is the default misc.base_directory. …
> 
> I just noticed that you are using the Debian package of vmm. The package
> uses /var/lib/vmm as base_directory.

Indeed. I missed that. Having the word Debian in the sentence below [1]
put me off I guess.

        The example below shows the steps executed on a Debian GNU/Linux
        system.

I can think of two things to further clarify it.

1. Add that `/srv/mail` is the default in `vmm.cfg`. Searching for that
string, for example with grep, would have shown me the location.

2. Add the following note to the instructions.

        Please note that the default is changed in some distributions
        like Debian.


Thanks,

Paul


[1] http://vmm.localdomain.org/installation/system_preparation.html

Re: [vmm-users] [solved in 0.6.1] Problems with `listusers` and domain aliases in vmm 0.6.0

[Paul M. <pau...@us...>]

Am Montag, den 24.02.2014, 20:47 +0000 schrieb Pascal Volk:
> On 02/24/2014 08:17 AM Paul Menzel wrote:

> > using Debian Wheezy with vmm 0.6.0, I have the following problem.
> > Looking at the changes for the versions afterward, I could not spot a
> > fix either [1][2].
> 
> Those files list only the 'most important' changes. The NEWS file
> <http://hg.localdomain.org/vmm/file/vmm-0.6.1/NEWS> for 0.6.1 mentions:
> 	+ Improved 'address searching' (by Martin F. Krafft).

Thanks. Next time I’ll check there.

> > I did `vmm domainadd example.net`, then adding a domain alias with
> > 
> >         $ vmm aliasdomainadd mail.example.net`
> > 
> > and then `vmm useradd te...@ex...`, but it is not listed in the
> > user list with `vmm listusers`.
> > 
> > Only `te...@ma...` (additional `mail.`) is listed twice as an
> > alias account (prefixed with `[-]`). This seems to be only a problem of
> > the command `listusers` as the real user `te...@ex...` seems to be
> > there.
> 
> I've just tested it with vmm-0.6.1-1 (jessie). The user gets listed for
> the destination domain [+] and each alias domain [-].

Indeed, with vmm 0.6.1 from Debian Jessie the output is correct. I’ll
submit a bug report to the Debian packages in the next few days.


Thanks,

Paul

Re: [vmm-users] /srv/mail in section System Preparation of Installation Guide

[Pascal V. <use...@lo...>]

On 02/24/2014 08:06 PM Pascal Volk wrote:
> /srv/mail is the default misc.base_directory. …

I just noticed that you are using the Debian package of vmm. The package
uses /var/lib/vmm as base_directory.


Regards,
Pascal

Re: [vmm-users] Problems with `listusers` and domain aliases

[Pascal V. <use...@lo...>]

On 02/24/2014 08:17 AM Paul Menzel wrote:
> Dear vmm users,
> 
> 
> using Debian Wheezy with vmm 0.6.0, I have the following problem.
> Looking at the changes for the versions afterward, I could not spot a
> fix either [1][2].

Those files list only the 'most important' changes. The NEWS file
<http://hg.localdomain.org/vmm/file/vmm-0.6.1/NEWS> for 0.6.1 mentions:
	+ Improved 'address searching' (by Martin F. Krafft).

> 
> I did `vmm domainadd example.net`, then adding a domain alias with
> 
>         $ vmm aliasdomainadd mail.example.net`
> 
> and then `vmm useradd te...@ex...`, but it is not listed in the
> user list with `vmm listusers`.
> 
> Only `te...@ma...` (additional `mail.`) is listed twice as an
> alias account (prefixed with `[-]`). This seems to be only a problem of
> the command `listusers` as the real user `te...@ex...` seems to be
> there.

I've just tested it with vmm-0.6.1-1 (jessie). The user gets listed for
the destination domain [+] and each alias domain [-].


Regards,
Pascal

Re: [vmm-users] /srv/mail in section System Preparation of Installation Guide

[Pascal V. <use...@lo...>]

On 02/24/2014 08:21 AM Paul Menzel wrote:
> Dear vmm folks,
> 
> 
> in the section System Preparation of Installation Guide [1] the
> `/srv/mail` folder should be created. But looking through the other
> steps it is never mentioned again.
> 
> On my current system the subfolders is empty too.

/srv/mail is the default misc.base_directory. If you've configured a
different path in your vmm.cfg (see: vmm cg misc.base_directory), that
path will be used instead.


If you don't use /srv/mail, you can delete the empty directory.
Before deleting /srv/mail make sure that none of your domains has the
'domain directory' somewhere inside /srv/mail.


Regards,
Pascal

[vmm-users] /srv/mail in section System Preparation of Installation Guide

[Paul M. <pau...@us...>]

Dear vmm folks,


in the section System Preparation of Installation Guide [1] the
`/srv/mail` folder should be created. But looking through the other
steps it is never mentioned again.

On my current system the subfolders is empty too.


Thanks,

Paul


[1] http://vmm.localdomain.org/installation/system_preparation.html

[vmm-users] Problems with `listusers` and domain aliases

[Paul M. <pau...@us...>]

Dear vmm users,


using Debian Wheezy with vmm 0.6.0, I have the following problem.
Looking at the changes for the versions afterward, I could not spot a
fix either [1][2].

I did `vmm domainadd example.net`, then adding a domain alias with

        $ vmm aliasdomainadd mail.example.net`

and then `vmm useradd te...@ex...`, but it is not listed in the
user list with `vmm listusers`.

Only `te...@ma...` (additional `mail.`) is listed twice as an
alias account (prefixed with `[-]`). This seems to be only a problem of
the command `listusers` as the real user `te...@ex...` seems to be
there.


Thanks,

Paul


[1] http://sourceforge.net/projects/vmm/files/vmm/0.6.1/
[2] http://sourceforge.net/projects/vmm/files/vmm/0.6.2/

Re: [vmm-users] How to let users change their password?

[Pascal V. <use...@lo...>]

On 02/11/2014 08:23 AM Paul Menzel wrote:

> first of all, thank you very much for this great piece of software, the
> great documentation and the prompt help in the IRC channel #vmm on
> <irc.freenode.net>!

Nice to hear that, thank you.

> Do best practices exist, how users can change the password themselves? I
> found the German blog post “Passwort ändern mit Roundcube und vmm
> basiertem Mailserver” [1] adding SQL queries to do that. Wanting to use
> Roundcube too in my set-up, I am going to use that too, if there is no
> other recommended way.

There is currently nothing, what users would allow to change their
passwords.

Some considerations:

	* Create an additional database user and add that user
	  to the group mailsys (or whatever group you've used
	  in your pg_hba.conf).

	* Give that user some permissions:
	  GRANT SELECT (local_part, uid, gid) ON users TO $USER;
	  GRANT SELECT, UPDATE (passwd) ON users TO $USER;
	  GRANT SELECT ON domain_name TO $USER;

Then execute a database query, like:

	SELECT local_part || '@' || domainname AS userid, uid, passwd
	  FROM users, domain_name
	 WHERE local_part = 'j.roe'
	   AND domainname = 'example.com'
	   AND domain_name.gid = users.gid;


	      userid       |  uid  |   passwd
	-------------------+-------+------------
	 j....@ex... | 79941 | {CRAM-MD5}…
	(1 row)

With such a result you can verify the email address, validate the
password. The uid will be used for the update query:

	UPDATE users SET passwd = '{SCHEME}…' WHERE uid = 79941;


Regards,
Pascal

[vmm-users] How to let users change their password?

[Paul M. <pau...@us...>]

Dear vmm folks,


first of all, thank you very much for this great piece of software, the
great documentation and the prompt help in the IRC channel #vmm on
<irc.freenode.net>!

Do best practices exist, how users can change the password themselves? I
found the German blog post “Passwort ändern mit Roundcube und vmm
basiertem Mailserver” [1] adding SQL queries to do that. Wanting to use
Roundcube too in my set-up, I am going to use that too, if there is no
other recommended way.


Thanks,

Paul


[1] http://www.finnchristiansen.de/2014/01/07/passwort-aendern-mit-roundcube-und-vmm-basiertem-mailserver/

[vmm-users] Version 0.6.2 released

[Pascal V. <use...@lo...>]

vmm-0.6.2 is available for download:
http://sourceforge.net/projects/vmm/files/vmm/0.6.2/vmm-0.6.2.tar.gz/download
http://sourceforge.net/projects/vmm/files/vmm/0.6.2/vmm-0.6.2.tar.gz.sig/download

What's new:
        * Added support for IDN ccTLDs and 'new' gTLDs
        * Added support for SCRAM-SHA-1 password hashes (requires
	  Dovecot ≧ v2.2.0)
        * Updated translations: Finnish
        - Fixed a TypeError in `userdelete … force`
        - Fixed an error in the install.sh script


Regards,
Pascal
-- 
The trapper recommends today: http://home.arcor.de/allusers/

Re: [vmm-users] Failed update to 0.6.1

[Gerald S. <ge...@sc...>]

Am 25.10.2013 21:06, schrieb Pascal Volk:
> On 10/25/2013 07:57 AM Gerald Schneider wrote:
>> I just found another problem (hopefully the last one):
>>
>> when I run "vmm di domain.com" I get the following error:
>>
>> Traceback (most recent call last):
>> …
>>      'FROM vmm_domain_info WHERE gid = %s', (self._gid,))
>> psycopg2.ProgrammingError: syntax error at or near ""alias domains""
>> LINE 1: SELECT aliasdomains "alias domains", accounts, aliases, 
>> relo...
>
> Hm, that error message is confusing me. What version of PostgreSQL 
> are
> you using? Some version ≤ 8.3? If so, you could apply the attached 
> patch.
> (PostgreSQL Versions ≤ 8.3 are "Unsupported versions". See
> http://www.postgresql.org/docs/8.4/static/)
I am using version 8.4.17-0squeeze1, but the patch helped nevertheless.

I think I'm done now, thanks for all the help :)

Regards,
   Gerald

Re: [vmm-users] Failed update to 0.6.1

[Pascal V. <use...@lo...>]

On 10/25/2013 07:57 AM Gerald Schneider wrote:
> I just found another problem (hopefully the last one):
> 
> when I run "vmm di domain.com" I get the following error:
> 
> Traceback (most recent call last):
> …
>      'FROM vmm_domain_info WHERE gid = %s', (self._gid,))
> psycopg2.ProgrammingError: syntax error at or near ""alias domains""
> LINE 1: SELECT aliasdomains "alias domains", accounts, aliases, relo...

Hm, that error message is confusing me. What version of PostgreSQL are
you using? Some version ≤ 8.3? If so, you could apply the attached patch.
(PostgreSQL Versions ≤ 8.3 are "Unsupported versions". See
http://www.postgresql.org/docs/8.4/static/)


Regards,
Pascal

Re: [vmm-users] Failed update to 0.6.1

[Gerald S. <ge...@sc...>]

I just found another problem (hopefully the last one):

when I run "vmm di domain.com" I get the following error:

Traceback (most recent call last):
   File "/usr/local/sbin/vmm", line 18, in <module>
     sys.exit(run(sys.argv))
   File 
"/usr/local/lib/python2.6/dist-packages/VirtualMailManager/cli/main.py", 
line 58, in run
     cmd_func(run_ctx)
   File 
"/usr/local/lib/python2.6/dist-packages/VirtualMailManager/cli/subcommands.py", 
line 310, in domain_info
     info = ctx.hdlr.domain_info(ctx.args[2].lower(), details)
   File 
"/usr/local/lib/python2.6/dist-packages/VirtualMailManager/handler.py", 
line 524, in domain_info
     dominfo = dom.get_info()
   File 
"/usr/local/lib/python2.6/dist-packages/VirtualMailManager/domain.py", 
line 404, in get_info
     'FROM vmm_domain_info WHERE gid = %s', (self._gid,))
psycopg2.ProgrammingError: syntax error at or near ""alias domains""
LINE 1: SELECT aliasdomains "alias domains", accounts, aliases, relo...
                             ^

Regards,
   Gerald

Re: [vmm-users] Failed update to 0.6.1

[Gerald S. <ge...@sc...>]

Thanks, by now I managed to get it (mostly) running.

Am 24.10.2013 20:31, schrieb Pascal Volk:
>> Traceback (most recent call last):
>>   File "/usr/local/sbin/vmm", line 11, in <module>
>>     from VirtualMailManager import *
>> ImportError: No module named VirtualMailManager
>
> There were 0.5.1 and 0.5.2 in 2009.
> The above error message could be caused by Python upgrades from e.g.
> 2.5.x to 2.6.x. The way to fix that problem: just run the upgrade.sh
> script. It should have installed the vmm code for the new Python 
> version.

I did that after I found it.

>>   File "/usr/local/sbin/vmm", line 18, in <module>
>>     sys.exit(run(sys.argv))
>>  …
>> psycopg2.ProgrammingError: column "sieve" does not exist
>> LINE 1: SELECT ssid, smtp, pop3, imap, sieve FROM service_set WHERE 
>> ...
>
> What Dovecot version is in your vmm.cfg? Something >= 1.2.0?
> If so, did you import the update_tables_0.5.x_for_dovecot-1.2.x.pgsql
> script
> 
> <http://hg.localdomain.org/vmm/file/vmm-0.5.2/update_tables_0.5.x_for_dovecot-1.2.x.pgsql>?
> (Before Dovecot 1.2.0 the column was named 'managesieve')
>
>> Afterwards I found the upgrade guide and ran
>> the update_tables_0.5.x-0.6.pgsql script.
>>
>> mailsys=> \i update_tables_0.5.x-0.6.pgsql
>                ^^^^^^^^^^^^^^^^^^^^^^^^^This file is for Dovecot < 
> 1.2.0

I was pretty sure I was using dovecot 1.1, that's why I ran the 
update_tables_0.5.x-0.6.pgsql script. But it actually is 1.2.15, so now 
I ran dovecot_update_v1.2+.pgsql as well, figuring that the other script 
is really only when updating from 0.5.x.

> You've executed the install.sh script. That script copies new 
> pgsql-*.cf
> files into Postfix' $config_directory. If you didn't modify them,
> Postfix tries to authenticate with the password 'some_password'.
>
> There is also the set-permissions.py script
> 
> <http://vmm.localdomain.org/upgrade/0.5-0.6.html#set-database-permissions>.
> This is used to set database permissions for Dovecot and Postfix.
> Execute this script, if you didn't do it already.
>
>
>> Is there any easier way than setting all up from scratch?
>
> If you are using Dovecot >= 1.2.0 you have also to apply the
> pgsql/dovecot_update_v1.2+.pgsql
> 
> <http://hg.localdomain.org/vmm/file/vmm-0.6.1/pgsql/dovecot_update_v1.2%2B.pgsql>
> SQL script.
> If you are using Dovecot < 1.2.0 set the correct version in your 
> vmm.cfg.
>
> Check all your pgsql-*.cf file in /etc/postfix.
> And finally execute the set-permissions.py script.
>
> I hope that solves all problems. :)

It did. I managed to solve most of it yesterday evening by replacing 
some_password with the actual password from backup files and I had to 
replace some SQL queries in the dovecot config manually, but applying 
the dovecot_update_v1.2+.pgsql script solved the last problem. Now vmm 
runs without exceptions again.

Thanks for the help.

Regards,
   Gerald

Re: [vmm-users] Failed update to 0.6.1

[Pascal V. <use...@lo...>]

Hi Gerald,

On 10/24/2013 01:42 PM Gerald Schneider wrote:
> Hi,
> 
> I don't know if this is the right way to ask for help, but I didn't find
> any other way.

Yes, either here on the mailing list or IRC: #vmm in the freenode network.

> I just tried to update my vmm installation to 0.6.1 and I found the
> upgrade guide only after it already failed. I was using a 0.5 version (I
> think), now it's too late to look up which one exactly, IIRC the last
> entry in the changelog was from 2009. The old version stopped working
> after I updated some system packages and I needed to fix it. Everytime I
> ran vmm I got this error message:
> 
> Traceback (most recent call last):
>   File "/usr/local/sbin/vmm", line 11, in <module>
>     from VirtualMailManager import *
> ImportError: No module named VirtualMailManager

There were 0.5.1 and 0.5.2 in 2009.
The above error message could be caused by Python upgrades from e.g.
2.5.x to 2.6.x. The way to fix that problem: just run the upgrade.sh
script. It should have installed the vmm code for the new Python version.

> I downloaded and extracted version 0.6.1, saved a backup of my vmm.cfg,
> ran ./install.sh, modified the new vmm.cfg to match my old as good as I
> could, ran vmm and it worked. 'vmm listdomains', 'vmm listusers' works
> too, what's not working for example is 'vmm ui mail@domain':
> 
>   File "/usr/local/sbin/vmm", line 18, in <module>
>     sys.exit(run(sys.argv))
>  …
> psycopg2.ProgrammingError: column "sieve" does not exist
> LINE 1: SELECT ssid, smtp, pop3, imap, sieve FROM service_set WHERE ...

What Dovecot version is in your vmm.cfg? Something >= 1.2.0?
If so, did you import the update_tables_0.5.x_for_dovecot-1.2.x.pgsql
script
<http://hg.localdomain.org/vmm/file/vmm-0.5.2/update_tables_0.5.x_for_dovecot-1.2.x.pgsql>?
(Before Dovecot 1.2.0 the column was named 'managesieve')

> Afterwards I found the upgrade guide and ran
> the update_tables_0.5.x-0.6.pgsql script.
> 
> mailsys=> \i update_tables_0.5.x-0.6.pgsql
               ^^^^^^^^^^^^^^^^^^^^^^^^^This file is for Dovecot < 1.2.0

> SET
> …
> UPDATE 5
       ^^^ Line 130-136 using column managesieve
> ALTER TABLE
> ALTER TABLE
> ALTER TABLE
> ALTER TABLE
> ALTER TABLE
> ALTER TABLE
> ALTER TABLE
> UPDATE 5
> CREATE TABLE 
> ALTER TABLE
> ALTER TABLE
> CREATE VIEW
  ^^ Line 185: CREATE VIEW vmm_domain_info
> psql:update_tables_0.5.x-0.6.pgsql:209: ERROR:  type "address_maildir"
> does not exist
> psql:update_tables_0.5.x-0.6.pgsql:210: ERROR:  type "dovecotpassword"
> does not exist
> psql:update_tables_0.5.x-0.6.pgsql:211: ERROR:  type "dovecotuser" does
> not exist
> psql:update_tables_0.5.x-0.6.pgsql:212: ERROR:  type
> "recipient_destination" does not exist
> psql:update_tables_0.5.x-0.6.pgsql:213: ERROR:  type
> "recipient_transport" does not exist
> psql:update_tables_0.5.x-0.6.pgsql:214: ERROR:  type "recipient_uid"
> does not exist
> psql:update_tables_0.5.x-0.6.pgsql:215: ERROR:  type "sender_login" does
> not exist

Yeah, as mentioned in the SQL script: 'the dirty way' ;)

> CREATE TYPE
> …
> CREATE FUNCTION
> mailsys=> \q

The database update was successful at all.

> 
> But this didn't help either. 
> 
> Postfix can't talk to the database either, I find these entries in the
> mail log:
> 
> Oct 24 13:39:47 rom144 postfix/trivial-rewrite[31435]: warning: connect
> to pgsql server localhost: FATAL:  password authentication failed for
> user "postfix"?

You've executed the install.sh script. That script copies new pgsql-*.cf
files into Postfix' $config_directory. If you didn't modify them,
Postfix tries to authenticate with the password 'some_password'.

There is also the set-permissions.py script
<http://vmm.localdomain.org/upgrade/0.5-0.6.html#set-database-permissions>.
This is used to set database permissions for Dovecot and Postfix.
Execute this script, if you didn't do it already.


> Right now my complete mail system is not working :(
> 
> Is there any easier way than setting all up from scratch?

If you are using Dovecot >= 1.2.0 you have also to apply the
pgsql/dovecot_update_v1.2+.pgsql
<http://hg.localdomain.org/vmm/file/vmm-0.6.1/pgsql/dovecot_update_v1.2%2B.pgsql>
SQL script.
If you are using Dovecot < 1.2.0 set the correct version in your vmm.cfg.

Check all your pgsql-*.cf file in /etc/postfix.
And finally execute the set-permissions.py script.

I hope that solves all problems. :)


Regards,
Pascal

[vmm-users] Failed update to 0.6.1

[Gerald S. <ger...@gm...>]

Hi,

I don't know if this is the right way to ask for help, but I didn't find
any other way.

I just tried to update my vmm installation to 0.6.1 and I found the upgrade
guide only after it already failed. I was using a 0.5 version (I think),
now it's too late to look up which one exactly, IIRC the last entry in the
changelog was from 2009. The old version stopped working after I updated
some system packages and I needed to fix it. Everytime I ran vmm I got this
error message:

Traceback (most recent call last):
  File "/usr/local/sbin/vmm", line 11, in <module>
    from VirtualMailManager import *
ImportError: No module named VirtualMailManager

I downloaded and extracted version 0.6.1, saved a backup of my vmm.cfg, ran
./install.sh, modified the new vmm.cfg to match my old as good as I could,
ran vmm and it worked. 'vmm listdomains', 'vmm listusers' works too, what's
not working for example is 'vmm ui mail@domain':

  File "/usr/local/sbin/vmm", line 18, in <module>
    sys.exit(run(sys.argv))
  File
"/usr/local/lib/python2.6/dist-packages/VirtualMailManager/cli/main.py",
line 58, in run
    cmd_func(run_ctx)
  File
"/usr/local/lib/python2.6/dist-packages/VirtualMailManager/cli/subcommands.py",
line 631, in user_info
    info = ctx.hdlr.user_info(ctx.args[2].lower(), details)
  File
"/usr/local/lib/python2.6/dist-packages/VirtualMailManager/handler.py",
line 785, in user_info
    acc = self._get_account(emailaddress)
  File
"/usr/local/lib/python2.6/dist-packages/VirtualMailManager/handler.py",
line 251, in _get_account
    return Account(self._dbh, address)
  File
"/usr/local/lib/python2.6/dist-packages/VirtualMailManager/account.py",
line 55, in __init__
    self._domain = Domain(self._dbh, self._addr.domainname)
  File
"/usr/local/lib/python2.6/dist-packages/VirtualMailManager/domain.py", line
64, in __init__
    self._load()
  File
"/usr/local/lib/python2.6/dist-packages/VirtualMailManager/domain.py", line
86, in _load
    self._services = ServiceSet(self._dbh, ssid=result[2])
  File
"/usr/local/lib/python2.6/dist-packages/VirtualMailManager/serviceset.py",
line 74, in __init__
    self._load_by_ssid(kwargs[key])
  File
"/usr/local/lib/python2.6/dist-packages/VirtualMailManager/serviceset.py",
line 126, in _load_by_ssid
    ' FROM service_set WHERE ssid = %s', (ssid,))
psycopg2.ProgrammingError: column "sieve" does not exist
LINE 1: SELECT ssid, smtp, pop3, imap, sieve FROM service_set WHERE ...

Afterwards I found the upgrade guide and ran
the update_tables_0.5.x-0.6.pgsql script.

mailsys=> \i update_tables_0.5.x-0.6.pgsql
SET
SET
CREATE SEQUENCE
CREATE TABLE
DROP VIEW
DROP VIEW
DROP VIEW
DROP VIEW
DROP VIEW
DROP VIEW
DROP VIEW
DROP VIEW
CREATE SEQUENCE
CREATE SEQUENCE
CREATE TABLE
INSERT 0 1
INSERT 0 1
INSERT 0 1
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
CREATE TABLE
INSERT 0 1
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
CREATE TABLE
CREATE FUNCTION
CREATE TRIGGER
ALTER TABLE
ALTER TABLE
ALTER TABLE
UPDATE 5
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
UPDATE 5
CREATE TABLE
ALTER TABLE
ALTER TABLE
CREATE VIEW
psql:update_tables_0.5.x-0.6.pgsql:209: ERROR:  type "address_maildir" does
not exist
psql:update_tables_0.5.x-0.6.pgsql:210: ERROR:  type "dovecotpassword" does
not exist
psql:update_tables_0.5.x-0.6.pgsql:211: ERROR:  type "dovecotuser" does not
exist
psql:update_tables_0.5.x-0.6.pgsql:212: ERROR:  type
"recipient_destination" does not exist
psql:update_tables_0.5.x-0.6.pgsql:213: ERROR:  type "recipient_transport"
does not exist
psql:update_tables_0.5.x-0.6.pgsql:214: ERROR:  type "recipient_uid" does
not exist
psql:update_tables_0.5.x-0.6.pgsql:215: ERROR:  type "sender_login" does
not exist
CREATE TYPE
CREATE TYPE
CREATE TYPE
CREATE TYPE
CREATE TYPE
CREATE TYPE
CREATE TYPE
CREATE TYPE
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
CREATE FUNCTION
mailsys=> \q

But this didn't help either.

Postfix can't talk to the database either, I find these entries in the mail
log:

Oct 24 13:39:47 rom144 postfix/trivial-rewrite[31435]: warning: connect to
pgsql server localhost: FATAL:  password authentication failed for user
"postfix"?
Oct 24 13:39:47 rom144 postfix/trivial-rewrite[31435]: fatal:
pgsql:/etc/postfix/pgsql-virtual_mailbox_domains.cf(0,lock|fold_fix): table
lookup problem
Oct 24 13:39:47 rom144 postfix/trivial-rewrite[31436]: warning: connect to
pgsql server localhost: FATAL:  password authentication failed for user
"postfix"?
Oct 24 13:39:47 rom144 postfix/trivial-rewrite[31436]: fatal:
pgsql:/etc/postfix/pgsql-virtual_mailbox_domains.cf(0,lock|fold_fix): table
lookup problem
Oct 24 13:39:48 rom144 postfix/smtpd[31284]: warning: problem talking to
service rewrite: Success
Oct 24 13:39:48 rom144 postfix/smtpd[31264]: warning: problem talking to
service rewrite: Connection reset by peer
Oct 24 13:39:48 rom144 postfix/master[31198]: warning: process
/usr/lib/postfix/trivial-rewrite pid 31435 exit status 1
Oct 24 13:39:48 rom144 postfix/master[31198]: warning:
/usr/lib/postfix/trivial-rewrite: bad command startup -- throttling

Right now my complete mail system is not working :(

Is there any easier way than setting all up from scratch?

Regards,
  Gerald

[vmm-users] Version 0.6.1 released

[Pascal V. <use...@lo...>]

vmm-0.6.1 is available for download:
http://sourceforge.net/projects/vmm/files/vmm/0.6.1/vmm-0.6.1.tar.gz/download
http://sourceforge.net/projects/vmm/files/vmm/0.6.1/vmm-0.6.1.tar.gz.sig/download

What's new:
	* Added help messages for `vmm help <subcommand>`
	* Updated translations: Dutch
	+ aliasinfo: Print list of destinations sorted.
	+ aliasdelete, catchalldelete: Accept multiple destinations.
	+ Improved 'address searching' (by Martin F. Krafft).
	+ Added file pgsql/dovecot_update_v1.2+.pgsql. Use this if you are
	  upgrading your old Dovecot installation to v1.2.0 or newer.
	- Fixed UnicodeDecodeErrors which may occur with some locales.
	- `user{quota,services,transport} … domain` didn't work as expected.
	- Fixed pgsql FUNCTION dovecotpassword() for Dovecot < v1.2.0.
	  (see UPGRADE for instructions how to fix the last both problems)


Regards,
Pascal
-- 
The trapper recommends today: http://home.arcor.de/allusers/

[vmm-users] Version 0.6.0 released

[Pascal V. <use...@lo...>]

vmm-0.6.0 is available for download:
http://sourceforge.net/projects/vmm/files/vmm/0.6.0/vmm-0.6.0.tar.gz/download
http://sourceforge.net/projects/vmm/files/vmm/0.6.0/vmm-0.6.0.tar.gz.sig/download

What's new:
	* Now vmm supports Dovecot v.2.0.x and v2.1.x
	* Added support for Psycopg 2
	* Added support for Blowfish-, SHA-256- and SHA-512-crypt
	  password hashes. Works also with Dovecot < v2.0.x.
	  New subcommand: listpwschemes
	* Added support for PostgreSQL-based dictionary quota limits
	  per user. Configurable globally and per domain. New commands:
	  domainquota and userquota. (Requires Dovecot >= v1.1.2)
	* Command aliasadd accepts multiple destinations.
	* Command domainadd can automatically create a postmaster
	  account.
	* Command useradd can generate random passwords.
	* Notes can be assigned to domains and accounts (by Martin F.
	  Krafft). New subcommands domainnote and usernote.
	* The subcommands userenable and userdisable have been replaced
	  by userservices. It is now also possible to enable/disable
	  services per domain with the additional subcommand
	  domainservices.
	* New translation: Vietnamese
	* Catch-all support (by Martin F. Krafft) New subcommands:
	  catchalladd, catchalldelete and catchallinfo.
	+ Interpolated alias destinations (by Martin F. Krafft). For
	  example the alias
		pos...@ex... → postmaster+%d...@ad...
	  will forward mails addressed to pos...@ex... to
	  pos...@ad....
	+ New subcommands: configget and configset.
	+ New subcommands by Martin F. Krafft: listaddresses,
	  listaliases, listrelocated and listusers.
	+ Added support for Dovecot's own high-performance mailbox
	  formats single- and multi-dbox.
	- Fixed Python 2.6 DeprecationWarnings
	- Command domaindelete replaced keywords 'delalias', 'deluser'
	  and 'delall' by the keyword 'force'.
	- Command listdomains lists now all matching domains, also when
	  the result contains primary and alias names, but the found
	  alias is not an alias for any of the found primaries.
	- Commands userenable/userdisable accept multiple service
	  names. The keyword 'all' has been removed.
	- Command userdelete replaced keyword 'delalias' by 'force'.


Regards,
Pascal
-- 
The trapper recommends today: http://home.arcor.de/allusers/

[vmm-users] Features planed for the 0.6.0 release

[Pascal V. <use...@lo...>]

This are my plans for the next vmm release:

* Domain 'auto postmaster'
    - create the postmaster account for newly created
      domains automatically
        - vmm.cfg
          + domain.autopastmaster  true || false
          + account.randompassword true || false

* Support Dovecot's quota rules
    - default for all users: Dovecot's plugin {quota_rule setting}
    - default/domain configurable: domainquota (dq) size [msgs] [force]
    - configurable per user: userquota (uq) size [msgs]

* vmm quota policy daemon (vmmqpd)
    - as a smtpd_end_of_data_restriction policy service for Postfix

* Support Postfix's content_filter
    - default per domain: domainfilter (df) filter [force]
    - per user: userfilter (uf) filter

* Support Dovecot's allow_nets
    - default for everyone: Dovecot/Postfix/iptables/packet filter
    - default per domain configurable: domainnetworks (dnw) CIDR [force]
    - configurable per user: usernetworks (unw) CIDR

* Enforce secured (SSL/TLS) connections per user
    - default per domain:  domainsecure (ds) true || false [force]
    - configurable per user: usersecure (us) true || false

* Database
    - replace all VIEWs with functions/procedures?
    - scripts/set_table_perms.py (simple way to set table permissions)


Should someone miss a feature please let me know it. Maybe it's possible
for me to include it in the 0.6.0 release.

As soon as everything is done I'll release a release candidate.


Regards,
Pascal

[vmm-users] Version 0.5.2 released

[Pascal V. <use...@lo...>]

vmm-0.5.2 is available for download:
https://sourceforge.net/projects/vmm/files/vmm/0.5.2/vmm-0.5.2.tar.gz/download
https://sourceforge.net/projects/vmm/files/vmm/0.5.2/vmm-0.5.2.tar.gz.sig/download

What's new:
	* Now vmm supports Dovecot v1.2.x.
	* vmm.cfg: renamed services.managesieve to services.sieve, added
	  misc.dovecotvers.
	* New translations: Dutch and French.
	+ Improved error handling for the domaininfo, aliasdomaininfo,
	  userinfo, aliasinfo and relocatedinfo subcommands.
	+ Sorted alias listing in userinfo output.
	+ Reduction of useless database lookups/updates.
	+ Partly improved database lookups.
	- Fixed a libpq.OperationalError in Account.delete().
	- Eliminated hopefully finally all (potential)
	  UnicodeDecodeErrors.


Regards,
Pascal