On 27 Aug 2010, at 5:57 AM, Mohammed Alli wrote: > That's is correct. An admin can definitely do that, but that is a lot of > work. The simplest solution is to use the generic @domain.com as the relay > entry, to allow all recipients for those domains.
This is already catered for you can just pull the domain name from the DB and prepend the @ sign to it. > The only drawback is even if the user doesn't exist, that email will hit the > receiving MTA. Thats correct but there are other mechanisms to check user existence on the final destination server like milter look ahead, or LDAP lookups > I'm lucky I don't deal with tons of users, so I've created an sql dump for > easy importing. You really do not have to maintain two lists of users, the MTA already has that info so the gateway should just look it up. > > I would like Baruwa to have an easy to use page made specifically to list > relay_recipients on a per-domain basis that is available to admins and domain > admins. This is already possible as the recipients are the user accounts on the system, In a SAAS environment it would not be practical to maintain lists of actual accounts, that is why there is the external authentication and forward lookup mechanisms that can be used. > This should have functionality of letting admins add/remove relay_recipients > or if global (@domain.com). All this can be managed on the destination systems and have your gateway look that up, the globals can be pulled from the DB as described above. > I don't know if this is something that would make sense though, let me know > what you feel about it. The project aims is to be able to drop in a gateway with very little admin overhead. -- JAVA - write once, crawl anywhere. _______________________________________________ Baruwa mailing list [email protected] http://lists.baruwa.org/mailman/listinfo/baruwa
