> On Wed, 2003-12-03 at 13:25, [EMAIL PROTECTED] wrote:
>> To make a long story short, I followed the instructions for installing
>> qmail-scanner, word-for-word, as described in 'The Qmail Handbook'. I've
>> overcome problems with permissions in the /var/spool/qmailscan files,
>> problems with running qmail-scanner-queue.pl, and compiled and installed
>> the included wrapper to work around the problem.
>>
>
> You say you followed the instructions word-for-word, but then
> immediately say you had permission problems?
>
> I cannot understand that. You aren't the only one who has had such
> problems, but I have yet to see any bug in the ./configure script which
> would cause such a thing.
>
> Typically we hear later that vpopmail was installed - and that was
> causing the problem (see FAQ).

Yes, I am using vpopmail, but as I mentioned before, I had it working for
a while previously on the same system. The workaround mentioned in the FAQ
is what's used in the Qmail Handbook, and it's what I'm doing right now.

> How about some more details - such as what OS you are running, versions
> and whether or not you have a working suidperl installed/etc.

I'm using FreeBSD version 4.9-STABLE, with qmail 1.03, vpopmail 5.2.1,
qmail-scanner 1.16, perl 5.6.1, but suidperl doesn't work, and I had to
use the suid wrapper written in C that came with qmail-scanner.

Also, in response to Stephen, I managed to extract these logs:

Dec  2 17:27:13 pop smtpd: 1070414833.088271 tcpserver: status: 2/80
Dec  2 17:27:13 pop smtpd: 1070414833.088692 tcpserver: pid 54087 from
216.109.87.86
Dec  2 17:27:13 pop smtpd: 1070414833.115381 tcpserver: ok 54087
pop.lightspeed.ca:206.12.82.99:25 86.exgon.com:216.109.87.86::47653
Dec  2 17:27:13 pop qmail-send: 1070414833.165975 delivery 4657: deferral:
Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
Dec  2 17:27:13 pop qmail-send: 1070414833.166331 status: local 0/10
remote 119/120
Dec  2 17:27:13 pop qmail-send: 1070414833.189446 starting delivery 4658:
msg 4582304 to remote [EMAIL PROTECTED]
Dec  2 17:27:13 pop qmail-send: 1070414833.189790 status: local 0/10
remote 120/120
Dec  2 17:27:13 pop pop3d: 1070414833.291210 tcpserver: status: 3/30
Dec  2 17:27:13 pop pop3d: 1070414833.291617 tcpserver: pid 54089 from
209.53.208.34
Dec  2 17:27:13 pop pop3d: 1070414833.292167 tcpserver: ok 54089
0:206.12.82.99:110 :209.53.208.34::3866
Dec  2 17:27:13 pop X-Qmail-Scanner-1.16:
[pop.lightspeed.ca107041483342654090] pop.lightspeed.ca107041483342654090
exits - try again later...
Dec  2 17:27:13 pop smtpd: 1070414833.460937
X-Qmail-Scanner-1.16:[pop.lightspeed.ca107041483342654090]
pop.lightspeed.ca107041483342654090 exits - try again later...
Dec  2 17:27:13 pop smtpd: 1070414833.461632 rm:
/var/spool/qmailscan/working/new/pop.lightspeed.ca107041483342654090:
Permission denied
Dec  2 17:27:13 pop pop3d: 1070414833.490455 tcpserver: end 54089 status 256
Dec  2 17:27:13 pop pop3d: 1070414833.490693 tcpserver: status: 2/30
Dec  2 17:27:13 pop smtpd: 1070414833.528515 tcpserver: end 54087 status 0
Dec  2 17:27:13 pop smtpd: 1070414833.528687 tcpserver: status: 1/80

The most interesting lines from the above are:

Dec  2 17:27:13 pop X-Qmail-Scanner-1.16:
[pop.lightspeed.ca107041483342654090] pop.lightspeed.ca107041483342654090
exits - try again later...
Dec  2 17:27:13 pop smtpd: 1070414833.460937
X-Qmail-Scanner-1.16:[pop.lightspeed.ca107041483342654090]
pop.lightspeed.ca107041483342654090 exits - try again later...
Dec  2 17:27:13 pop smtpd: 1070414833.461632 rm:
/var/spool/qmailscan/working/new/pop.lightspeed.ca107041483342654090:
Permission denied



-------------------------------------------------------
This SF.net email is sponsored by OSDN's Audience Survey.
Help shape OSDN's sites and tell us what you think. Take this
five minute survey and you could win a $250 Gift Certificate.
http://www.wrgsurveys.com/2003/osdntech03.php?site=8
_______________________________________________
Qmail-scanner-general mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general

Reply via email to