Hey Bill,
I totally agree. I will put back in the check (for autoresponders)
to not let local users set one up for a current address.
Also I suggest we change a few wordings. Replace autoresponders
on the main with something like "Mail Robot". And replace
"Owners address" with something like "Send a copy to:"
I agree with removing the show redirect code. That functionality
is handled by the modify user page.
I also think when a user logs in they should be send directly
to the modify user page, since that is the only thing they can
do.
I will work on these changes today and post an update
Ken
Bill Shupp wrote:
>
> Ken,
>
> With the addition of your modify user code, I'm starting to think that it
> would make sense to separate autoresponder functionality from vacation
> functionality. For example:
>
> [EMAIL PROTECTED] logs in creates an autoresponder for [EMAIL PROTECTED], who
> is also a pop user. Then user [EMAIL PROTECTED] logs in and selects "show
> redirect", and sees the contents of the .qmail-test file. (Try it, it does
> this)
>
> I know this probably wouldn't happen much, but rather than spend time
> cleaning up the "show redirect" part to detect if the .qmail-test file
> contains redirect or autoresponder info, maybe it would make more sense to
> go back to your original philosophy: autoresponders should NOT have an owner
> address that is the same as the autoresponder address. Since a vacation
> message solution is already in place, this shouldn't be a problem for
> anyone.
>
> Also, now that "modify user" handles forwards, perhaps when non postmaster
> users log in, they shouldn't see "show redirect" anymore. Just "modify
> user". Couldn't the redirect override the forward settings created by the
> modify user page?
>
> I'll be happy to provide the patches for these two things...
>
> Thoughts?
>
> -Bill
