Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 60876 - ucspi's qmail.cdb qmail-scanner fix pls
Summary: ucspi's qmail.cdb qmail-scanner fix pls
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Server (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Qmail Team (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-19 03:51 UTC by Alexander Ivanchev
Modified: 2006-11-14 03:53 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Ivanchev 2004-08-19 03:51:20 UTC
oh, woa... thanks for the nightmarish experience ;-(

PLEASE, fix the default qmail tcp.qmail-smtp so that the EXPORT points out to the qmail-scanner's wrapper, instead of the .pl file directly. ->

# If you are using qmail-scanner, this line here is the correct one to use
# instead (comment out the above ':allow' line FIRST) and applies that script
# to any mail coming in that is not from a host allowed to relay. You can
# change the value of the variable to any other value you desire to use custom
# scripts for example.

:allow,QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue"
# 192.168.0.2:allow,RELAYCLIENT="",RBLSMTPD=""

Enabling the queue from here otherwise TOTALLY causes qmail-scanner to fail -- this was set properly in the qmail installation's common-conf, but apparently got looked over should one decide to enable it in the cdb... 3 hrs wasted.. whew :)

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2004-08-21 18:18:38 UTC
it's in the todo list for the new qmail -r16 (late August I hope).
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2006-08-20 05:46:23 UTC
Huh, what's the status here? 
Comment 3 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2006-11-14 03:53:05 UTC
this appears to have been fixed some time ago.