[Mailman-Users] Redirect all -bounce emails

[Tom Kavanaugh]

Hi Mark,

Thanks for your response and suggestions.

> You can get away without some of the others if you don't tell people about
them, and they > don't expect them to work from other Mailman experience.

I can get away with all the other addresses with every list. It is only the
listname-bounce that worries me.

>If you're thinking that you can get around the issue by having all bounces
from any list be
>returned to the 'mailman' list posting address, you could do this in the
source code, but >not by using aliases on mine.name.com.

Yes, this is precisely what I want to accomplish. Could you point me to some
place, or the portion of the code that needs to be tinkered with. I am not a
perl/python person, so this is going to be a huge learning curve for me.

Regards
Elvis


On 2/11/06, Mark Sapiro <msapiro at value.net> wrote:
>
> Tom Kavanaugh wrote:
> >
> >I setup a few mail lists (including default mailman list) in
> >name.comdomain, and worked with my IT folks to redirect <maillist>@
> >name.com to my mail server <mailist>@mine.name.com
> >I do get a few <maillist-name>-bounce at name.com emails, and I would like
> to
> >re-direct all these emails to mailman at name.com (or mailman at mine.name.com)
> >Does someone have ideas how to accomplish this?
> >
> >I do not administer the company's mail servers.
> >Folks here are not open to the list.name.com domain idea, for legacy
> >reasons.
>
>
> Depending on the MTA that recieves the incoming mail for the name.com
> domain and whether it has the ability through NTFS or whatever to
> access files or directories on mine.name.com, it may or may not be
> possible to do something to direct all list mail to mine.name.com by
> looking at aliases or whatever on mine.name.com, but that may be even
> less acceptable to the IT folks than just installing the necessary
> aliases.
>
> See the post at
> <http://mail.python.org/pipermail/mailman-users/2006-January/048725.html>
> and the surrounding posts in that thread for more on this.
>
> Basically, there are 10 addresses per list - the listname address plus
> the 9 listname-* (where * is admin, bounces, confirm, join, leave,
> owner, request, subscribe or unsubscribe) addresses - which all must
> be able to receive mail and route it to Mailman in a way that Mailman
> can tell which of the 10 addresses it came from. In order for Mailman
> to fully function as documented, 9 of these should work (-admin is
> deprecated). You can get away without some of the others if you don't
> tell people about them, and they don't expect them to work from other
> Mailman experience.
>
>
> >I have a bunch of /etc/aliases entries for each of my mail lists on
> >mine.name.com server.
> >Is there a way I can use these alaises to re-firect <maillist-bounce>@
> >name.com to mailman at name.com
>
>
> I'm not sure what you're getting at here. If you're thinking that you
> can get around the issue by having all bounces from any list be
> returned to the 'mailman' list posting address, you could do this in
> the source code, but not by using aliases on mine.name.com. But, you
> still have the issue of the other listname-* addresses.
>
> --
> Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
>
>