Topic: Throttling not working when sending from fake email address
======== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.8.6
- Linux/BSD distribution name and version: CentOS 6
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx):Apache
- Manage mail accounts with iRedAdmin-Pro? Yes
- Related log if you're reporting an issue:
====
A customer's email account got hacked (or he gave it to someone through phishing). I do limit every account to only be able to send x emails per 24 hours so it shouldn't really be a problem.
But... when they (the hackers) send email through my server using the hacked account but configure their email client so the emails are sent from a non-existing address in that domain, the server just accepts the email and sends it out, while Cluebringer is not even tracking it, as not linked to an account.
The easiest solution I can think of is to only allow people to send emails using the address they connect with as the sender, but I don't know how to configure that.
Any other solution to prevent my server from potentially sending out millions of emails because one of the customers got hacked would be very welcome
----
Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.