On Mon, 10 Jun 2002, Greg Ward wrote:
> OK, CVS checkout works fine now. Thanks.
>
> For testing, I've got qpsmtpd running from the command-line, listening
> to port 2525. I'm using the default config, with a few blacklists added
> to dnsbl_zones. But I'm not convinced that it's working; for o
OK, CVS checkout works fine now. Thanks.
For testing, I've got qpsmtpd running from the command-line, listening
to port 2525. I'm using the default config, with a few blacklists added
to dnsbl_zones. But I'm not convinced that it's working; for one thing,
qpsmtpd seems to accept wildly bogus d
Hi Ask,
The rearchitecting and plugin plans sound really cool.
FWIW, my goal is to be able to write a plugin that takes a simple text-file table of
search strings and reject messages for each one; then run all the matches against the
message (headers and body), and bounce as needed (kinda like
On Mon, 10 Jun 2002, Greg Ward wrote:
> Has the filesystem on cvs.perl.org changed recently? Or is this a
> temporary thing?
oops, we changed it in November but I forgot to upgrade the
instructions. The cvs server was upgraded and we killed the old
symlink.
try,
cvs -d :pserver:[EMAIL PROT
Same problem here.
Was able to checkout just a couple days ago. So the change is recent anyway.
-c
At 4:09 PM -0400 6/10/02, Greg Ward wrote:
>The CVS checkout instructions on the qpsmtpd page aren't working:
>
>$ cvs -d :pserver:[EMAIL PROTECTED]:/home/perlcvs login
>Logging in to :pserver:
The CVS checkout instructions on the qpsmtpd page aren't working:
$ cvs -d :pserver:[EMAIL PROTECTED]:/home/perlcvs login
Logging in to :pserver:[EMAIL PROTECTED]:2401/home/perlcvs
CVS password:
/home/perlcvs: no such repository
Has the filesystem on cvs.perl.org changed recently? Or is this a
