On Sunday 27 July 2003 11:39, Jeff Hedlund wrote: > Evren Yurtesen wrote: > > Why did you remove alias/forward page? it was handy to give a user alias > > capability but disable forwarding for that domain if we dont want them > > to be able to forward their emails. > > The removal was an attempt to make things easier to understand. > > There are still possibilities to patch qmailadmin to not allow remote > forwarding...
Honestly, if someone has asked me ( :-> ), I would have kept the words Alias and Forward, and even kept the interface the same, but just removed the Alias implementation methods and replaced them with &[EMAIL PROTECTED] methods so that maildir are never written to directly. That way one can still disable aliases or forwards. Forwards would have to be verified so that they definately don't contain local domain addresses. Perhaps another patch is in order? > > > Also, is it possible to disable user to set forwarding from qmailadmin > > when he/she enters to change his password? > > Not at this point, but it could be a future feature of qmailadmin > (filing an RFE on the sourceforge project page would be a good idea: > http://www.sf.net/projects/qmailadmin) > > Jeff -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net
