#2606 Email reply not appearing at the issue
Closed: Fixed Opened by bignose.

Email replies to issues are not appearing on the issue page. I do not know whether the replies are sent to the issue subscribers.

The following messages were sent to the reply address from Pagure's issue tracking system:

All of those messages were accepted for delivery. None of them appear at the corresponding issue page, and I do not know whether they were sent on to the issue subscribers.


Just to be sure, the email address with which you sent these emails is linked to
your account on pagure.io?

(FTR the comment above was sent by email)

On 14-Sep-2017, Pierre-YvesChibon wrote:

Just to be sure, the email address with which you sent these emails
is linked to your account on pagure.io?

The messages referred to in this issue were sent from a different
address, not linked to the Pagure account.

So, if they are being silently dropped, this bug report should be
resolved by changing that behaviour. Messages to the specific reply
addresses should IMO never be silently dropped.

--=20
\ =E2=80=9CPinky, are you pondering what I'm pondering?=E2=80=9D =
=E2=80=9CI think so, |
`\ Brain, but three round meals a day wouldn't be as hard to |
o__) swallow.=E2=80=9D =E2=80=94_Pinky and=
The Brain
|
Ben Finney ben@benfinney.id.au

Messages to the specific reply addresses should IMO never be silently dropped.

What behavior would you expect then? The email got delivered to the system, it's just that processing it failed.

On 15-Sep-2017, Pierre-YvesChibon wrote:

Messages to the specific reply addresses should IMO never be
silently dropped.
=20
What behavior would you expect then? The email got delivered to the
system, it's just that processing it failed.

Because the message was to a very specific, unpublished, and hard to
guess address, it is quite unlikely to be spam. I would expect that if
there's a failure in processing the message, the sender should be
notified with an explicit error message and suggestion for what to do
instead.

--=20
\ =E2=80=9CIt's not what you pay a man, but what he costs you t=
hat |
`\ counts.=E2=80=9D =E2=80=94=
Will Rogers |
_o__) |
Ben Finney ben@benfinney.id.au

I have re-sent some of the above messages from a different email address, associated with the Pagure account.

All of those messages were accepted for delivery. None of them appear at the corresponding issue page, and I do not know whether they were sent on to the issue subscribers.

The sender email address, ben+python@benfinney.id.au, has long been associated with the Pagure account and has been able to correspond in the past with Pagure issues.

I have tried adding some debugging, could you try again?

Ok I think it may be because you're replying with a different email than the one pagure uses.
It looks like pagure sends the notifications to ben+pagure and you're replying to ben+python.

Could you try with ben+pagure?

On 18-Sep-2017, Pierre-YvesChibon wrote:

Ok I think it may be because you're replying with a different email
than the one pagure uses.

Messages have successfully been delivered and associated with issues,
sent from each of ben+pagure@benfinney.id.au and
ben+fedoraproject@benfinney.id.au.

It looks like pagure sends the notifications to ben+pagure and
you're replying to ben+python.

I have associated a number of addresses with this account, exactly
because I want to reply with an appropriate =E2=80=9CFrom=E2=80=9D address =
for each
project. I expect that the message will be delivered correctly because
the address is associated with the Pagure account.

--=20
\ =E2=80=9CScience and religion are incompatible in the same sense t=
hat |
`\ the serious pursuit of knowledge of reality is incompatible |
_o__) with bullshit.=E2=80=9D =E2=80=94Paul Z. Myers,=
2010-03-14 |
Ben Finney ben@benfinney.id.au

I think this is fixed in : https://pagure.io/pagure/pull-request/2632

Metadata Update from @pingou:
- Issue close_status updated to: Fixed

On 18-Sep-2017, Pierre-YvesChibon wrote:

Ok I think it may be because you're replying with a different email
than the one pagure uses.

Messages have successfully been delivered and associated with issues,
sent from each of ben+pagure@benfinney.id.au and
ben+fedoraproject@benfinney.id.au.

It looks like pagure sends the notifications to ben+pagure and
you're replying to ben+python.

I have associated a number of addresses with this account, exactly
because I want to reply with an appropriate =E2=80=9CFrom=E2=80=9D address =
for each
project. I expect that the message will be delivered correctly because
the address is associated with the Pagure account.

--=20
\ =E2=80=9CScience and religion are incompatible in the same sense t=
hat |
`\ the serious pursuit of knowledge of reality is incompatible |
_o__) with bullshit.=E2=80=9D =E2=80=94Paul Z. Myers,=
2010-03-14 |
Ben Finney ben@benfinney.id.au

On 29-Sep-2017, Pierre-YvesChibon wrote:

I think this is fixed in : https://pagure.io/pagure/pull-request/2632

How can we know? Should I expect a message to a Pagure issue today to
succeed, where last week it failed?

--=20
\ =E2=80=9CWe are human only to the extent that our ideas remain human=
e.=E2=80=9D |
`\ =E2=80=94_Breakfast of Champions_, Kurt Vonne=
gut |
_o__) |
Ben Finney ben@benfinney.id.au

How can we know?

By testing it once it's deployed?

Should I expect a message to a Pagure issue today to
succeed, where last week it failed?

3.8 has been released but isn't deployed in production, it will likely be after freeze is over at the end of next week.

On 01-Oct-2017, Pierre-YvesChibon wrote:

3.8 has been released but isn't deployed in production, it will
likely be after freeze is over at the end of next week.

Where can I find out whether this is ready to test?

--=20
\ =E2=80=9CHe that would make his own liberty secure must guard even =
his |
`\ enemy from oppression.=E2=80=9D =E2=80=94T=
homas Paine |
_o__) |
Ben Finney ben@benfinney.id.au

On Sun, Oct 08, 2017 at 11:35:45PM +0000, Ben Finney wrote:

bignose added a new comment to an issue you are following:
``
On 01-Oct-2017, Pierre-YvesChibon wrote:

3.8 has been released but isn't deployed in production, it will
likely be after freeze is over at the end of next week.

Where can I find out whether this is ready to test?

For one by checking the footer of pagure.io which indicates the version it's
running :)

Metadata