プロジェクト

全般

プロフィール

Vote #80876

未完了

Emails not being processed because of

Admin Redmine さんが約2年前に追加. 約2年前に更新.

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Email receiving_29
対象バージョン:
-
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
29
version_id:
0
issue_org_id:
33440
author_id:
458745
assigned_to_id:
0
comments:
1
status_id:
1
tracker_id:
3
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

I have Redmine receive email via SMTP. I noticed about 90% of them go through just fine, that 90% of emails would update their associated tickets no problem.

However, the other 10% would not work. It would be stuck in limbo (in the inbox). I was able to track it down from the

mail_handler.rb > dispatch

The email's header for in_reply_to did not have the correct value to extract the proper object_id.

Here is an example:

References: redmine.issue-12345.20200428144405.5@omitting.com,redmine.journal-67890.20200512212705.5@omitting.com
In-Reply-To: redmine.journal-67890.20200512212705.5@omitting.com

In this example, the 12345 was the correct ticket number, while 67890 does not exist in our Redmine.

I think the header array needs to switch from:

@headers = [email.in_reply_to, email.references].flatten.compact@

to:

@headers = [email.references, email.in_reply_to].flatten.compact@

OR

The regex for MESSAGE_ID_RE needs to point to include issue

OR

dispatch has a validation to check if the object_id exists or not. If it does not, it moves on to the next array key.


journals

We are experiencing a similar issue with mail reception in case of multiple redmine instances and agents answering to one instance into another instance.

However for our case, switching the header priority is not enough as we would need to distinguish between several redmine instances.
--------------------------------------------------------------------------------

Admin Redmine さんが約2年前に更新

  • カテゴリEmail receiving_29 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0