2 Oct 2011 23:53
inappropriate result caching in router?
Ross Boylan <ross <at> biostat.ucsf.edu>
2011-10-02 21:53:03 GMT
2011-10-02 21:53:03 GMT
exim 4.69 reports it can't route lmtpbouncelong-ross <at> betterworld.us, despite this router: lmtp_bounce_long: debug_print = "R: lmtp_bounce_long for $local_part <at> $domain" driver = accept local_part_prefix = lmtpbouncelong- local_parts = +imap_users transport = cyrus_fail_long If I comment out the local_parts test, routing succeeds. ross is in +imap_users. Routing appears to fail because the result of a previous local_parts test (with different affixes) is used. Is this a bug? Is there anything I can do about it? The larger scheme is that I'm trying to send myself a notice if the lmtp delivery fails. To do that I plan to rewrite the envelope sender to, e.g., lmtpbouncelong-xxx and then intercept the bounce with a special router and autoreply transport. I don't want to use a regular bounce because the notice needs to avoid having any of the potentially problematic characters from the original message in it. DETAILS The debug log of the failure shows (in part) --------> local_long router <-------- local_part=lmtpbouncelong-ross domain=betterworld.us checking local_parts lmtpbouncelong-ross in "ross:karen:kelsey"? no (end of list) lmtpbouncelong-ross in "+imap_users"? no (end of list) local_long router skipped: local_parts mismatch(Continue reading)
RSS Feed