webportal to adjust customer settings / lamp, authentication, mysql, data processing

Freelancer have to: - code a new web-interface for a spamfilter-product with Laravel/CodeIgniter that runs on regular linux LAMP with following functions and release it on an empty employers linux-system. Freelancer gets: Root-Access to debian 10 virtual machine fully installed LAMP with example-data in mySQL-DB Web-Interface needs to have all following functions: - provide login-capabilties by USER+Password from MySQL/MariaDB (DB) with additional option for 2FA (just option, doesnt have to be implemented now) - store passwords only salted & hashed in database - Option to provide web-interface to customers in different languages by just modifying a single "translation-file" (just option, no additional languages need to be implemented now) - UTF8 as default charset/language - option for customer to change own password - allows multi-login (different customers or same customer from multiple devices) and take care of locking - provide option to customer to re-sent lost password to customer-address (from DB) - auto logout after X-minutes inactivity - Show customer own domain/s (from DB) - show contract/product details (package-size and productname) from DB MILESTONE 1 IS RELEASE ------------------------------------------------------------------------------------------------------------------------------------------------------- - show if customer has received mails for more mailboxes than he licensed (count uniq RCPT-TO-addresses and record status) - dashboard, that shows overall filter-stats (blocks/rejects/delivers) per day / week / month / year (customer can select timerange) (data from DB) - filter to search through stats (search for all rejected mails in last 5 days or 3 weeks, or yesterday from sender bad-sender@[login to view URL] or to recipient mike@[login to view URL]) MILESTONE 2 IS RELEASE ------------------------------------------------------------------------------------------------------------------------------------------------------- - let customer maintain own black- and whitelists on a per domain or address-basis (add,delete,modify,disable,enable) like blacklist all mails from bad-sender@[login to view URL] for own domain [login to view URL] whitelist all mails from good-sender@[login to view URL] to all domains whitelist all mails to admin@[login to view URL] - sanity check for entries, no blacklist, if there is already a matching whitelist-entry - auto-export of all black-and whitelists settings (for all customers!) everytime, any customer changes a white-blacklist-setting to a local directory on webserver in a single text-file in the following form: Example: [login to view URL]: admin@[login to view URL] john@[login to view URL] postmaster@[login to view URL] [login to view URL] #blacklist uniq-rule-id { from = "bad-sender@[login to view URL]"; rcpt = "@[login to view URL]"; apply { actions { reject = yes; } } } #whitelist uniq-rule-id { from = "good-sender@[login to view URL]"; rcpt = "john@[login to view URL]"; whitelist = yes; } MILESTONE 3 IS RELEASE ------------------------------------------------------------------------------------------------------------------------------------------------------- DATABASE EXAMPLE: table-users: customernumber, username, admin-email-addy, hashed-and-salted-password, package-size, productname 1,mikecorp,admin@[login to view URL],$asdfasdf$, 50, binford 4000 table-domains: customernumber, domains, sender-blacklist, sender-whiltelist,recipient-whitelist 1,[login to view URL];[login to view URL],bad-sender@[login to view URL],good-sender@[login to view URL],postmaster@[login to view URL] table-stats: customernumber, domains, blacklist-entries, whitelist-entries table design is not final and can/should be discussed.