On Tue, 31 Jan 2006, Gary Palmer wrote: > > I have a "custom" lookup implimented in perl which is used to set the > return_path variable on the outbound transports. I am wondering what is the > best way to force the message to be deferred if the lookup encounters a > problem? Returning a forced failure just means the message is delivered with > the old return_path, which is undesirable as it is likely unroutable outside > of the local system. The docs say "if it fails for another reason, delivery > is deferred". What would "another reason" be in this situation?
A non-forced string expansion failure. From the perl point of view, returning undef causes a forced failure whereas calling die (I think) is an unforced failure. Tony. -- <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> http://dotat.at/ ${sg{\N${sg{\ N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\ \N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}} -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
