> UsersRepositoryAliasingForwarding (URAF) take each recipient of the mail
> and for each send the mail to one or more of this:
> - error : if it find any problem in the aliasing/forwarding
> - remoteRecipient: if a forwarding has been specified
> - localRecipient: if an alias has been specified
That is the same with a VUT. :-)
> I think that there is a difference that we should analyze:
> In URAF you can put a local address both in alias and in forward: the
> result is different because the aliasing is done on the current mail
> that will move forward in the processor while the forwarding creates a
> new mail that will enter the spool from the root. VUTs do not allow
> this distinction because local addresses are considered aliases while
> remote addresses are sent to the root processor in a new mail.
I don't believe that the differences are intentional or significant.
> My best solution is to make it returns a collection of "destinations"
> including "errors", "forwards", "aliases".
Return to what?
> Having this association between an input recipient and its "expansion"
> will allow us (later) to manage DSN correctly. In fact we may need to
> track the original recipient and its rewrites to be able to create a
> compliant DSN.
That would be equally so for a VUT. The point is that there are no
differences. We should merge the lot under a single virtual user table
interface, whatever changes we feel we should make to it.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
