I upgraded to 0.40 over the weekend. Everything seemed to work fine but I think I missed some key issues. On Monday qpsmtpd would not relay for our offsite users. They could send to addresses in our domain but not anything outside our domain. I had to roll back to the old version which is broken in other ways but at least works enough.
The logs showed that the mail was fine all the way up to rcpt_to. rcpt_to would return DENY if the mail was going to an outside domain. It looks as though rcpt_to was doing it's job because normally we don't want to relay for just anybody but we are trying to use the whitelist_soft plugin to allow relaying for those offsite users. Let me say here that I am working toward authenticated relaying but we are not there yet so I need the whitelist_soft to work if possible. We are using whitelist with our older qpsmtpd that is mostly working but has issues. whitelist is not a link on the wiki so I am trying whitelist_soft instead. I just turned on the same configuration on port 587 and 465 only for testing (see I'm working on using standards). Thank you for bearing with me to this point. I realize this is a long email. I am guessing that rcpt_to is not aware of the whitelist_soft mechanisms. The whitelist_soft calls are returning OK in the logs but rcpt_to is denying when it gets to that point. Does anyone know if this is true (rcpt_to is not whitelist_soft aware)? Do I need to modify rcpt_to? Am I looking in the wrong place? Am I misunderstanding what whitelist does? I haven't found anything when googling for these key terms and searching the archives. The pod for whitelist_soft doesn't say anything about how it does the whitelisting or having to deal with other modules such as rcpt_to. Thank you -- JT Moree
