RE: [vchkpw] MySQL questions, vchkpw & tcpserver
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've had success, however, using a ludicrously high timestamp (99). j -- "Not all those who wander are lost." - JRR Tolkien
Re: [vchkpw] MySQL questions, vchkpw & tcpserver
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 just confirmed the format is as I said before. Add the IP address > like 192.168.0 with a NULL timestamp. > > Shane Thanks, both. I've implemented Shane's solution for the time being, as we're already set up for that, simply needing the correct syntax. However, we're going to be building a new mailcluster in the near future so I'll be looking at alternatives to our current approaches on different things. I'm happiest with the chance to centralize everything in SQL, however, wherever it's reasonable to do so. j -- "Not all those who wander are lost." - JRR Tolkien
RE: [vchkpw] MySQL questions, vchkpw & tcpserver
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 one place. PS: I just confirmed the format is as I said before. Add the IP address like 192.168.0 with a NULL timestamp. Shane >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 > >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.
Re: [vchkpw] MySQL questions, vchkpw & tcpserver
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 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 -- Jeremy Kitchen Systems Administrator [EMAIL PROTECTED] Kitchen @ #qmail on EFNet - Join the party! . Inter7 Internet Technologies, Inc. www.inter7.com 866.528.3530 toll free 847.492.0470 int'l 847.492.0632 fax GNUPG key ID: 93BDD6CE
RE: [vchkpw] MySQL questions, vchkpw & tcpserver
Im not certain, but I think you can add the IP like 192.168.0 with a NULL timestamp with version 2 of the tcpserver patch. Shane >-Original Message- >From: Joel Newkirk [mailto:[EMAIL PROTECTED] >Sent: Tuesday, 30 March 2004 11:41 PM >To: [EMAIL PROTECTED] >Subject: [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've applied >the tcpserver patch to also use vpopmail:relay to store info on >'always-allowed' relaying from our own IPs. > >My questions: > >1 - Previously, with .cdb arrangement, we used the form "192.168.0." to >permit relaying from any machine in that /24 network. How do I specify >the same using vpopmail:relay?? When I've tried using the >same form, it >appears not to work. Do I need to insert each IP >individually? (that'd >be ugly, with a /21 public network and roughly the same size >in combined >private networks, but if that's the way then that's the way...) > >2 - Allowing 'permanent' relaying - Do I just use a ridiculously high >timestamp? > >3 - How did I end up with entries like this in vpopmail:relay??? > >| 216.26.255.33 | 1080657350 | >| 216.26.255.65.41.4 | 108036425024 | > >I've got (currently) two qmail/vpopmail nodes in the cluster running on >the MySQL backend, and a third still on cdb (until we're assured of the >stability of the new setup). Because of this split, I've written a >small perl program that periodically synchronizes the two - it reads in >open-smtp, reads in all entries from the relay table, removes the >earlier of any duplicates, then inserts/updates entries in the db and >writes a new open-smtp. > >j > >-- >"Not all those who wander are lost." - JRR Tolkien > >
