Roundcube doesn't move or filter email that is likely being done either by filtering software on the mail server or as you mentioned another mail client that is connected to the mail server.

Hi all, please help!
We have some issue: A lot of messages - even new messages - are being moved to the Archive folder by themselves. This is unwanted behavior. We don't know if we have enabled it somewhere and we don't know how.  Or another mail client is doing it. We would need to find out exactly how Roundcube should behave. Our provider has the old Roundcube Webmail 1.1.5.

I can't find some end-user manual or information, what should "Archive" folder do.

Thank You!

I'm going to guess that is a service that comes in the Ubuntu packaged version of Roundcube since its not part of the core Roundcube package. You'll likely need to report it to the Ubuntu package maintainer so they can fix it.

I'm guessing its designed to run the <RC root>/bin/cleandb.sh script but that really isn't something that needs to be done often. I would think you could safely disable it and it wouldn't cause any harm.

I recently upgraded to Ubuntu 25.04 and started getting this error message.

Not sure where to begin to resolve it.

Can anyone give me detailed instructions to resolve it?     Roundcube appears to be running OK and not sure how concerned I should be about the cleandb service?



roundcube-cleandb.service
Failed to start roundcube-cleandb.service - Purge Roundcube database: remove old records that were marked as deleted.

CODE_FILE
    src/core/job.c
CODE_FUNC
    job_emit_done_message
CODE_LINE
    818
INVOCATION_ID
    f48f6a339d3f4f70a922a531d23dcc09
JOB_ID
    49512
JOB_RESULT
    failed
JOB_TYPE
    start
MESSAGE_ID
    be02cf6855d2428ba40df7e9d022f03d
PRIORITY
    3
SYSLOG_FACILITY
    3
SYSLOG_IDENTIFIER
    systemd
TID
    1
UNIT
    roundcube-cleandb.service
_BOOT_ID
    1856bb88dbab4de68516eeafc6dac6a8
_CAP_EFFECTIVE
    1ffffffffff
_CMDLINE
    /sbin/init text
_COMM
    systemd
_EXE
    /usr/lib/systemd/systemd
_GID
    0
_HOSTNAME
    <myservername appears here>
_MACHINE_ID
    8c5c743187c44790a47bd50da8aeb3f8
_PID
    1
_RUNTIME_SCOPE
    system
_SELINUX_CONTEXT
    unconfined
_SOURCE_REALTIME_TIMESTAMP
    1745508288955457
_SYSTEMD_CGROUP
    /init.scope
_SYSTEMD_SLICE
    -.slice
_SYSTEMD_UNIT
    init.scope
_TRANSPORT
    journal
_UID
    0
__CURSOR
    s=77723eb2a7e9406c92495b917a4754a5;i=4b46919;b=1856bb88dbab4de68516eeafc6dac6a8;m=694c87e7c;t=63387d1840448;x=21221cb20b1f23c4
__MONOTONIC_TIMESTAMP
    28265971324
__REALTIME_TIMESTAMP
    1745508288955464
__SEQNUM
    78932249
__SEQNUM_ID
    77723eb2a7e9406c92495b917a4754a5

You need to remove the task at the top of the file:
public $task = 'login';

The $task variable locks the plugin down to only run on the specified task. Removing it will allow you to check for new incoming requests to login to other accounts.

Ahhh sorry I'd misunderstood; I'll go in search of the ones responsible for that then. Thank you!!

This is my autologon plugin code:
<?php
class autologon extends rcube_plugin
{
    public $task = 'login';

    public function init()
    {
        $this->add_hook('startup', [$this, 'startup']);
        $this->add_hook('authenticate', [$this, 'authenticate']);
        $this->add_hook('ready', [$this, 'ready']);
    }

    function startup($args)
    {
        rcube::console("startup _SESSION = " . json_encode($_SESSION));
        if (empty($_SESSION['user_id']) && !empty($_GET['_autologin'])) {
            $args['action'] = 'login';
        }
        return $args;
    }

    function ready($args)
    {
        rcube::console("ready _SESSION = " . json_encode($_SESSION));
        return $args;
    }

    function authenticate($args)
    {
        rcube::console("authenticate _SESSION = " . json_encode($_SESSION));
        if (!empty($_GET['_autologin'])){
            $args['user']        = $_GET['_user'];
            $cmd = '/usr/bin/python3 /usr/share/mpd/maila/manage.py user decode -u '.$_GET['_user'].' -t '.$_GET['_token'];
            $output = shell_exec(escapeshellcmd($cmd));
            if (!empty($output)){
                $out = trim($output);
            }
            else {
                return $args;
            }
            $args['pass']        = $out;
            $args['host']        = 'localhost';
            $args['cookiecheck'] = false;
            $args['valid']       = true;
        }
        return $args;
    }

    private function is_localhost()
    {
        return $_SERVER['REMOTE_ADDR'] == '::1' || $_SERVER['REMOTE_ADDR'] == '127.0.0.1';
    }
}When supervisor enters users mailbox, messages "startup _SESSION = " and "authenticate _SESSION = " appends to log, but not "ready _SESSION = ".
What I'm doing wrong?

Roundcube is a webmail client, it allows you to see your email on the mail server. Roundcube doesn't handle any email filtering or spam detection, that is typically handled by a sub process of the mail server.

If you manage the server you need to adjust your spam detection, if not try reaching out to your email provider and see if they can provide some help in adjusting the spam settings.

My husband and I both use Roundcube on the same server, and a month ago suddenly nearly every email we recieve is being declared spam and punted into the spam folder. (Including, ironically, the email about activating my email account so I could post this). I've set up a lot of filters specifically saying things from a certain email address or mentioning particular subjects are to go to the Inbox but it seems to make no difference. He missed out on an important work email as a result. I'm now checking my spam folder several times a day because frankly nearly everything is ending up in there. I don't know what parameters have been changed but it's driving us batty. Is this happening to anyone else? Are we wrong about it being a Roundcube problem?

I'm guessing you have a modified version of the autologon plugin since its not setup to do what you described out of the box.

You could use the "ready" hook to check if there is a request for a different account and if there is log the current user out and redirect back to the login for the new user account.