• Add encryption option in user settings
• By enabling this option user should enter extra encryption password that will be used to encrypt all emails starting from the point when encryption was enabled
• Encryption option will generate asymmetric encryption keys locked with password entered
• Once encryption option is enabled all emails that will be received will be encoded with stored in database public key.
• To read emails user need additionally enter password for private.key when he try to open encrypted email
• Optionally password might be stored in web mailbox
• Encrypted emails will be visible in web and grpc interfaces only and non-accessible from pop3/imap protocols.

When some emails are removed email list doesn't fetch new emails if are from server

• Add option in personal settings to enable 'Trash' auto cleanup
• Add option in personal settings to set auto cleanup time. One of: 1d/1w/1y
• Add 'Trash' auto cleanup based on selected options.

Selection list is not reset when page changed, but should

• Add form to remove emails in user settings
• Add server-side logic
• Make possible to remove only non-main emails

User should be able to make mails read/unread when multiple emails selected

When i want to build the project i am seeing this error.

now db18 version is installed. which berkeleydb version is suitable with your github.com/semlanik/berkeleydb ?
lastly you fixed pointer issues for which version of berkeleydb?
thanks.

github.com/semlanik/berkeleydb

/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:44:7: could not determine kind of name for C.DBC
/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:19:15: could not determine kind of name for C.DB_CREATE
/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:20:15: could not determine kind of name for C.DB_EXCL
/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:25:16: could not determine kind of name for C.DB_INIT_MPOOL
/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:33:14: could not determine kind of name for C.DB_QUEUE
/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:21:15: could not determine kind of name for C.DB_RDONLY
/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:22:15: could not determine kind of name for C.DB_TRUNCATE
/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:34:14: could not determine kind of name for C.DB_UNKNOWN
/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:53:9: could not determine kind of name for C.db_create
/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:229:27: could not determine kind of name for C.db_full_version
/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:245:9: could not determine kind of name for C.db_strerror
/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:210:9: could not determine kind of name for C.go_cursor_get_first
/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:221:9: could not determine kind of name for C.go_cursor_get_last
/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:188:9: could not determine kind of name for C.go_cursor_get_next
/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:199:9: could not determine kind of name for C.go_cursor_get_prev
/root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:172:9: could not determine kind of name for C.go_db_cursor
cgo:
cc errors for preamble:
In file included from /root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:6:
./bdb.h:5:29: error: expected parameter declarator
extern int go_db_open(DB *, DB_TXN *, char *, char , DBTYPE, u_int32_t, int);
^
/usr/include/db.h:91:17: note: expanded from macro 'DB_TXN'
#define DB_TXN 0x80000000 / Do transactions. /
^
In file included from /root/go/pkg/mod/github.com/semlanik/[email protected]/bdb.go:6:
./bdb.h:5:29: error: expected ')'
/usr/include/db.h:91:17: note: expanded from macro 'DB_TXN'
#define DB_TXN 0x80000000 / Do transactions. */
^
./bdb.h:5:22: note: to match this '('
extern int go_db_open(DB *, DB_TXN *, char *, char *, DBTYPE, u_int32_t, int);
^
./bdb.h:11:24: error: unknown type name 'DB_ENV'
extern int go_env_open(DB_ENV *, char *, u_int32_t, u_int32_t);
^
./bdb.h:12:25: error: unknown type name 'DB_ENV'
extern int go_env_close(DB_ENV *, u_int32_t);
^
./bdb.h:20:31: error: unknown type name 'DBC'
extern int go_db_cursor(DB *, DBC **);
^
./bdb.h:21:31: error: unknown type name 'DBC'
extern int go_cursor_get_next(DBC *, char *, char *);
^
./bdb.h:22:31: error: unknown type name 'DBC'
extern int go_cursor_get_prev(DBC *, char *, char *);
^
./bdb.h:23:32: error: unknown type name 'DBC'
extern int go_cursor_get_first(DBC *, char *, char *);
^
./bdb.h:24:31: error: unknown type name 'DBC'
extern int go_cursor_get_last(DBC *, char *, char *);
^
9 errors generated.

Implement multiple email selection in web interface

there is no main.ini default?
application can not start. file seems deleted.

• Add option to enable/disable two-factor authentication to config file
• As second authentication factor Telegram bot will be used
• When 2 factor authentication is enabled, user should scan 2 factor token from his display by using smartphone and and send this token to assigned to server telegram bot.
• Telegram bot should be run on related webserver and confirm "telegram user" assignment to gostfix user
• When user will try to log in next time, after successful basic authentication telegram bot will send question with 2 selection(Yes/No) to confirm logging in, in case of success server will redirect to mailbox. Otherwise redirect to login page

Controlls to manipulate multiple emails remain active after switching between folders/mailboxes

Implement pop3 email list function.

• Add form in user settings
• Add server-side functionality
• Add option in config file to enable and disable email management for users

Implement removal of multiple emails selected in web interface

• Add following user roles with privileges:

1. Admin - the server maintainer and superuser. Have access to all manipulations with users and mailboxes (except access to mailbox internals, like attachments and mail bodies). Might be only one on server. User is configured while initial installation and could be changed in configuration file only.
2. Moderator - server moderator, has access to users and mailboxes. May add or remove user mailboxes also enable or disable access to account
3. User - may have full access to own mailboxes (including access to mailbox internals, like attachments and mail bodies) and add/remove emails for own account

Implement pop3 email read/unread functionality

Implement pop3 email delete functionality

User should be able to reply inbox message

Implement base pop3 server