Harish/Gora/Noufel, Actually the rules I am guessing are not just based on fields. I guess sometime later we want to do some some deep diving there. So I want to do some stuff with a programming language may be write and read stuff to some redis kind of in-memory database.
A typical rule I want to write is rate limiting for a particular email id to certain specifc domains. Or based on particular set of message reroute that through an alternate email server or use some Amazon SES kind of an API. Standard Postfix stuff I have seen is just not flexible enough. I saw something called milters, but not sure whether the project is dead. Also mails going out could be as high as 30,000 emails an hour during peak hour. So 30 K mails may have to parsed, I am not very sure about Python performance there. But we can always throw more hardware to solve performance issue. To define the problem. 1)I set up an interim SMTP server which listens to a bunch of rules 2) All users authenticate to the SMTP server and sends the mail using the server. It would be almost like a email relay kind of connection. 3) Once the email arrives, it parses the email, checks some database etc, does some simple number crunching, 4) And then reroutes the mail through an alternate SMTP server to reach the customer. 5) It may also decide not to send the mail. You can think off this as an outbound spam gateway. Ramdas > > While I have no knowledge of Lamson, I would echo Noufal in > recommending something like postfix. Cannot go into details without > knowing more about your requirements, and anyway those would not be > germane to this list, but postfix's transport system is very flexible > in allowing mail redirection. IMHO, one should use the right tool for > the job at hand. > > Regards. > Gora _______________________________________________ BangPypers mailing list BangPypers@python.org https://mail.python.org/mailman/listinfo/bangpypers
