Chad, I appreciate the insight. I do realize it's a difficult problem but, I think that there's a solution (albeit possibly from someone smarter than I).
I do have variables that are known (the sender email address and the recipient email address). The problem is tying them to the IP Address of the MTA when it's seen @ spamd. It may be that there isn't a solution without direct modification of spamd. If that's the case, then I hope the developer(s) will consider this suggestion. I definitely won't be disabling spamd ;). I would have a minor revolution on my hands if my users suddenly had spam again...heh. OpenBSD greylisting has been very effective for us thus far. --James On 10/26/05, Chad M Stewart <[EMAIL PROTECTED]> wrote: > James, > > The more I think about this one, the more I think there is no > solution to your issue. Well okay there are two choices, either use > spamd or not. :) > > You would have to have ESP to know from which IP address a particular > sender would be sending. If I'm sitting in a hotel and using their > WiFi then it is very probable that my message will be coming from > their SMTP server, not that which I use normally. Given only my mail > address you have no way of determining for sure, which server I use > to send mail. The server I submit a message to does not have to be > the server that eventually connects to the recipients server in DNS. > > You can't provide an email address to spamd as the redirection > happens before spamd, rather with PF. The default is to send the > packets to spamd. Once the connection gets rdr to spamd, I'm not > aware of anyway to say, redirect again to your real MTA. That brings > us back to knowing the connecting servers IP address. > > You could disable spamd protection and see how long it takes for your > users to complain about the amount of spam they are getting. :) > > > -Chad > > > On Oct 25, 2005, at 9:57 PM, James Harless wrote: > > > I appreciate the suggestions, but, not quite what I'm looking for yet. > > Either of these would allow me to whitelist someone AFTER they had > > been > > greylisting. What I'm looking for is a way to whitelist them based > > on user > > input.. before their initial email has been sent. In this somewhat > > typical > > scenario, the user has contacted me and said "I don't want mail from > > [EMAIL PROTECTED] to be delayed... whitelist them, please." > > > > --James > > > -- What would Bilano do?
