This feature can be controlled from the command line when creating a new virtual email domain with the --quota option. See the linuxconf --help to see the syntax. I still have to complete the help about this topic.
The new strategy is slightly changed: If sendmail.cf was generated by Linuxconf, then the previous strategy apply. If it was not (or was modified, even just a byte), then Linuxconf won't take about it. The only way to get a new sendmail.cf from Linuxconf will be interactive when changing configuration in mailconf itself.
The pophash system solves a real problem for mail server with "moving" users. If you enable relay control, then only users originating from specific networks may use the SMTP server. With this strategy, any user who have successfully connect with the vpop3d server will be allowed in. The popauther.pl script maintain in real time the /etc/mail/pophash database and sendmail uses this db to grant relay or not (plus all the other databases it already uses).
vpop3d has been modified so it provides suitable information through the syslog facility.
linuxconf --modulemain mailconf --addvuser domain user name linuxconf --modulemain mailconf --delvuser domain user
linuxconf --modulemain mailconf --vpasswd account
The new password is passed on standard input, so it can't be sniffed by looking at a PS output.
Linuxconf was not supporting this properly in the user account dialog.
This defines (or redefines) an alias. You provide as many values as needed.
Same thing for virtual email domain
Delete an alias definition
Same thing for virtual domain
Remove some values from one alias definition
Same thing for virtual domains
Delete some values from all aliases. This is useful when you delete an account and wish to remove it from all aliases.
Same thing for virtual domains.
linuxconf --modulemain mailconf --generatecf
THis may be used when you add or remove a virtual email domain using the command line for example.
they can change their password. The older htmlmod:userpass URL is still operational.
The RBL is a way to reduce SPAM.
The help screen has been fixed.
These check-box allows one to lock partly or completely a virtual domain email service. This can be used when migrating a vdomain from one server to another, without stopping the mail service for other domain.
vdeliver and vpop3d were fixed to support this. vimap will have to learn about this little trickery. Quite easy to adapt.
I have reworked the presentation of the mailconf basic configuration dialog and also the help screen, which was dating to say the least.
I put a check-box for each. I also reworked the dialog to place options together under a new tab called "SMTP features".
Now, the per user quota is used if available. If not, the domain limit is used.
By deleting the temporary file immediately, even if vdeliver exits abnormally, the file is gone.
The auto-responder feature allows dummy email address to be connected to some content, sent whenever a message is received for this address. For example, for a vdomain called vdomain.com one can create a file called /var/spool/vmail/files/vdomain.com/prices.auto and this file will be sent whenever someone send a message to firstname.lastname@example.org. This pseudo user prices does not have to be created in the account database. The file just have to exist. Note that this file has precedence over accounts and aliases.
The vacation is handle using roughly the same logic. For user joe member of the domain vdomain.com, if you create a file /var/spool/vmail/files/vdomain.com/joe.vacation it will be sent to the sender whenever a mail is received. Bulk messages and mail-daemon related are omitted.
Also, a file called /var/spool/vmail/files/vdomain.com/joe.froms is maintained. It is used to record the fact that an email was sent to a sender once, so we won't send the vacation message over and over to the same person.
Please test this and submit comments. Once settle, we will had the administration tool allowing users to change their vacation message themselves.
# Get the available variable /sbin/vregistry --list | grep vdomain # Retrieve the fallback destination /sbin/vregistry --get vdomain.fallback.foo.com # Set the domain wide inbox disk quota /sbin/vregistry --set vdomain.quota.foo.com 10000
/sbin/vregistry --set user.gecos.foo.com.joe "his name"
The parsing of the header was case sensitive (which was wrong) and it was failing to locate the return address of a message properly.
From now on, when a user, or administrator set a password, it will be crypt-ed using MD5 (the same format found in /etc/shadow). Older crypt-ed password will still work.
vimap was not tested. Please check it all. Since vpop3d did not need any change, things should be fine ... :-)
This change provides better password crypt. The previous format was only using the first 8 characters of the password. Also you can move accounts from the main domain to vdomain without reentering the passwords.
Sponsored by Eric Wood.
The aliases may be modified for virtual email domains from the web interface. Enter web mode and visit the "special entries" link to find out.
This is a nice way to delegate vdomain administration to the vdomain user/owner/customer without having to create a real user account.
Sponsored by Eric Wood!
| some command
The command may be defined using the following tokens:
A sample command has been created: /usr/lib/linuxconf/lib/sendsmtp. It performs SMTP message delivery without any domain/MX resolution.
This token replacement is also done in aliases pointing to a command (filter program).
The mailconf module does not handle this file, but if it exists, it generates a sendmail.cf using it.
The module was doing some sanity check and had a flaw. For example, it was checking if you were simply attempting to redirect the user emails to ... the user, which was pointless. Pointless unless you redirect it somewhere else. It is valid to redirect email for user Joe another place (email@example.com) and still deliver it in the local mailbox. This is done by entering "joe firstname.lastname@example.org)
In some case, the module was confused and was rejecting your entry claiming that you were simply redirecting email to itself.
When creating a new account with a vacation text, the file was created with the wrong name.
There were also some spelling errors.
The module auto-magically move old configuration (stored in /etc/conf.linuxconf) to /etc/mail/trusted_users when you change the configuration. There is no migration tool needed.
Also, the control files used by procmail were moved from /etc to /etc/vmail.
Check this out!
With this milter enabled (and sendmail.cf configured to use it), sendmail checks with the milter to learn if the user exist (or an alias). If not, the mail is rejected immediately.
If the vdomain has a fallback destination configured, the milter let the mail go.
An init script called vdomaincheck is delivered to start/stop the milter.
gives access to a form requesting the email address (not just the user id). From the email address, the form operates on the proper vdomain.
Now it checks if procmail succeeded. It will only perform the vacation task if procmail succeeded.
We added a little feature with that. If procmail produce the exit code 1, the vacation message won't be performed, but vdeliver will return success to sendmail. This allows you to silently drop message. Thanks to Eric Wood for the suggestion and testing.
Not really a mailconf bug, but it was affected by the UI toolkit bug.
#date: start_date end_date
The dates are encoded using international convention yyyy/mm/dd.
The old behavior is preserved (A db file without #date: means the vacation processing must be done).