Archive: EXIM modification to support email filtering based on sender and recipient email addr
Budget
78$
per month
Posted: 5 years ago
Closed
- Description
- Please see attachment for better formatted description
I would like to filter incoming emails based on their email addresses and the implicit meaning I have assigned to those email addresses. This will be running on a dedicated cPanel server running CentOS to which we will have ROOT access. Development will be on a cloud based development environment in the same software configuration as the production system.
1. Consider an incoming email address of the format: @
Where
will be typically “z.” or “y.” or anything else. Only “z.” or “y.” have relevance for this project. Anything else will be passed through for conventional EXIM processing.
will be a character string that will be a substring search argument
will be a domain hosted on a dedicated Linux cPanel server
2. If is “z.” on the incoming email, a match will be checked for between the on the incoming TO: email address and the sender’s domain. The match will be performed as a substring test to determine if is contained within the sender’s FROM: domain name (excluding everything to the left of the @ sign). If that match is true, the email use is considered as valid and the incoming email is redirected to the email address, such as [email protected] where my important email resides. If the match is not true, the email is considered as fraudulent and is redirected to the email address, such as [email protected] where suspected emails are stored for future inspection.
3. If is “y.” on the incoming email, all such incoming emails will be considered as valid with no match being required between the on the incoming TO: email address and the sender’s domain. All such email will be redirected to the email address, such as [email protected] where my important email resides.
4. This is all the implementation that is required. A nice improvement would be if this could be table driven, with the being the first value in the table, an indicator of match vs. wildcard acceptance action as the second value in the table, the email address being the third value in the table, and the email address being the fourth value in the table. This would allow this more generalized implementation to be used for multiple email addresses hosted at to use the same email filtering by assigning separate character string to each of the multiple email addresses.
Skills:
linux,cpanel,Community Enterprise Operating System (CentOs),integrated development environment (IDE),software development,system administration
- Category
Drag