Linuxconf 1.9r6 (Test release)

Sendmail configuration

There was a limitation in the Complex (user) routing. It was not possible to reroute a message to a virtual email domain on the same server. The original algorithm only allowed for redirection to a local account or to another mail server. This is now more general.

POP account password

There is no easy way for a POP account user (or PPP user) to change his own password. While there are some protocol allowing that, few client software support them. Linuxconf now provide an interface using its html mode to do just that. The interface support both the normal users and the users of the virtual email domains. To access this facility, a special URL has been defined. It is

http://your_server:98/htmlmod:userpass:

where your_server is one potential name use to get to your server (and its multiple virtual email domain). A good idea is to enter this URL in one the HELP page of the server. This is a new feature. Comments are welcome on this topic.

Virtual Email domains

vdeliver

vdeliver had a small buglet which causes a glitch. While it was delivering properly the messages, it was reporting a failure. Sendmail was sending back to the sender an error message about it.

vpop3d

Few people were having a problem with vpop3d. Some are using shadow password, other are using normal password and now many are using PAM based systems (such as RedHat 4.0). This is causing problem as Linuxconf's users can't just use the binary release I am doing. While vpod3d can be compile for normal or shadow password, unlike Linuxconf which adapt dynamically, has to be recompiled to support one or the other.

To allow for an easier installation, vpop3d has a new option. You can pass it one parameter which must be the path of the normal POP-3 daemon on your system (generally /usr/sbin/ipop3d). When vpop3d detect that the default domain of the machine is the target of the request, it will chain to the standard daemon. If you have installed vpop3d (in /etc/inetd.conf) without argument, then vpop3d will manage all request. Current installation are unaffected.

You can test this easily. For a machine named server.foo.com and a virtual domain with a virtual POP server server.virtual.com, try this.

telnet server.foo.com pop-3
telnet server.virtual.com pop-3

The greeting message of vpop3d is different from the message you will get from your standard POP daemon. This should confirm you that you have correctly installed vpop3d to achieve this.

DNS

More lexical tests have been added.