Actual configuration of MySQLfilter

The following articles mainly introduce the actual configuration of qmailadmin + vpopmail + MySQLfilter. If you are interested in the actual operations, you can click and view the following articles. I hope it will help you with the actual configuration of MySQLfilter. The method acting on qmail-local (that is, MDA. There are several questions to ask.

The following articles mainly introduce the actual configuration of qmailadmin + vpopmail + MySQL filter. If you are interested in the actual operations, you can click and view the following articles. I hope it will help you with the actual configuration of MySQL filter. The method acting on qmail-local (that is, MDA. There are several questions to ask.

The following articles mainly introduce the actual configuration of qmailadmin + vpopmail + MySQL filter. If you are interested in the actual operations, you can click and view the following articles. I hope it will help you with the actual configuration of MySQL filter.

The method acting on qmail-local (that is, MDA.

There are several problems to solve.

1. How to automatically initialize your initial MySQL filter file when creating a user.

2. How does the filter defined by webmail work.

3. There are also some problems encountered in the process of solving these problems.

For the first problem, I studied qmailadmin and found out after reading the code,

Qmailadmin supports plug-in configuration files,

Run the script defined in the plug-in configuration file. The script is for each domain, that is, placed under the directory of the domain.

No introduction on the Internet. It is estimated that it is inter7 unleased.

The Directory of the domain is located through/var/qmail/users/assign. For example, the content of assign is as follows:

 
 

  
  
+foo.com-:foo.com:515:511:/home/vpopmail/domains/foo.com:-:: 
 
 

A configuration file. qmailadmin-hooks is defined in/home/vpopmail/domains/foo.com. Note:

The configuration file format is as follows:

 
 

  
  
#.... 
  
  
op: cmd 
 
 

To the qmailadmin-1.06, op supports the following operations:

 
 

  
  
"adduser", 
  
  
"deluser", 
  
  
"moduser", 
  
  
"addmaillist", 
  
  
"delmaillist", 
  
  
"modmaillist", 
  
  
"listadduser", 
  
  
"listdeluser" 
 
 

For example, if you want to do something after adding a user, add MySQL filter as an example. qmailadmin-hooks

The configuration can be as follows:

Adduser:/home/vpopmail/bin/inituser. sh

The inituser. sh script is as follows:

 
 

  
  
#!/bin/bash 
  
  
Domain=$1 
  
  
User=$3 
  
  
Passwd=$2 
  
  
DomainPath=/home/vpopmail/domains/$Domain 
  
  
umask 0177 
  
  
exec 1> /tmp/adduser.log 
  
  
exec 2> /tmp/adduser.log 
  
  
echo $DomainPath 
  
  
cat>$DomainPath/.qmail-$User <|maildrop $DomainPath/$User/.mailfilter 
  
  
EOF 
  
  
cat>$DomainPath/$User/.mailfilter 
  
  
EOF 
  
  
cat>$DomainPath/$User/.userfilter <#MFMAILDROP=2 
  
  
# 
  
  
# DO NOT EDIT THIS FILE. This is an automatically generated filter. 
  
  
FROM='$User@$Domain' 
  
  
import SENDER 
  
  
if ($SENDER ne "") 
  
  
{ 
  
  
FROM=$SENDER 
  
  
} 
  
  
to "$DomainPath/$User/Maildir/." 
  
  
EOF 
  
  
cat>$DomainPath/$User/Maildir/maildirfilterconfig 
  
  
MAILDIR=$DomainPath/$User/Maildir 
  
  
EOF 
 
 

For the second problem, inituser. sh has provided a solution, that is, sqwebmail

Maildirfilterconfig is used to find the MySQL filter file. The definition is ../. userfilter, which is included in. mailfiter,

Point. mailfilter is the rule file called by maildrop.

There are several points to explain,

1. Comments in the first few lines of userfilter are valid. They are the sqwebmail mark and cannot be removed. Otherwise, sqwebmail reports an error.

2. Why does MAILDIRFILTER point to. mailfiter instead of. userfilter. You can add it to. mailfilter.

Other MySQL filters rule, which do not need to be edited by the user.

3. The script in qmailadmin-hook is executed by the sub-process qmailadmin fork. qmailadmin is run by an http user.

So there will be errors when creating these files. Therefore, we have changed the source code in the qmailadmin */user. c directory of the source code package.

Before the fork function of call_hooks, it is as follows:

 
 

  
  
+ setuid(0); 
  
  
+ setgid(VPOPMAILGID); 
  
  
+ setuid(VPOPMAILUID); 
  
  
pid = fork(); 
 
 
.

After compiling qmailadmin, replace the files in the cgi directory. Note that the owner is the root and setuid bits.

4. Why isn't su used for execution in inituser. sh, so you don't need to change the code? First, apache (the most popular WEB server platform on Unix) Redirects stdin, while su checks

Stdin is not tty. If not, it will not be executed. Second, the fork sub-process is exec to execute the commands specified in the MySQL filter configuration,

Exec does not copy euid and egid, so if you do not need su, you need to compile a suid program by yourself. This is troublesome.

. Qmailadmin-hooks is as follows:

 
 

  
  
adduser: /home/vpopmail/bin/inituser.sh 
  
  
deluser: /home/vpopmail/bin/deluser.sh 
 
 

/Var/vpopmail/bin/deluser. sh:

 
 

  
  
#!/bin/bash 
  
  
Domain=$1 
  
  
User=$3 
  
  
Passwd=$2 
  
  
DomainPath=/home/vpopmail/domains/$Domain 
  
  
rm -f $DomainPath/.qmail-$User 
 
 

Note: The original qmailadmin has a bug.

In this line of the qmailadmin */user. c function call_hooks in the source package

Error = execl (cmd, Newu, Domain, Password1, Gecos, NULL );

The problem is obvious here. The second parameter of execl is arg0, which does not actually work. While Gecos is the real user

User name, which is a value only when it is created. If it is left blank, It is Newu. Therefore, I thought the user name is $3.

However, when moduser and deluser are used, the Operation user name is not in Newu, but in ActionUser.

Therefore, the deluser and moduser scripts defined in the hook cannot obtain the user name.

So you need to change this line

 
 

  
  
if (Newu %26amp;%26amp; *Newu) { 
  
  
error = execl(cmd, cmd, Newu, Domain, Password1, Gecos, NULL); 
  
  
} else { 
  
  
error = execl(cmd, cmd, ActionUser, Domain, Password1, Gecos, NULL); 
  
  
} 
 
 

In addition, if you want to facilitate expansion, you can also put op in the execl parameter. In this way,

You can use a script. The operation is based on the op type. It's not like dividing it into many scripts like me.

Therefore, after user. c is finished, the following is near the fork of the call_hooks function:

 
 

  
  
setuid(0); 
  
  
setgid(VPOPMAILGID); 
  
  
setuid(VPOPMAILUID); 
  
  
pid = fork(); 
  
  
#ifdef DEBUG 
  
  
fprintf(actout,"Where the parameters are: %s, "%s", %s, %s, %s, %s, NULL); ", 
  
  
cmd, hooks[hook_type], Newu, Domain, Password1, Gecos); 
  
  
#endif 
  
  
if (pid == 0) { 
  
  
// error = execl(cmd, Newu, Domain, Password1, Gecos, NULL); 
  
  
if (Newu %26amp;%26amp; *Newu) { 
  
  
error = execl(cmd, cmd, Newu, Domain, Password1, Gecos, NULL); 
  
  
} else { 
  
  
error = execl(cmd, cmd, ActionUser, Domain, Password1, Gecos, NULL); 
  
  
} 
 
 

Inituser. sh and deluser also need to change the parameter location. I only paste the modified header lines as follows:

 
 

  
  
#!/bin/sh 
  
  
User=$1 
  
  
Domain=$2 
  
  
Passwd=$3 
  
  
RealName=$4 
  
  
 
 
 

The above content is an introduction to the configuration of qmailadmin + vpopmail + MySQL filter. I hope you will find some gains.