So simple. :) No the curmail_size is correct. The shared mailbox is in
the public namespace. I explicitly put it there to make it available for
every user. The spam user only exists because the script needs the
password to access the mail folders. As I understand it is not possible
to login with __anyone__ or __public__, right?
The dbmail-util command is part of the cronjob dbmail installed.
0 3 * * * root /usr/sbin/dbmail-util -ay >/dev/null 2>&1
Is that the same command? Since -d is included in -a I would tend to say so.
Why isn't the curmail_size set to zero if it wasn't yet calculated? It
was set to zero for all the users, except for the spam user. Is there a
reason for that or should I just live with the working thing now? :)
Tanks for the help.
Christian
PS:
After running the spam script again curmail_size is back to its
astronomic value.
What the script does is (shortened):
$imap->select('#Public/Spam');
$imap->search("ALL");
$imap->message_to_file("/tmp/salearn",$msgs[$i]);
$salearn = `/usr/bin/sa-learn --no-rebuild --showdots --spam
/tmp/salearn`; }
$imap->delete_message($msgs[$i]);
$imap->expunge();
$imap->close();
The commands come with the Perl IMAPClient module. How can they have
such a bad influence on the mailbox? Now I have to run dbmail-util after
the script every time?
> Is the spam box accessible under the #User or #Public namespace?
>
> If the #Public namespace is used, the mailbox involved is owned by the
> 'anyone' user, not the spam user.
>
> dbmail-util -dy which will re-calculate all user quota. Isn't that part
> of your daily cronjob?
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
