Stephen Warren <[EMAIL PROTECTED]> writes:
> Lloyd Zusman wrote:
>>
>> [ ... ]
>>
>> | /path/to/tmda-filter --environ=VHOME=/var/vmail/virtdomain.com/user \
>> --vhome-script=/path/to/some-script
>>
>> where where "user" and "virtdomain.com" are different for each email
>> account, and where "some-script" simply does an "echo $VHOME".
>>
>> ... or some such thing.
>>
>> Does that seem right?
>
> That makes perfect sense to me.
Thanks.
> [ .. .]
>
> That said, you're obviously telling postfix where to deliver the mail
> for each virtual user, since each has a separate maildir. One would
> *assume* that postfix would also do something sensible and look for
> .forward etc. in a similar place, but I'm just guessing now!
>
> Hope this helps, although probably not:-)
Well, it does indeed help. I'll check to see if the ~/.forward file can
be indeed found.
And after reading more postfix docs, I think that I have an alternative,
in case ~/.forward cannot be found: I can put a "spawn" or "pipe" recipe
in "master.cf" to run a script that takes ${recipient} as one of its
command-line arguments. Then, in "main.cf", I can refer to it as
"unix:private/myscript".
In my example, the ${recipient} would be set to "[EMAIL PROTECTED]".
Inside this script, I could parse it and use its user and domain parts
to locate the appropriate TMDA config file and to generate an
appropriate invocation of tmda-filter.
... or something like that.
So one way or the other, I think that I can make this work.
Once I get it working, I'll post my results here, in case they might be
of general interest.
Thanks again for all your help.
--
Lloyd Zusman
[EMAIL PROTECTED]
God bless you.
_____________________________________________
tmda-users mailing list (tmda-users@tmda.net)
http://tmda.net/lists/listinfo/tmda-users
