"Miquel E. Cabanas" <Miquel.Cabanas@uab.es> writes:

I am using SmartList v3.14 to run a small list. Today I was

SmartList v3.14? That was only seen in prerelease, ala 3.14pre. What's the output of ".bin/flist -v"?

forced to disable the auto-remove features because procbounce insisted in identifying one of the list members as responsible of all bounces related to messages he had submitted to the list instead of the real bouncers.

He also claims to get back lots of autoreplies (i.e. vacation messages and the like) and error messages, though it is my understanding that such messages should go back to the list-request, and forwarded exclusively to the list master...

Before going too much further, you should make sure that messages you get from the list have a Return-Path: header field or "From " line that has the list's -request address. If not, then something is keeping SmartList from putting the correct envelope sender address on the outgoing messages. If that's not the case, then apparently lots of the people on your list have broken mail servers and vacation responders. Assuming this is a "discussion list", where most people reply to the list, you could try setting the "From:" address on outgoing messages to the list address. This is probably most easily done by setting the "reply_to" variable in the list's rc.custom file, ala: #reply_to reply_to = "From: $listaddr" # uncomment to force replies to # go to the list (discouraged) # why discouraged? see: # http://garcon.unicom.com/FAQ/reply-to-harmful.html

I've compared the header of some messages submitted by him to the list with those by other users, and, as expected, they are alike.

Did his messages include a Reply-To: header?

For the case it might help, this person uses PINE as MUA, other people from his lab using other MUAs do not get unsubscribed, neither complain about getting autoreplies or error messages.

Well, then *something* must be different about his messages... Philip Guenther Procmail Maintainer