How does OTRS digest tickets? If it's POP3, then see if there's information
that your mail server is getting the ticket.
Check cron jobs (daily and time scheduled).
Look at the header and see if there's an SMTP sender.
If all else fails, you may have to test for that ticket in PostMaster
Filter and set it for X-OTRS-Ignore 1 or yes.
If you know generally when the ticket is created, you may be able to
disable otrs cron jobs for the few minutes while you're looking at the
mailbox manually.
If it's not in the mailbox, it may be "stuck" in the OTRS spool
folder/directory and has permissions set that do not enable OTRS to delete
the file.
On Wed, Oct 26, 2016 at 10:25 AM,
All;
Last week I made a network topology change that temporarily broke OTRS' email abilities (it had no route to the email server).
After fixing the networking issues I sent an email to OTRS to verify that everything was working correctly. OTRS behaved as predicted, and all was right with the world.
However, ever since then we have been receiving a spurious ticket at 12:10 (+/- 10 seconds or so), which has as its body the complete text the test email, including SMTP headers and raw encoding.
I have tried rebooting OTRS' server, with no luck. I have not tried to Google the issue, as I don't feel my Google Fuu is up to trying to explain the situation to Google search.
Does anyone have any suggestions on next steps to correct this behavior?
CentOS 7 / Apache 2.4.6 OTRS 5.0.11 ITSM GC 5.0.11 ITSM Core 5.0.11 ITSM Change Management 5.0.11 ITSM Configuration Management 5.0.11
Thank you,
Dominic L. Hilsbos, MBA, CSDA Director - Information Technology Perform Air International Inc. www.PerformAir.com
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs