The pod for the smtp-forward plugin says:
| CONFIG
|It takes one required parameter, the IP address or hostname to
|forward to.
|
| queue/smtp-forward 10.2.2.2
|
Unfortunately, that doesn't work because . isn't allowed in the
hostname parameter.
Also, code for
This patch makes the headers more like those added by spamc. It also
fixes a real bug, but I forgot what that was :-)
hp
--
_ | Peter J. Holzer| Humor ohne Emoticons ist trockener Humor.
|_|_) | Sysadmin WSR |
| | | [EMAIL PROTECTED] | -- Toni Grass in aip
This patch allows running from xinetd and inetd.
Inetd is distributed with almost all Unix versions. Xinetd with most
current Linux distributions. Both lack some features that tcpserver has
(inetd more than xinetd), but for those which want to run qpsmtpd
without qmail (I now have it running with
On Monday, Sep 8, 2003, at 03:08 America/Los_Angeles, Peter J. Holzer
wrote:
This patch allows running from xinetd and inetd.
Very cool.
Is /usr/local/bin/ts a standard program? Maybe we should have the
log() thing support using syslog instead of stdout with some option.
Could you add some
On 2003-09-08 03:29:00 -0700, Ask Bjørn Hansen wrote:
On Monday, Sep 8, 2003, at 03:08 America/Los_Angeles, Peter J. Holzer
wrote:
This patch allows running from xinetd and inetd.
Very cool.
Is /usr/local/bin/ts a standard program?
Ups, sorry, that slipped in. No, its a simple program
Hi,
Does anyone have any ideas on how to reduce the amount of disk IO
Qpsmtpd and qmail do? Current, my server hits the hard drive four
times for each incoming local message:
1. Qpsmtpd in spool directory
2. qmail queue's directories
3. Amavis to do a virus scan
4. qmail-local writing to
At least in the case of qsmptd running under SpeedyCGI, each instance of qpsmtpd
gobbles
progressively more memory for each message it processes until it finally hits the
softlimit setting.
Does that also happen running under Pperl?
Jim
James H. Thompson
[EMAIL PROTECTED]
- Original
On Monday, Sep 8, 2003, at 17:43 America/Los_Angeles, James H. Thompson
wrote:
At least in the case of qsmptd running under SpeedyCGI, each instance
of qpsmtpd gobbles
progressively more memory for each message it processes until it
finally hits the softlimit setting.
Does that also happen
