<div dir="ltr"><div>Might want to also consider having a more flexible approach as Alex had mentioned.<br></div>Will also help with some of the hardware requirements as you can also reject non-valid recipients at MTA as well as splitting the emails up, so the core MailScanner farm has less to do.<br>
</div><div class="gmail_extra"><br clear="all"><div>-- <br>Martin Hepworth, CISSP<br>Oxford, UK</div>
<br><br><div class="gmail_quote">On 11 July 2014 09:51, Sam Gelbart <span dir="ltr"><<a href="mailto:samg@synaq.com" target="_blank">samg@synaq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi All,<br>
<br>
We at SYNAQ use and have used Mailscanner for many years. As an Email Hygiene provider MailScanner has served us very well.<br>
However, as we have grown (very rapidly in the past 6 months, to many more customer domains) we have noticed some deficiencies in MailScanner.<br>
<br>
Below is a brief description covering our problem areas:<br>
<br>
Overview<br>
The issue has arisen due to SYNAQ's ever growing client base and the fact that we're provisioning more and more customers (and email domains) on our hygiene platform, and that more than one of these customer recipients/domains (and their applicable rulesets) are being addressed in the same email.<br>
<br>
Problem 1<br>
1) <a href="http://abc.co.za" target="_blank">abc.co.za</a> and <a href="http://xyz.co.za" target="_blank">xyz.co.za</a> are both provisioned on our platform.<br>
2) <a href="http://abc.co.za" target="_blank">abc.co.za</a> has quarantining of SPAM configured, while <a href="http://xyz.co.za" target="_blank">xyz.co.za</a> does not.<br>
3) Mailscanner accepts the message for processing but "chooses" <a href="mailto:user@abc.co.za">user@abc.co.za</a> and <a href="http://abc.co.za" target="_blank">abc.co.za</a> as the Message's "to_address" and "to_domain".<br>
4) MailScanner determines that the message is SPAM and because it has "chosen" @<a href="http://abc.co.za" target="_blank">abc.co.za</a> as the email domain it deletes the message as the configured spam action for @abc.coz.a is to delete.<br>
5) However the rule for <a href="http://xyz.co.za" target="_blank">xyz.co.za</a> is to store/quarantine spam. This does not happen because of the actions above and data is also never logged via MailWatch.<br>
6) The example above is a based on very simple scenario, and as you are aware this applies to many more complex rulesets (size, File Type etc) across the system.<br>
<br>
Problem 2<br>
1) <a href="http://abc.co.za" target="_blank">abc.co.za</a> and <a href="http://xyz.co.za" target="_blank">xyz.co.za</a> are both provisioned on our platform.<br>
2) A third party emails both <a href="mailto:user@abc.co.za">user@abc.co.za</a> and <a href="mailto:user@xyz.co.za">user@xyz.co.za</a> in a single email message.<br>
3) Mailscanner accepts the message for processing but "chooses" <a href="mailto:user@abc.co.za">user@abc.co.za</a> and <a href="http://abc.co.za" target="_blank">abc.co.za</a> as the Message's "to_address" and "to_domain".<br>
4) When the message is processed, the MailWatch.pm script receives a message object for SQL logging with data only for <a href="mailto:user@abc.co.za">user@abc.co.za</a> and <a href="http://abc.co.za" target="_blank">abc.co.za</a>; <a href="http://xyz.co.za" target="_blank">xyz.co.za</a> is never logged.<br>
<br>
Finally we have considered splitting incoming messages by recipient at an MTA level to address this problem, but our calculations show that it would require 3.5x more hardware to process this increased mail load. So for us a MailsScanner solution is ideal.<br>
<br>
Based on the above, could you tell me if there is anything that can be done from a MailScanner community point of view to help develop MailScanner functionality to address these issues?<br>
We'd be very happy to give a nice donation for a fix or patch.<br>
<br>
Also if the community has any ideas on other ways we can remedy this problem we welcome your feedback.<br>
<br>
Thanks and regards,<br>
<br>
Sam Gelbart<br>
SYNAQ<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
MailScanner mailing list<br>
<a href="mailto:mailscanner@lists.mailscanner.info">mailscanner@lists.mailscanner.info</a><br>
<a href="http://lists.mailscanner.info/mailman/listinfo/mailscanner" target="_blank">http://lists.mailscanner.info/mailman/listinfo/mailscanner</a><br>
<br>
Before posting, read <a href="http://wiki.mailscanner.info/posting" target="_blank">http://wiki.mailscanner.info/posting</a><br>
<br>
Support MailScanner development - buy the book off the website!<br>
</font></span></blockquote></div><br></div>