------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1139 --- Comment #2 from Julian Gilbey <[email protected]> 2011-08-29 12:55:28 --- I see that you are right, but for a slightly non-obvious reason, and therefore it will fail in more complex cases, such as mine. The addition of the local_user_suffix clauses to the localuser router has *two* separate purposes: (1) It means that emailing [email protected] will save the email address in the mailbox of user if user does not have a forwarding file. (2) It verifies the address [email protected] during the verification process. However, what would happen if the site wishes to behave as follows: an address [email protected] is only valid if the user has a $home/.forward-foo forwarding file present? Then the userforward router would include the options: local_part_suffix = -* local_part_suffix_optional file = $home/.forward$local_part_suffix require_files = $local_part:$home/.forward$local_part_suffix no_verify Then [email protected] will use .forward-foo if that file exists, otherwise it should bounce as undeliverable. But then, adding the local_user_suffix clauses to the localuser router would mean that it would instead be dumped into the user's mailbox, and without either that clause or my suggestion, the address would be unverifiable. I think that the documentation could be improved slightly, perhaps, or maybe this example could be offered as an alternative; it took me a while to figure out what exactly was going on, and such an example would have been very useful to me. Julian -- Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
