On Sun, April 1, 2012 4:41 pm, Mike Scott wrote: > Actually, while I remember a disagreement, I'm not sure myself of the > details. I think it might have been about using some sort of engine to > guess a likely answer to unsubscribed queries - I vaguely seem to recall > you didn't approve:
Yes, now I remember, thanks. I stepped in because you suggested a bayesian autoresponder, and I explained why in my opinion it wouldn't work in this case. But it was a purely technical disagreement, nothing personal. Heck, I was so happy to have found somebody else that didn't want to "send again to unsubscribed user"!. Anyway, it's all in the thread I posted yesterday. apologies if my memory is wrong. > > On that latter point, do I understand correctly that the basis of your > approach is to track incoming unsubbed emails, and automatically copy > corresponding list responses to their originators, so removing the > subbed/unsubbed issue entirely? Response would still be from a person, > but they'd not have to worry that the originator might not receive the > reply. correct. The way I propose to recognize unsubscribed users is the ONLY one that can work because, running on the same server as the mailing list software, can do it in the right way: checking if the sender address is in the list of subscribers :-) Then it sends copy of all and only the list replies to that message to that sender address. Details in the thread I posted yesterday, there's no need I type the whole thing again. > plus carefully worded information about subscribing and > the benefits (and otherwise) of doing that. One might mix both approaches Bayesian filters cannot work in this case because they assume that the sender knows what he's talking about. And it's not needed at all, if the sender receives answers from real humans anyway. But of course the copy automatically sent by the autoresponder can and should have added the extra info you describe. Marco --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
