On Tue, 2004-03-30 at 13:20, Shane Chrisp wrote:
> PS: I just confirmed the format is as I said before. Add the IP address
> like 192.168.0 with a NULL timestamp.
>
> Shane
Well, I've tried this, but it always disappears from the DB eventually,
I presume (unchecked) when clearopensmtp runs. I'v
On Tue, 2004-03-30 at 12:59, Jeremy Kitchen wrote:
> this is better: http://untroubled.org/relay-ctrl
> put /var/spool/relay-ctrl on an nfs share. Easy as pie.
> then you can just use normal tcprules stuff if you want to do static relay
> controls, etc.
>
> -Jeremy
And Shane Chrisp wrote:
> I
The mysql server patch for tcpserver works very well and its simple
to use. That's aside from the fact that almost every qmail install
out there is using tcpserver anyway. Makes sense to keep it simple.
But each to their own, I personally would rather keep all the IP's that
are allowed to relay in
On Tuesday 30 March 2004 03:40 pm, Joel Newkirk wrote:
> I'm set up to use vpopmail:relay table to track pops, and I've applied
> the tcpserver patch to also use vpopmail:relay to store info on
> 'always-allowed' relaying from our own IPs.
ugh.
this is better: http://untroubled.org/relay-ctrl
p
[vchkpw] MySQL questions, vchkpw & tcpserver
>
>I've got a couple of issues.
>
>I'm in the process of migrating a cluster of qmail servers to MySQL
>backend for authentication, and have a question:
>
>I'm set up to use vpopmail:relay table to track pops, and I
I've got a couple of issues.
I'm in the process of migrating a cluster of qmail servers to MySQL
backend for authentication, and have a question:
I'm set up to use vpopmail:relay table to track pops, and I've applied
the tcpserver patch to also use vpopmail:relay to store info on
'always-allowed'
