>Charles M. Hannum writes:
>>
>> >> Also, that doesn't resolve my VERP problem.
>> >
>> > Sorry, I thought it did. Why doesn't it?
>>
>> Uhhh, did you *read* my first piece of email? If I get a VERP address
>> of `[EMAIL PROTECTED]',
>> how pray tell is my mailing list software supposed to know that the
>> mail was actually sent to `[EMAIL PROTECTED]'?
>
> It's supposed to strip off the "foo-owner-mycroft-" prefix and the
> "@netbsd.org" suffix, and change the rightmost = into an @. Were you
> expecting me to write the script for you?
Actually, the prefix is `foo-owner-', *not* `foo-owner-mycroft-'.
(However, had you not made that mistake, your answer would be equally
useless.)
It would strip off `foo-owner-', etc., resulting again in
`[EMAIL PROTECTED]' -- which is not the
address the mail was sent to, and is therefore useless for automatic
bounce/reply processing.
There is no way for the mailing list software to get from
`[EMAIL PROTECTED]' to
`[EMAIL PROTECTED]' without having knowledge of virtualdomains.
That's not an acceptable solution.
I could possibly introduce some pure magic by having the final `-' in
virtualdomains be something else -- say, `&' -- and then explicitly
look for that in the VERP address, but that still fails to be
transparent.
