On Wed, 2 Jul 2008, Marc Perkel wrote: > > I know this isn't going to be simple but it might not be to complex. > Exim would have to be expanded to run multiple queues rather than just > one. Then you would have to add some logic to move messages between the > queues should the first attempt fail. OR - send the message to a > secondary "retry" server with a disk based queue for retry processing. > You might also have some overflow logic should the ram drive fill up > that it switches to disk based queueing or stops taking new connections > on queue full. > > I'm thinking these kinds of changes might not take too much > restructuring to accomplish. >
So, write a wrapper for exipick or similar, and run a separate exim instance for the reliable queue. -- -------------------------------------------------------- Dave Lugo [EMAIL PROTECTED] LC Unit #260 TINLC Have you hugged your firewall today? No spam, thanks. -------------------------------------------------------- Are you the police? . . . . No ma'am, we're sysadmins. -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
