[otrs] FW: OTRS Scheduler Daemon Cron: MailAccountFetch

[DHil...@performair.com]

All;

I'm receiving several of the below emails every day.

From: Dominic Hilsbos
Sent: Tuesday, March 08, 2016 7:13 PM
To: Dominic Hilsbos
Subject: Undeliverable: OTRS Scheduler Daemon Cron: MailAccountFetch

<Local Exchange Server> rejected your message to the following e-mail addresses:
root@localhost
<Local Exchange Server> gave this error:
Hop count exceeded - possible mail loop
A problem occurred during the delivery of this message. Please try to resend the message later. If the problem continues, contact your helpdesk.

Diagnostic information for administrators:
Generating server: performair.com
root@localhost
<Local Exchange Server> #554 5.4.6 Hop count exceeded - possible mail loop ##
Original message headers:
<Lots of headers deleted>
Received: from otrs.performair.com (<OTRS Local IP Address>) by <Local Exchange Server>
(192.168.150.22) with Microsoft SMTP Server id 14.3.248.2; Tue, 8 Mar 2016
18:10:42 -0700
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: OTRS Scheduler Daemon Cron: MailAccountFetch
X-Powered-BY: OTRS - Open Ticket Request System (http://otrs.org/)
X-Mailer: OTRS Mail Service (5.0.5)
Date: Tue, 8 Mar 2016 18:10:46 -0700
Message-ID: <1457485846.16...@otrs.performair.com>
To: <root@localhost>
Organization: McGown Enterprises
From: OTRS Notifications <ot...@otrs.performair.com>
Return-Path: ot...@otrs.performair.com
X-TM-AS-Product-Ver: SMEX-11.1.0.1239-7.500.1018-22178.006
X-TM-AS-Result: No--0.464500-5.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No

How can I configure OTRS to either not send whatever this email is, or to send it correctly (i.e. from a proper email address, and to a proper email address)?

This behavior just started a couple days ago, though we've been running OTRS for several months. I upgrade OTRS from 5.0.5 to 5.0.7 last night, but received 4 more of these this morning.

Thank you,

Dominic L. Hilsbos, MBA, CSDA
Director - Information Technology
Perform Air International Inc.
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

[David Boyes]

Look into configuring a real host name for outgoing mail (or rewrite all outgoing headers to us...@performair.com) in your MTA configuration. That message usually triggers due to Exchange detecting unconfigured mail servers. 'Root@localhost' is usually a sign of an unconfigured system.

[DHil...@performair.com]

David;

The message is coming from OTRS, of course the MTA is unconfigured, the only thing the server does is run OTRS.

Why is there a piece of OTRS that is trying to send mail to server superuser account? What does this email (from an OTRS daemon) likely indicate?

Thank you,

Dominic L. Hilsbos, MBA, CSDA
Director - Information Technology
Perform Air International Inc.

[David Boyes]

> On Mar 9, 2016, at 10:26 AM, "DHil...@performair.com" <DHil...@performair.com> wrote:
>
> David;
>
> The message is coming from OTRS, of course the MTA is unconfigured, the only thing the server does is run OTRS.

The message you quoted is an Exchange message, so the problem is there. Exchange (stupidly) has filters for common misconfigurations which are usually not helpful.

>
> Why is there a piece of OTRS that is trying to send mail to server superuser account? What does this email (from an OTRS daemon) likely indicate?

OTRS sends mail to root about configuration problems, as root is most likely to be the one that can fix it.

>From the subject line, the message is probably a notification that the OTRS scheduler is not running (just a guess) or that there's a problem fetching new mail. It's probably sending the message to all the OTRS admin ids, which include root by default.

[DHil...@performair.com]

David;

Look beyond the error message itself, and you find that the original message comes from... OTRS. Transferred directly to my internal Exchange server, as it should (and does) do with all OTRS communications. This communication, apparently from one of the cron job(s) doesn't use correct email addresses.

Received: from otrs.performair.com (<OTRS Local IP Address>) by <Local Exchange Server>

<Local Exchange Server IP> with Microsoft SMTP Server id 14.3.248.2; Tue, 8 Mar 2016

18:10:42 -0700
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: OTRS Scheduler Daemon Cron: MailAccountFetch
X-Powered-BY: OTRS - Open Ticket Request System (http://otrs.org/)
X-Mailer: OTRS Mail Service (5.0.5)
Date: Tue, 8 Mar 2016 18:10:46 -0700
Message-ID: <1457485846.16...@otrs.performair.com>
To: <root@localhost>
Organization: McGown Enterprises
From: OTRS Notifications <ot...@otrs.performair.com>
Return-Path: ot...@otrs.performair.com
X-TM-AS-Product-Ver: SMEX-11.1.0.1239-7.500.1018-22178.006
X-TM-AS-Result: No--0.464500-5.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No

Higlights:
Received: from otrs.performair.com

Subject: OTRS Scheduler Daemon Cron: MailAccountFetch

From: OTRS Notifications <ot...@otrs.performair.com> (WTH does this address com from?)

How can I get the Cron job(s) to not send email to my mail infrastructure?

Thank you,

Dominic L. Hilsbos, MBA, CSDA
Director - Information Technology
Perform Air International Inc.

-----Original Message-----
From: otrs-b...@otrs.org [mailto:otrs-b...@otrs.org] On Behalf Of David Boyes
Sent: Wednesday, March 09, 2016 9:08 AM
To: User questions and discussions about OTRS.
Subject: Re: [otrs] FW: OTRS Scheduler Daemon Cron: MailAccountFetch

[Gerald Young]

The address is NotificationSenderEmail in Framework::Core 

Default value: otrs@<OTRS_CONFIG_FQDN>

> How can I get the Cron job(s) to not send email to my mail infrastructure?

It's sending to root@localhost because there is an agent or notification recipient with root@localhost as an email address that's accepting notifications.