What you're asking for is auto-whitelisting; this doesn't really have anything to do with the graylist filter.
This would be a cool feature -- if a local user sends a message, automatically whitelist the sender/recipient pair to allow any responses to be delivered. Perhaps this feature would only activate if the local user authenticated while sending the initial message. The auto-whitelist entries could expire after a short time, so the list wouldn't get out of control. In version 4.0.0, you'll be able to do this manually -- spamdyke's configuration will be customizable for each sender, recipient, remote IP and remote rDNS name (or any combination of those). If you wanted to put the time into it, you could probably create a script that would analyze your log file and create/remove the auto-whitelist entries without any additional spamdyke code. Good suggestion -- I'll put some thought into this. -- Sam Clippinger Roman V. Isaev wrote: > Feature request. Excuse me if I missed something and it's possible > to do with current tool, but I did not find anything yet. > > Recently I installed spamdyke and some of my users began to complain > about > missing emails. In 90% cases this happens when they receive no repy because > their peer's mail server has no reverse dns. There is a problem: I have no > time and nerves to press owners of these servers to set up correct reverse dns > (it's much like fighting with windmills anyway) and my users have no leverage > on these who send mail either because they can't explain their needs to their > sysadmins (who don't care anyways). Now if the spamdyke could auto ungraylist > adress pairs when internal mail goes through the system that would solve 95% > of the problem. > > I.e. something like that: my server is foo.com and we have a bar.com > without > rdns. Right now if the [EMAIL PROTECTED] sends a message to [EMAIL PROTECTED] > and he replies > [EMAIL PROTECTED] gets no response. But if we add [EMAIL PROTECTED] to > foo.com directory > when we see the mail going from inside to outside it would solve most of the > problem. > > Or at least if I could whitelist address PAIRS I'd write web interface > for > my users to add important addressess (it's very unlikely for spammers to guess > what's important for certain users anyway)... > > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
