Re: Virtual delivery agent

From: Wietse Venema (no email)
Date: Thu Aug 01 2002 - 10:10:07 EDT


Joshua E Warchol:
> > Question.
> >
> > What is making it hard to use the virtual delivery agent, apart
> > from the inability to execute commands, which is unlikely to ever
> > happen?
> >
> > The virtual delivery agent was added several years after the initial
> > design, and it does not fit perfectly. I would like to make it a
> > realistic option to do this:
> >
> > local_transport = virtual
> > mydestination = $virtual_mailbox_maps
> >
> > or something morally equivalent.
>
> Right now I've got local_transport set to virtual, and I have a seperate
> map for mydestination, which works "ok". The filter I need to use isn't
> perfect because it returns all the users for a domain, which takes longer.
> I fault myschema for this, not postfix.
>
> The problem I was referring to was this. My users want to be able to setup
> "forwarders" within their domain that do not have a mailbox, just forwarding
> off to another host (AOL, whatever). For this I need to use a virtual_maps
> map. There is probably some overlap between what I use virtual(5) for and what
> I use virtual(8) for.

I see. Using the virtual(5) map as duct tape is perfectly OK here.
The only bad thing is the misleading name of the parameter.

> virtual(8) is a fantastic part of postfix. I can't imagine doing this
> with real users.
>
> Running commands is not an requirement at all, just being able to bounce
> messages off to other addresses.

I'm glad virtual(8) works well. I suppose that for many sites it
could be the default delivery agent. It would need a few transport
map entries to route UNIX shell accounts off to the local delivery
agent as discussed in a thread yesterday.

        Wietse
-
To unsubscribe, send mail to with content
(not subject): unsubscribe postfix-users








Hosted Email Solutions

Invaluement Anti-Spam DNSBLs



Powered By FreeBSD   Powered By FreeBSD