Consider one domain davidfavor.com and a messaged delivered to the [email protected] user by a cronjob using sendmail. Thus the message is enqueued into exim.
I'd like this message to then lookup the MX records for davidfavor.com which are net1.coolsurf.com and net2.coolsurf.com and simply deliver the message to the first active MX record. If a message is enqueued for [email protected] then this message follows the same logic, lookup MX records and take first active one. In other words, I only desire exim to handle outgoing mail, never incoming mail on port 25. I've tried this: domainlist local_domains = davidfavor.com : coolsurf.com : ... ... ... ... begin routers smart_route: driver = manualroute domains = +local_domains transport = smtp route_list = * net2.coolsurf.com net1.coolsurf.com dnslookup: driver = dnslookup self = send transport = remote_smtp which results in the new error... 2009-05-28 10:45:57 cwd=/common/cron 5 args: exim -d -odf -t [email protected] 2009-05-28 10:45:57 cwd=/var/spool/exim 9 args: /usr/sbin/exim -d=0xfbb95cfd -odi -t -oem -oi -f <> -E1M9jfx-0002Hk-6c 2009-05-28 10:45:57 1M9jfx-0002Hl-73 <= <> R=1M9jfx-0002Hk-6c U=exim P=local S=683 T="Mail failure - no recipient addresses" from <> for [email protected] 2009-05-28 10:45:57 cwd=/var/spool/exim 5 args: /usr/sbin/exim -d=0xfbb95cfd -odi -Mc 1M9jfx-0002Hl-73 2009-05-28 10:45:57 1M9jfx-0002Hl-73 Error in smart_route router: unknown routing option or transport name "net1.coolsurf.com" 2009-05-28 10:45:57 1M9jfx-0002Hl-73 == [email protected] R=smart_route defer (-1): error in router: unknown routing option or transport name "net1.coolsurf.com" W B Hacker wrote: > David Favor wrote: >> Maybe I require to use something like this... > > *snip* > > Lots of data posted. > > Very little clear *information* as to what you inted to do vs are doing. > > 'port 25' - referenced several times.... > > Could you provide, for example <an_IP>:25 <an_other_IP>:25 for each of the > players when describing what they are intended to do. > > It would also help to tell us what specific function 'qpsmtpd' is expected to > perform for this setup > > AFAIK, qpsmtpd was written to provide Exim-like functionality for <another> > MTA > that did not have what Exim already has built in. > > More often than not, well-coded compiled 'C' will outperform equally > well-coded > interpreted perl> > > Bigtime. > > Unless you are doing something exceptionally pre-verted, you may not be > heading > for the best solution available to you. > > Bill > > -- Love feeling your best ever, all day, every day? Click http://RadicalHealth.com for the easy way! -- ## 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/
