Page MenuHomePhabricator

OTRS notification system keeps recreating old mails in queues
Closed, ResolvedPublic

Description

Author: tomasz.sienicki

Description:
Since the upgrade of OTRS *exactly the same* 12 old emails reappear everyday in the info-pl queue; and the same 12 notifications are mailed everyday (every time with a new ticket number).

These are emails with subject lines:

  1. [Ticket#(new number every time)] New ticket notification! ([Ticket#2007012010 [...])
  2. [Ticket#(new number every time)] New ticket notification! (Spis latarń)
  3. [Ticket#(new number every time)] New ticket notification! ([Ticket#2007020310 [...])

+ 9 mails in Chinese.


Version: unspecified
Severity: major

Details

Reference
bz10043

Event Timeline

bzimport raised the priority of this task from to High.Nov 21 2014, 9:50 PM
bzimport added projects: Znuny, Shell.
bzimport set Reference to bz10043.
bzimport added a subscriber: Unknown Object (MLST).

jeluf wrote:

2007020310 is not a valid ticket ID. Please provide more detail.

tomasz.sienicki wrote:

(In reply to comment #1)

2007020310 is not a valid ticket ID. Please provide more detail.

OK, look at these:

  • [Ticket#2007052710000347]
  • [Ticket#2007052610000536]
  • [Ticket#2007052510000396]

This is one of the 12 mails that reappear everyday.

jeluf wrote:

There are some tickets hanging in the spool directory. Those are among them. I removed all of them, but I don't yet understand why tickets stay in the spool directory *and* go into OTRS at the same time.

So while removing them makes those tickets go away, new ones will likely appear sooner or later.

tomasz.sienicki wrote:

Again, the same situation: we have 5 mails that re-appear everyday:

[Ticket#2007081410000428]
[Ticket#2007081410000401]
[Ticket#2007081410000366]
[Ticket#2007081410000357]
[Ticket#2007081410000339]

jeluf wrote:

Removed all mails from /opt/otrs/var/spool

Looks like a bug in the perl script that processes mails. It crashes after inserting the ticket into the DB.