1. you do not wish authenticated users to be able to send mails except to local users
2. you do not wish authenticated users to be able to send emails except to local users AND an additional set of domains
With #1 that is easy. With #2, you'll need a custom mail listener as our present behavior is to allow local users to send email to anyone they like. We would accept such a mail listener of course as a contribution.
basically, there will be no sending of email from users, except possibly an admin user, or support user
if that doesnt work, then I could just have the mail listener send the email, manually, i.e. connect to another mail server, and send while in mail listener, this is more just for admin, performance, and possibly support instances
This mail server is strictly for receiving emails from legitimate domains, to registered users
it does not have POP enabled, in this instance, it is more of a Application server, in that there really is no user interaction
not really talking looking up to see if there on blocked mail servers list, per se, but as stated, would like to add it to where only certain institutions can send email to users, institutions on a list, or in a dbase, etc.
Okay so you need a custom mail listener for this. If you can make it generic (have it check a domain group) then we'd take it.
i gots to go to sleep...but
isnt that higher up in the "food chain", couldnt I do it, when getting the "Message-From" or whatever header, or am I lost at exactly where the mail listener is in the food chain
seems like the mail will still be received, but the message listener will either just toss it, based on the domain name, in dbase or keep it, and handle however
have a good night man!
It does happen after the mail has been received. It will be expunged though. If we moved processing up the chain it would have a greater overall cost. I still may offer such an interface, but it will be costly.