> > Le 04/01/2011 22:24, Noel Jones a écrit : > > On 1/4/2011 3:04 PM, pf at alt-ctrl-del.org wrote: > >> > >> I'm trying to stop the chain of: > >> Sender calls recipient, recipient calls their tech, > >> recipient's tech calls me... Then I tell them to contact the > >> sender's admin... Then the sender's admin claims that > >> "everyone" else accepts their email, even though they don't > >> have any reverse dns, and suggests that I add an exception for > >> their servers. > >> > >> I would hope that occasionally someone in that chain would > >> notice the url and read it, saving everyone else's time. > >> I rarely get "why are you blocking me?" for rbl listed > >> domains, so I'm guessing that those client specific self > >> service urls do provide some benefit. > > > > > > There won't be reject-specific text anytime soon; the effort is just > too > > high. Implementing custom text for just a few reject_* restrictions > > would raise false expectations, and is unlikely to be implemented > > judging from past half-solution proposals. > > I would love it if the client IP could be included in the message. This > is useful because the guy at the other end doesn't necessarily knows > which IP contacted us; and the IP syntax doesn't cause problems with > URLs. (well, I am also saying this because almost all of my rejections > are based on the IP reputation). > Here also most rejections are based on the IP reputation (or rDNS). When we know the IP we can automatically check for the rDNS information (and if needed check the log file). That is also why I really would like to have the IP in it.
> but a static text is ok for me. > > > > > A "generic" self-help web link that refers them to match the first > part > > of the reject message with a list of possibilities should be > > sufficient. I believe this to be a fairly common practice already. The only missing thing is that someone has to read the not delivered messages and that is something we probably can't fix with Postfix (or other software). Regards, Mark
