We offer store and forward services for a handful of clients, and we've also found that it was easier, more effective, and cheaper to do this with a different product than Imail. The biggest problem we had with using Imail (as configured in KB) is that we were accepting 'all' mail for the domain (like having a 'nobody' alias, and all associated headaches). All of that mail was re-directed to the destination mail server and delivered or bounced (more commonly).
Given the very high, increasing, and universal %age of msgs to unknown recipients, any MX must have the db of known recipients, or the MX will become inundated with undeliverable delivery failure/postmater msgs as the next-hop mailbox server rejects unknown recipients.
The only downside we've found occurs when the destination mail server is unreliable. Alligate will queue messages that can't be delivered if the destination server is unreachable, and attempt delivery periodically, but if the destination mail server is up and down intermittently, the queue may get very large and problems ensue.
very large deferred queues cause slow-down problems for any MTA, but should not cause any other problems (like total failure).
If an MX is going to be in the mail relay business, it really needs to be able to handle/hold 2 days of non-deliverable mail "gracefully".
Len
_____________________________________________________________________ http://IMGate.MEIway.com : free anti-spam gateway, runs on 1000's of sites
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
