[vPostMaster] New features?

[Jørgen Haseth Laukholm]

This email became a private dialogue between me and one of the develovers.
Forwarding it to the mailinglist as I suppose it contains info usefull for
the list.

---------------------------- Original Message ----------------------------
Subject: Re: [vPostMaster] New features?
From:    "Sean Reifschneider" <jafo at tummy.com>
Date:    Fri, September 8, 2006 2:59
To:      "J?rgen Laukholm" <jorgen at laukholm.com>
--------------------------------------------------------------------------

On Fri, Sep 08, 2006 at 12:59:28AM +0200, J?rgen Laukholm wrote:
>I partly agree. My setup today is 2 secondary mx with greylisting and rbl
lists enabled. So my approach is to relay mail (and spam) on these
servers, and let the master mx do the content-analyze with amavis and
spamassassin.

vPostMaster doesn't really have a way to support that sort of
configuration directly.  You can, however, run 3 mail servers with them
all pointing at the same backend database and mounting the same mail spool
for delivery. This is a way of spreading the load of anti-spam and
anti-virus around among many machines.

>Have you thought of supporting Cyrus mailserver? A Cyrus mailserver would
give that kind of functionality through Sieve.

I really don't know Cyrus well enough to know how that would even be
possible.  It's certainly not something that's high in priority on the
TODO list -- having some seive functionality in the current code is
definitely higher priority.

>1. When deleting a user from vPostMaster the directory structure is kept
intact with all the mail. Is this by purpose so you manually have to
delete the user directory afterwards, or is this a bug/problem with my
setup?

I left it there on purpose because it's so easy to delete a user and so
much data goes with that, that it's a bad mistake to make.  You're right
though, I should switch that to deleting the directory, and if you don't
have good backups you deserve what you get.  ;-/

>2. Tried the vpmuser script to add/delete users. Adding users works like
a charm, but deleting users gives me the following error:
>
>$python vpmuser --delete --domain test.com --user test
>FAILURE: Database error while deleting user: ERROR:  permission denied
for relation users
>DELETE FROM users WHERE name = 'test' and domainsname = 'test.com'
>
>What is causing this problem?
>(My vPostMaster install is on a Debian Stable system, using your
>install-vpostmaster script to install vPostMaster)

That is a PostgreSQL permissions issue.  To fix it you should be able to do:

   su -s /bin/sh postfix
   psql -d vpostmaster
   grant delete on users to vpostmaster;
   Control-D
   Control-D

That will be fixed in the next release, thanks for pointing that out.

>3. One feature I would love to see implemented, is a column in the
database keeping track of when a user was last logged in, and also
visible in the web-interface. Would that be possible?

It would be fairly easy to trap when the POP/IMAP server had last
requested the password from the database.  However, that doesn't provide
information on if the user successfully logged in, and couldn't tell a
real login from someone issuing a bad password against that account via
POP.

Ideally, the way to do it would be if Dovecot, the POP/IMAP server,
supported doing another SQL query after the user was authenticated, or
when there was a failed login, possibly also when they disconnected.  It
could also include information on the remote IP, etc...  However, it
doesn't.

The only way currently to do that would be to set up another process which
watched the mail log file and pulled out the dovecot messages, and pushed
them into the database.

I'll add this as a TODO entry.

Thanks,
Sean
-- 
 Nothing like a river-boat cruise at 3am to make a person realize how
great life can be - as long as they have a boat.  -- A. Wyskowski, 2002
Sean Reifschneider, Member of Technical Staff <jafo at tummy.com>
tummy.com, ltd. - Linux Consulting since 1995: Ask me about High Availability