FWIW, I think that being able to use spamdyke with other mail servers (I have my eye on postfix) would be a big boon. Solving the IPV6 problem at the same time would be a bonus. -- -Eric 'shubes'
On 05/12/2011 02:48 PM, Sam Clippinger wrote: > It's true spamdyke doesn't handle IPv6, but it's equally likely the > first problem is in tcpserver or xinetd. Because spamdyke is started by > another process (tcpserver or xinetd, depending on your setup) after the > incoming connection has been accepted, spamdyke can't discover the > remote IP address on its own. Instead, it relies on that other process > to set the environment variable TCPREMOTEIP to a dotted-quad IPv4 > address, which it reads on startup. If that variable isn't set or isn't > a dotted-quad, spamdyke assumes an IP address of 0.0.0.0 and moves on. > In the short term, I'll consider making spamdyke skip rDNS-related tests > if the IP address is 0.0.0.0. That way, IPv6 addresses simply won't be > checked (by those filters) but they'll still work for IPv4. > > I've been considering this problem for a little while now, specifically > thinking about the number of installed (ancient) qmail servers whose > administrators are scared to upgrade (I'm in that group). After all, if > a running server has an IPv4 address, there's little incentive to > (potentially) break the entire thing by trying to patch/recompile part > of qmail to handle IPv6 addresses. Some external force is needed to > overcome that resistance (e.g. a paying client can't receive email from > a customer whose mail server uses IPv6). I think the only way to really > solve the problem is to handle IPv6 AND implement one of the > longest-standing items on my TODO list -- make spamdyke run as a daemon > and accept incoming connections itself. That would allow a nervous > sysadmin to replace tcpserver entirely and retain the option of > switching it back if anything goes wrong. It would also allow spamdyke > to forward incoming connections to another host/port so it would work > for more than just qmail servers (e.g. sendmail, postfix, Exchange). > > I'll see what I can do after I get this next version out. I still need > to learn more about supporting IPv6 myself... > > -- Sam Clippinger > > On 5/12/11 8:49 AM, Daniel Anliker wrote: >> hi list, >> >> as i see spamdyke and ipv6 is not working. >> >> first problem is this one: >> >> May 12 15:45:31 john spamdyke[19276]: DENIED_RDNS_MISSING from: >> dan...@danliker.ch to: info-T21eQE/xtcismel7j9a...@public.gmane.org >> origin_ip: 0.0.0.0 origin_rdns: >> (unknown) auth: (unknown) encryption: TLS >> >> it gives a ip 0.0.0.0 if the sender is a ipv6 address.... >> >> best regards >> daniel >> _______________________________________________ >> spamdyke-users mailing list >> spamdyke-users@spamdyke.org >> http://www.spamdyke.org/mailman/listinfo/spamdyke-users >> _______________________________________________ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
