Mayuresh, I dont know if this helps:
I worked on Zimbra 7 on RHEL for last 15 days. Zimbra uses Postfix as an MTA. (You may need to additionally install/config DNS server for a DNS domain in question.) Zimbra gives you simple(r) command line interface to its Postfix MTA configuration to allow mail relay. I strongly suggest you dont allow unauthenticated relay on MTA unless MTA is inside a firewall. Otherwise your MTA will get blacklisted in no time. If MTA is inside firewall, allow unauthenticated relays on it, and allow connections to port 25 ONLY from local IP addresses ( like 192.168.1.0/24etc). cheers, shyam .... On Thu, Sep 8, 2011 at 9:12 PM, Mayuresh <mayur...@acm.org> wrote: > Wondering what will be a good smtp setup for a desktop machine given some > needs expressed below: > > 1. Client invokes sendmail: > > Generally acceptable and perhaps most common setup. For large mails > sometimes the remote server interaction hangs. There is no reliable queue > mechanism. > > Feel much comfortable if the moment you say "send" the mail goes to a > local queue and a daemon keeps track of it till it is sent. If it could > not send it, it returns it back to you. > > > 2. Postfix (or any good smtp daemon): > > Meets above mentioned requirements. Only problem is your username and > password to authenticate to relay host needs to be supplied once as root. > There is no client side way of doing this. > > Trying to find a way by which relay authentication information is > configurable entirely on client side (without having to use root login) > while achieving all benefits that the smtp server provides. > > Somewhat like postfix with authentication information (hash map files in > case of postfix) allowed to be maintained by individual non root users. > > Mayuresh. > > _______________________________________ > Pune GNU/Linux Users Group Mailing List > _______________________________________ Pune GNU/Linux Users Group Mailing List
