[#286] GRASS issuetracker: reply-to address modification request

Hi Sascha,

seems to help! A recent report is now set to grass-dev
as From: (instead of intevation).

Thanks for this! you may close the report.

Markus

Sorry, the second part of my last message was of cause nonsense. As this issue is not in a tracker of the GRASS project you can't see the effect on the messages sent by the Site Admin tracker.

Please check the effect with any tracker of the GRASS project and report if it is what you needed...

Cheers
Sascha

Hi *,

I have developed a patch which allows to set the reply-to address for all mails generated by the trackers of one group (project).

I have now activated this feature for GRASS, the effect should be visible in the mail generated for this entry.

Does that help?

Cheers
Sascha

For what its worth: this is most likely an Debian issue
(at least our installation is based on the GForge Debian packages and the mail-subsystem always were a source of endless trouble).

I'll recheck with a fresh vanilla stable (etch) setup -- if it works there porting to wald shouldn't be too hard.

We will find out what the problem is.
Sorry for the hassle.

In the meantime, setting the reply-to with Mailman
should at least have all replies go to the mailinglist.
Or are you saying that Mailman would not replace the reply-to header?

Their answer:

http://gforge.org/tracker/?func=detail&atid=119&aid=2894&group_id=1
>Comment By: Timothy Perdue (bigdisk)
Date: 2007-05-17 07:08
>Status: Closed
Message:
Reply to trackers has worked for years now. Closed.


At this points I am lost. Seems to be a "wald" issue then.

Markus

Hi Bernhard,

the problem consists of two parts:

1. (non) acceptance of CCed emails in Gforge

2. reply-to not set to grass-dev (if 1. is impossible)

A current header example:

From grass-coder@wald.intevation.org Thu May 17 13:41:43 2007
Reply-To: grass-coder@wald.intevation.org
To: noreply@wald.intevation.org
From: <grass-coder@wald.intevation.org>
Date: Thu, 17 May 2007 13:42:00 +0200 (CEST)
Subject: Re: [grass-code R][392] raster metadata: units and veritcal datum -> cell_misc/
Return-Path: grass-coder@wald.intevation.org
code R item #392, was opened at 2007-05-04 08:41

If I reply, it goes to grass-coder@wald.intevation.org which then responds

wald.intevation.org[78.47.251.62] said: 550
<grass-coder@wald.intevation.org>: Recipient address rejected: User
unknown in local recipient table (in reply to RCPT TO command)>

To make at least 2. possible, the reply-to should be grass-dev. Certainly this is a poor workaround, since 1. is desired and worked quite well for the old RT (double spam testing with spamassasin at RT level and bogofilter at grass-dev level + handwritten extra procmail rules).

Cheers,
Markus

Hi Markus,

thanks for opening the issue about accepting
email responses with gforge.org!
Actually I believe this is our http://wald.intevation.org/tracker/index.php?func=detail&aid=85&group_id=1&atid=162
so we should delay discussion about accepting updated
information in there.

Originally you described the problem for this very ticket
to be the reply-to header. The mailman should solve this
problem, as replies will go to the mailinglist then.
If it does not I am unsure if I understand this part
of your problem good enough.

I have now reported this upstream:

http://gforge.org/tracker/index.php?func=detail&aid=2894&group_id=1&atid=119

Some comments:

> search for reply_to_address in the [General Options] section
> of the Mailman administration web interface for
> the list.

It is already set to grass-dev there but this doesn't help for the problem (apparently).

> We will do something
> about those problems of course as we want to provide a
> good infrastructure.

Great - please think about a workaround, because...

> As to accepting email replies, I suggest to open another
> seperate issue for it. Gforge has a lightweight issue-tracking
> and ideally I would want a roundup-plugin for
> it.

... you posted this there in 2004 and this is some years ago. I am afraid that it will take years to get our wish implemented upstream. And I think that we should not go back to the good old RT.

thanks,
Markus

Markus,

search for reply_to_address in the [General Options] section of the Mailman administration web interface for
the list.

As for submitting the issues to Gforge: Your impact
will be as good as ours. The good point about using a
transparent software with a community
is that all people that want
to help us to make the software better can actually do so.
So if you our other people from GRASS want to improve
Gforge they are not limited by us. We will do something
about those problems of course as we want to provide a
good infrastructure.

As to accepting email replies, I suggest to open another
seperate issue for it. Gforge has a lightweight issue-tracking and ideally I would want a roundup-plugin for it. http://gforge.org/tracker/?group_id=1&atid=119&func=detail&aid=931

> We should
> a) open up a new feature request with gforge
> to have it configured for new tracker entry which
> reply-to address they get.

Since my impact factor at gforge is most likely zero, I suggest to get it submitted by an Intevation Gforge admin.


> b) Markus, you can change
> this at the grass-dev@ mailinglist side as well.
> Ideally, users would use a list-reply feature for
> their response on a grass-dev@ post. But you can enable
> reply-to mangeling for all posts.
> As far as I understood it would solve your problem.
> Did I get this right?

Yes and no. The overall goal is that replies on the bug report can be CC'ed to the gforge tracker, too, to keep it in sync (the good old RT did so). Some reply-to mangling (not sure where to enable in Mailman) would avoid at least the mails to no-reply but it doesn't solve the real problem.

I am raising priority.
We should
a) open up a new feature request with gforge
to have it configured for new tracker entry which
reply-to address they get.
b) Markus, you can change
this at the grass-dev@ mailinglist side as well.
Ideally, users would use a list-reply feature for
their response on a grass-dev@ post. But you can enable
reply-to mangeling for all posts.
As far as I understood it would solve your problem.
Did I get this right?

The discussion on the GForge project site your link points to is an a different (though related) subject: they are talking about the "Task Manager", which seems to generate mails, too.

The subject we are having here is slightly different: It is true, that having the reply address of the tracker mails set to a non valid address is inconvenient, but in fact this is a (AFAIK Debian) workaround for the fact, that replying to the tracker itself doesn't work as expected.

The expected (at least by me, and some projects I know) behavior for trackers is this: When replying to a mail send by a gforge tracker, the reply is handled by the tracker just as if it have been written as an reply in the web interface.

So the behavior requested by you seems to differ from the general solution to the problem.

Maybe we can implement some special handling for all mails send to grass-dev AT grass.itc.it but I don't have the time to check this posibility right now (I'm currently working on moving wald.intevation.org onto a new hardware).

cheers
sascha

http://gforge.org/tracker/?group_id=1&atid=105&func=detail&aid=508

Their suggestion is useless for us.

This is a pressing bug which causes quite some pain for the development.

Markus

We need to do something about this in general.
If anybody wants to help,
check the http://www.gforge.org site for such a request,
if necessary add one and add it here.