Mar 10

I have qmailtoaster installation so my users are in:

/home/vpopmail/domains/DOMAIN.XXX/USER

you need two create two file:

first called “mailfilter” can be put wherever you want (this file will be in .qmail file), me  I choose:

/home/vpopmail/domains/

so now I have:

/home/vpopmail/domains/mailfilter

second called “.qmail” must be pun in user folder in the same dir with Maildir folder, like this:

/home/vpopmail/domains/MYDOMAIN.XXX/USER/.qmail

File contents are:

.qmail

|preline /usr/bin/maildrop /home/vpopmail/domains/mailfilter

mailfilter

SHELL=”/bin/bash”
import EXT
import HOST
logfile “/var/log/maildrop/mailfilter.log”
USERHOME=`/home/vpopmail/bin/vuserinfo -d $EXT@$HOST`
if (/^Subject:.*\[SPAM\]/:h)
{
log “WE got a SPAM, moving mail to spam directory $USERHOME/Maildir/.Junk”
DUMMY=`test -d $USERHOME/Maildir/.Junk`
#if .Junk folder exists
if ( $RETURNCODE == 0 )
{
to “$USERHOME/Maildir/.Junk”
}
else
{
log “No Junk directory in $USERHOME/Maildir”
to “$USERHOME/Maildir/”
}
}
else
{
to “$USERHOME/Maildir/”
}

This works for users in witch dirs you put .qmail file. If you want for whole domain you must use :

/home/vpopmail/domains/MYDOMAIN.XXX/.qmail-default file instead of .qmail in user directory.

written by MG \\ tags: , , ,

Jan 30

First locate simcontrol file at /var/qmail/control

The default file looked like this:

:clam=yes,spam=yes,spam_hits=10,attach=.mp3:.src:.bat:.pif:.exe

If you want to just stop spam processing for a single user you have to put:

user@domain.com:clam=yes,spam=no,spam_hits=10

in front of existing line, result:

user@domain.com:clam=yes,spam=no,spam_hits=10
:clam=yes,spam=yes,spam_hits=10,attach=.mp3:.src:.bat:.pif:.exe

for an entire domain just put:

domain.com:clam=yes,spam=no,spam_hits=10

Save an run #qmailctl cdb

 

written by MG \\ tags: , , , ,

Jan 27

qmail + SPAMD +FC12 error:

 error: Can’t locate Crypt/OpenSSL/Bignum.pm in @INC (@INC contains: /usr/lib/perl5/vendor_perl/5.10.0/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.10.0 /usr/
local/lib/perl5/site_perl/5.10.0/i386-linux-thread-multi /usr/local/lib/perl5/site_perl/5.10.0 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.10.0/i386-linux-thread-multi /usr/lib/perl5/5.10.0 /usr/lib/perl5/si
te_perl) at /usr/local/lib/perl5/site_perl/5.10.0/i386-linux-thread-multi/Crypt/OpenSSL/RSA.pm line 17.

solution: run cpan and install Crypt::OpenSSL::Bignum module.

> cpan

>install Crypt::OpenSSL::Bignum

written by MG \\ tags: , , ,

Jan 26

if you want to modify qmailadmin to check if new password is strong you can do like this:

edit qmailadmin.c and:

add:   #include <ctype.h>

I wrote a function to check if new password contains at least 1 alphachar and 1 digit.

add it before int main(argc,argv)


int check_strong(char *pass_string)
{
    int digit=0;
    int alpha=0;
    int length=strlen(pass_string);
    int i;
    for(i=0;i<length;i++){
       if( digit == 1 && alpha == 1 ) return 1;
       else{
                  if(isdigit(pass_string[i])) digit=1;
                  if(isalpha(pass_string[i])) alpha=1;
       }
    }
    return 0;
}
Continue reading »

written by MG \\ tags: , , , ,

Jan 18

problem:

./load ezmlm-gate subdb.a getconf.o slurpclose.o slurp.o \
getopt.a getln.a auto_bin.o env.a sig.a fs.a \
strerr.a substdio.a stralloc.a alloc.a error.a str.a case.a wait.a \
open.a lock.a seek.a -L/usr/lib64/mysql -lmysqlclient -lnsl -lm -lz
/usr/bin/ld: cannot find -lmysqlclient
collect2: ld returned 1 exit status
make: *** [ezmlm-gate] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.578TXA (%build)

check if you have:

 /usr/lib64/mysql

if not, make a link :

 ln -s /usr/lib/mysql/ /usr/lib64/

 in /usr/lib/mysql/  you must have something like this:

 libmysqlclient.a
 libmysqlclient_r.a
 libmysqlclient_r.so -> libmysqlclient_r.so.16.0.0
 libmysqlclient_r.so.16 -> libmysqlclient_r.so.16.0.0
 libmysqlclient_r.so.16.0.0
 libmysqlclient.so -> libmysqlclient.so.16.0.0
 libmysqlclient.so.16 -> libmysqlclient.so.16.0.0
 libmysqlclient.so.16.0.0

written by MG \\ tags: , , ,

Jun 03

1. First stop qmail: “qmailctl stop”

2. Go to /var/qmail/supervise/ and  copy entire smtp directory to smtp-ssl .

Edit /var/qmail/supervise/smtp-ssl/run by adding :

SMTPS=1
export SMTPS

after line: VCHKPW=”/home/vpopmail/bin/vchkpw”  and change port from smtp to 465 .

Now file should look like this:

#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD=”/var/qmail/bin/qmail-smtpd”
TCP_CDB=”/etc/tcprules.d/tcp.smtp.cdb”
HOSTNAME=`hostname`
VCHKPW=”/home/vpopmail/bin/vchkpw”
SMTPS=1
export SMTPS

exec /usr/bin/softlimit -m 12000000 \
    /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c “$MAXSMTPD” \
    -u “$QMAILDUID” -g “$NOFILESGID” 0 465 \
    $SMTPD $VCHKPW /bin/true 2>&1

3. Edit /var/qmail/supervise/smtp-ssl/log/run :

change /var/log/qmail/smtp  to /var/log/qmail/smtp-ssl

Continue reading »

written by MG \\ tags: , , ,

Apr 17

Qmail logs quite a lot of information about what it’s doing, although it can be daunting to collect it all together. If you’re using daemontools, each daemon has its own set of logs, kept in a rotating set of log files maintained by multilog, usually with a TAI64N timestamp.

The qmail-send process logs each message queued and each delivery attempt. The qmail-smtpd process logs each incoming SMTP connection, although it won’t describe what happened during the connection. tcpserver logs every connection denied due to entries in the connection rules file, and rblsmtpd logs every connection it blocked due to a DNSBL entry. If you use QMAILQUEUE to run other programs at SMTP time, anything they send to stderr is logged, and if you’ve added other patches to qmail-smtpd, anything they write to stderr is logged, too.

A system can be set up to do logs analysis on the fly, every time multilog switches to a new log file or once a day in a batch. It often makes sense to combine the two, doing some work at switching time and the rest daily. Although it’s usually more convenient to keep the logs for each application separate, it’s not hard to create combined logs for analysis or just to keep around in case someone needs to look at them later. If a set of logs from different programs all have TAI64N timestamps, merge them using the standard sort program sort -m. TAI64N timestamps are fixed-length hex strings, so merging them in alphanumeric order is the same as date order. Once they’re merged, tai64local can make the timestamps readable by people. So to merge a set of log files, all of which have the standard multilog TAI64N names that start with an at-sign:

sort -m \@* | tai64nlocal > merged-log

Run command above in one of your log directories.

See http://cr.yp.to/libtai/tai64.html for more detail.

written by MG \\ tags: ,