[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Mail Forwarding
- Subject: Re: [cobalt-users] Mail Forwarding
- From: "Rob Evans" <robe@xxxxxxxxxxxxxxxxxxx>
- Date: Thu Jan 6 15:04:03 2000
- Organization: Fujitsu Australia Software Technology
Jason Braverman wrote:
> Whenever I try to do that on the raq2 in the web area that asks for
> FORWARDING: it gives me an error saying that
>
> someone@xxxxxxxxxxxxx,\username is not a valid email and that a valid
email
> looks like someone@xxxxxxxxxxxxx
>
> Any idea what I am doing wrong?
>
> -Jason
On the Qube1 (& RaQ1?) this was allowed because the "Forward e-mail to:" was
taken as entered, not being checked for validity.
On the Qube2 & RaQ2 it is being checked for validity and only one address is
being allowed. The programmer seems to have assumed that was sufficient,
considering that a mailing list facility had been added. But this is not
true, as the two facilities have different purposes - from the user
perspective.
Since this topic regularly turns up on this list, again I ask the question
of Cobalt:
Could the logic used (on Qube2 & RaQ2) to parse "Forward Email To" be
changed to handle multiple addresses, like that for mailing lists, so that
the user can specify multiple forwarding addresses, allowing the keeping of
a local copy of forwarded mail?
The suggestions about editing the aliases file are off the mark for two
reasons:
1) the basic idea of these boxes is that straight-forward processes should
be carried out through the web interface, most definitely when that is by
individual users;
2) we don't want individual users telneting on (particularly not as "root")
and most likely corrupting things.
Regards, Rob Evans