Small update — it now works both ways

In addition to attaching Paperless documents while composing, you can now save an attachment from a received email straight into Paperless without leaving Roundcube:

• A "Save to Paperless" button on each attachment, plus one in the attachment preview toolbar (after Open).
• The file is uploaded server-side; the plugin then polls the Paperless consume task and reports the outcome — saved ✓ / already exists (duplicate) / failed.
• Same security model as before: the per-user API token is stored encrypted, and the token + Paperless URL never reach the browser (single server-side proxy). Roundcube 1.6.x/1.7.x · Elastic skin · PHP 7.4+.
  

Shipped in v1.2.0. Code, install & docs: https://github.com/dodjango/roundcube-paperless-attach — composer require dodjango/paperless_attach

Feedback and testing on other 1.6.x or 1.7.x setups is very welcome!

What it is
I built a plugin that brings Paperless-ngx (a self-hosted document management system) into the Roundcube compose window: attach documents from Paperless directly while writing an email, instead of downloading and re-uploading them.

My typical use case: replying to an email and attaching a document I already have filed in Paperless — hit "Attach from Paperless", search, pick, send. 

What it does
 

• "Attach from Paperless" button in the compose window
• Search & filter by tags, correspondent, document type and date
• Selected documents are fetched server-side and attached to the outgoing mail

Implementation notes
 

• Roundcube 1.6, Elastic skin only; PHP 7.4+
• Per-user API token stored encrypted (rcmail->encrypt/decrypt); the browser never sees the token or the Paperless base URL — all Paperless traffic is server-side
• Attach happens at send time via the message_ready hook, so the download-induced session reload doesn't drop the attachment

Install
composer require dodjango/paperless_attach
Code & docs (GPL-3.0): github.com/dodjango/roundcube-paperless-attach

  Feedback welcome — issues and PRs appreciated.

All solved. Syntax is correct:

./bin/updatedb.sh --dir=./SQL --package=roundcube

And another error appear:

DB Error: [1146] Table 'roundcubemail.uploads' doesn't exist (SQL Query: SELECT * FROM `uploads` WHERE `session_id` = '...' AND `group` = '...' ORDER BY `created`) in /usr/local/www/roundcube/program/lib/Roundcube/rcube_db.php on line 553 (POST /mail/?_task=mail&_from=compose&_id=...&_uploadid=...&_action=upload)

and well, I find updatedb.sh - when run it, error:
ERROR: Database schema directory not specified (--dir)

running with  --dir=SQL --package=roundcube, error:
ERROR: Specified database schema directory doesn't exist.

What is correct syntax for updatesb.sh ?

Thanks, I did it same by adding

 ALTER TABLE `session` ADD `expires_at` DATETIME;

Because in freebsd can't find updatedb.sh script.

You need to update the Roundcube database, run the <RC root>/bin/updatedb.sh script.

Hi all!
After upgrade roundcube to 1.7.1 get error:
 DB Error: [1054] Unknown column 'expires_at' in 'INSERT INTO' (SQL Query: INSERT INTO `session` (`sess_id`, `vars`, `ip`, `expires_at`) VALUES ('...', '...', '10.10.0.1', now() + INTERVAL 36000 SECOND)) in /usr/local/www/roundcube/program/lib/Roundcube/rcube_db.php on line 553 (GET /mail/)

what type of column 'expires_at' I must insert to db?

Upgrade from ports in freebsd.

You need to contact your email provider, Roundcube is a webmail client and doesn't manage or have access to your email account.

someone hacked or I forgot my account password here is the mail [email protected] 

// https://fotora.ru/uploaded/?ID=GAFPO31052026210239 \\ <<--- here is a photo proof that I was in this account, I use this account for war thunder

I suggest you find an example of a message, may be 2 or 3, if possible, and clearly describe which filter rule you think should have applied when you contact your provider.

There is no filtering built into Roundcube, the info you posted shows the managesieve plugin which suggests they are using sieve on the mail server to do the filtering. What you see in Roundcube is only for managing the rules. They can look into why the rule was not triggered.

Using the managesieve plugin you cannot rerun rules or access logs. The rules are applied a the time the message is received only.