I am trying to configure QmailAdmin for my system to work with my
xf86-64 system and not having luck.. Here is the output:
ps2:/usr/src/qmail/qmailadmin-1.2.0 # ./configure
--enable-htmldir=/home/prostream/prostream.net
--enable-cgibindir=/home/prostream/cgi-bin/
--enable-autoresponder-bin
I am using vpopmail, courier imap, and qmail. I am a bit overwhealmed
on which SMTP auth patch to use. I want it so that when a user checks
their imap e-mail it enters their IP into a table for SMTP auth. Where
do i proceed to go to get this to work properly?
Thanks,
Brooks
I am installing vchkpw + SMTP AUTH + qmail. I have installed qmail with
this patch:
qmail-smtpd-auth-0.31 from
http://members.elysium.pl/brush/qmail-smtpd-auth/
Here is my run tcpserver script for qmail-smtpd:
exec /usr/local/bin/softlimit -m 1000 \
/usr/local/bin/tcpserver -v -H -R -
Ok, after the huge number of irrevlent replies to my last thread I am
attempting to post an update on my SMTP Auth problem. I have tried just
most smtp patchs, the on in the contrib dir of vpopmail and
http://shupp.org/patches/netqmail-1.05-tls-smtpauth-20040207.patch I
have included captur
On another side note, I was looking for some other assistance in setting
up spamassassin so that it can filter out e-mail and just not even show
up in my box. My spam as become out of control as I am sure many
systems are. I installed qmail-filter, but unsure how to configure it
so that it wi
Peter Palmreuther wrote:
Where
does the space character after '.com' comes from? Seems there's
something wrong with Base64-decoding / handing decoded values over to
vchkpw. I might be wrong, but all logs similar to this found in my
system logs have ':' instead of ' :'.
I'd say this is a case
Peter Palmreuther wrote:
Please replace your strace call by
strace -fF -s 4096 -o /tmp/qmail.log -e write ...
(replace '...' with 'softlimit -m ...' and so on).
else we'll not see what qmail hands over to vchkpw.
3906 write(2, "tcpserver: status: 0/20\n", 24) = 24
3906 write(2, "t
Peter Palmreuther wrote:
However your Base64-encoded your login data, something went wrong.
There's a '\n' that shouldn't be there.
The correct B64-data would be:
Username: YnJvb2tzQGJyb29rc3JveS5jb20=
Password: amo=
Please try again with these data and report in.
Peter,
After tyring with these