I have added to this feature-request my chkuser version 2.08b patch. Rediffed for the actual qmail-1.03-r16.ebuild that is marked as stable. to install: 1) download the tar file and extract it to a seperate folder 2) edit the chkuser_settings.h for your needs. (the file is modified by me to activate the mx lookup and the mail adress format checker. Also I have activated the environment var's CHKUSER_START and SENDER_NOCHECK) 3) run ./install.sh 4) install qmail with emerge -pv qmail as usual 5) add at your tcp.smtp CHKUSER_START="ALWAYS" after :allow to activate chkuser for all domains. 6) do an echo "0" > /var/control/mfcheck because the sender is checked now by chkuser. So a double check isn't usefull. (or not recommanded) I would prefer it when any qmail-ebuild developer add my patches to the -r17 release and add a use-flag "vpopmail" or "chkuser" to activate the patch. Because at first vpopmail must be installed. I like chkuser since version 2 very much. Better than any of the qmail-spp programs. Greetings from Germany Jan Lange Reproducible: Always Steps to Reproduce:
Created attachment 73520 [details] chkuser patch for the qmail-1.03-r16.ebuild here the patch as tar file
Please, attach a plaintext patch.
Created attachment 73521 [details, diff] qmail-1.03-r16_chkuser-2.0.8b.patch
Created attachment 73522 [details, diff] qmail-1.03-r16_chkuser-2.0.8b_ebuild.patch patch for the qmail-1.03-r16.ebuild
Created attachment 73523 [details] chkuser_settings.h
Created attachment 73524 [details] install.sh a small installer, to make it easier to install the patch for beginner-testers
.
Thanks for providing the patch. Blocking to the -r17 bug, so we don't forget it.
I applied this patch and it is giving me problems. The first problem I noticed is I have a POP account that simply forwards email sent to it to another POP account (was a full account and will be again but user is on system that does not have access to external pop servers right now). This CHKUSER patch immediately causes the smtp server to reject these with an error saying this account does not exist. However, now what has me really stumped is I then noticed a couple of aliases that do not work, but others do which are configured the exact same way. For example, I set up aliases when I register at a site and these all forward to a POP account. Some will work and others won't even though they all exist and point to the same POP account. I've set it to not activate until I get this sorted out. Any thoughts on how to debug this would be great. Thanks.
Hi, I was going to submit my own patch to qmail for chkuser support but I found this item a few days ago... My patched qmail is working fine for me and I too use aliases, forwards, and just about every other feature that qmail/vpopmail offer... :) I briefly looked at the original patch submission and I didn't see anything substantially different than my patch. I'll upload the patches I'm using and you can try this alternate version to see if you get the same results, etc. -- jthomps
Created attachment 76133 [details, diff] alternative chkuser patch
Created attachment 76134 [details, diff] alternative ebuild patch
Created attachment 89915 [details] qmail+chkuser-2.0
Created attachment 89916 [details, diff] path for qmail-chkuser
We won't add custom patches to mail-mta/netqmail. Please use QMAIL_PATCH_DIR.
