View Issue Details

IDProjectCategoryView StatusLast Update
0027418Plugin - EmailReportingGeneralpublic2026-11-09 06:03
Reporterbos4711 Assigned ToSL-Gundam  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version0.10.1 
Summary0027418: Importing lots of mail for one issue does not respect the time
Description

I found this bug yesterday and it's reproducable everytime. ER monitors mailbox M and polls once an hour. Yesterday I found that one particular ticket had lots of mail to-be-imported (subject contains [Ticket XXX]), but the import did not respect the timestamps of the mail. At all. This resulted in that the bugnotes came in a random order, which screws things up.

Attaching a screenshot to show how it looks in our system. All three mails were waiting in the mailbox to be imported. My hand-drawn 1, 2 and 3 shows which order the bugnotes should have been in.

TagsNo tags attached.
Attached Files
mantis_bogus.png (47,706 bytes)   
mantis_bogus.png (47,706 bytes)   

Activities

SL-Gundam

SL-Gundam

2020-10-21 11:39

manager   ~0064574

IMAP or POP3?

bos4711

bos4711

2020-10-21 15:12

reporter   ~0064577

POP3.

SL-Gundam

SL-Gundam

2020-10-22 04:16

manager   ~0064579

We don't have a date for sorting available so we are largely depending on the order the mail server delivers the emails.
If we do want to sort on a date we would need to parse all emails first which would cause high memory usage which is not acceptable

bos4711

bos4711

2020-10-23 02:39

reporter   ~0064584

Does the same problem (lack of date) apply to IMAP as well?

SL-Gundam

SL-Gundam

2020-10-23 03:35

manager   ~0064585

Yes the PEAR extensions work largely the same in this regard.

There are plans to replace PEAR with PHP_IMAP (https://www.php.net/manual/en/book.imap.php)
But thats still a while away

SL-Gundam

SL-Gundam

2026-11-09 06:02

manager   ~0071582

Last edited: 2026-11-09 06:03

IMAP now uses the UID. This should suffice since the number will increase on every new email received.
Fixed in EmailReporting 0.13.0 and later versions

This is not fixable for POP3