Answer to the Reports not emailing you.

[gotkimchi]

Scenario: Reports are no longer being emailed to you. This might have worked on previous versions.

Solution: First, you will need to check your email setting on the Untangle. Yes, we know that on the previous version this might have worked.
If you do not have your own mail server, you will need to select send email directly. Please note, some ISPs block sending out SMTP so this might not work. You might want to try this setting:
http://forums.untangle.com/attachmen...on-utgmail.jpg

If you do have your own mail server, you will need to select use specified SMTP server, put the IP address of the email server. (Some will require authentication and some do not, pending on the email server). Please be sure to put a valid from email address.

Also some networks, you will need to put the Untangle's IP address on the allow relay.

After setting all this up, run the email test (try one internal email address and one external).

If the email works, uninstall the reports module off the rack, and reinstall. Make sure to write down the email addresses on the reports module, just in case.

If the email does not work, you will need to check out the logs:
To trouble shoot this, if you have SSH access (command line), you can check the mail log by typing this:

less /var/log/exim4/mainlog

***Just found out that if you have a special character on the name (using the branding manager), that will cause the reports to not generate and/or sent out.***

[sswanson@ultisat.com]

Following the helpful advice in the original post of this thread, I discovered the reason I was not receiving reports via e-mail.

The exim log complained that the e-mail was too big...

2010-02-18 03:20:54 rejected MAIL FROM:<inetgw3@ultisat.com> H=localhost (localhost.localdomain) [127.0.0.1]: message too big: size=63835195 max=52428800

After unchecking the "Attach Detailed Report Logs..." setting, I have received a report each day.

Good luck,

Scott

[boyan.sharic]

Originally Posted by sswanson@ultisat.com

The exim log complained that the e-mail was too big...

Scott,

what do You mean too big? You used up all Your inbox space or the e-mail was too big for the mail server to send?

[WebFooL]

boyan.sharic,
I think that the message was to big.
Most Email servers can set a Message limit.

[sky-knight]

Yeah if it's too big don't send the CSV data.

[boyan.sharic]

i did everything that gotkimchi said and reports really were sent to e-mail...BUT only if I turn off "Attach Detailed Report Logs to Email"

if that option is on - no e-mail.

[boyan.sharic]

ill try different mail server and see how it goes

[datajockeys]

The way the report attachments are sent, OS X Email will download the message (all of the data is there) but it will not show up in the message as an attachment. Stealth reports? :-) Apple has verified this issue. Please take a look at the way the file is being attached so us OS X users can go back into Happy Camper Land.

[mrunkel]

Originally Posted by datajockeys

The way the report attachments are sent, OS X Email will download the message (all of the data is there) but it will not show up in the message as an attachment. Stealth reports? :-) Apple has verified this issue. Please take a look at the way the file is being attached so us OS X users can go back into Happy Camper Land.

Today, we were investigating this very issue for a customer. They would receive the email see that was very large in size but their client wouldn't show an attachment. In the course of troubleshooting we added ourselves to the reports distribution list.

This very same email that the client couldn't open, opened for us in the following email clients:

Thunderbird version 2.0.0.16 (20080707) on OS X
Outlook 2007 on Windows XP
mutt on debian
Mail on OS X - Version 4.2 (1078)
Outlook Web Access - Exchange 2007

This message was sent directly from the customer untangle, filtered by our untangle for spam/anti-virus and delivered to our unix mail front end. It was then passed on to our exchange server.

We did have one system in the network that couldn't open the attachment, but that turned out to be an issue with AVG anti-virus mangling the mime encoding.

It still appears that the issues with hidden attachments is happening in transit between the untangle sending the message and the client reading it. Messages sent unmodified from the untangle have always been viewed normally.

For those interested, here is what the mime encoding should look like. Yours should be similar, if they aren't, something in the path has modified the message.

Received: from mail.untangle.com (12.181.48.133) by email.untangle.com
 (12.181.48.132) with Microsoft SMTP Server (TLS) id 8.1.393.1; Fri, 2 Apr
 2010 00:10:33 -0700
Received: from [75.102.13.23] (helo=dogcloud.untangle.com)	by
 mail.untangle.com with esmtp (Exim 4.63)	(envelope-from
 <untangle@untangle.example.com>)	id 1Nxb1V-0005eh-9N	for
 supportteam@untangle.com; Fri, 02 Apr 2010 00:10:33 -0700
Received: from localhost ([127.0.0.1] helo=localhost.localdomain)	by
 dogcloud.untangle.com with esmtp (Exim 4.69)	(envelope-from
 <untangle@untangle.example.com>)	id 1Nxb1S-00069S-4h	for
 supportteam@untangle.com; Fri, 02 Apr 2010 02:10:30 -0500
From: "untangle@untangle.example.com" <untangle@untangle.example.com>
To: supportteam <supportteam@untangle.com>
Content-Class: urn:content-classes:message
Date: Fri, 2 Apr 2010 00:10:30 -0700
Subject: New Untangle Daily Reports Available
Thread-Topic: New Untangle Daily Reports Available
Thread-Index: AcrSM5YZKWUYqaa1RRSPLdmOfP7xYw==
Message-ID: <E1Nxb1S-00069S-4h@dogcloud.untangle.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-AuthSource: EXCHANGE.Untangle.local
X-MS-Has-Attach: yes
X-Auto-Response-Suppress: DR, OOF, AutoReply
X-MS-Exchange-Organization-SenderIdResult: Fail
X-MS-Exchange-Organization-PRD: untangle.example.com
X-MS-TNEF-Correlator:
received-spf: Fail (EXCHANGE.Untangle.local: domain of
 untangle@untangle.example.com does not designate 12.181.48.133 as permitted
 sender) receiver=EXCHANGE.Untangle.local; client-ip=12.181.48.133;
 helo=mail.untangle.com;
Content-Type: multipart/mixed;
	boundary="_004_E1Nxb1S00069S4hdogclouduntanglecom_"
MIME-Version: 1.0

--_004_E1Nxb1S00069S4hdogclouduntanglecom_
Content-Type: multipart/alternative;
	boundary="_000_E1Nxb1S00069S4hdogclouduntanglecom_"

--_000_E1Nxb1S00069S4hdogclouduntanglecom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The Untangle Summary Reports for 03/31/10 - 04/01/10 are attached. The PDF =
file requires Adobe Reader to view.

--_000_E1Nxb1S00069S4hdogclouduntanglecom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<HTML>
The Untangle Summary Reports for 03/31/10 - 04/01/10 are attached.
The PDF file requires Adobe Reader to view.
</HTML>=

--_000_E1Nxb1S00069S4hdogclouduntanglecom_--

--_004_E1Nxb1S00069S4hdogclouduntanglecom_
Content-Type: application/pdf; name="reports-040210-Daily.pdf"
Content-Description: reports-040210-Daily.pdf
Content-Disposition: attachment; filename="reports-040210-Daily.pdf";
	size=441169; creation-date="Fri, 02 Apr 2010 00:10:33 GMT";
	modification-date="Fri, 02 Apr 2010 00:10:33 GMT"
Content-Transfer-Encoding: base64

JVBERi0xLjMNCiWTjIueIFJlcG9ydExhYiBHZW5lcmF0ZWQgUERGIGRvY3VtZW50IGh0dHA6Ly93
d3cucmVwb3J0bGFiLmNvbQ0KJSAnQmFzaWNGb250cyc6IGNsYXNzIFBERkRpY3Rpb25hcnkgDQox

[u3b3rg33k]

I just realized I'm in the sinking UT/OS X boat, too. Good to know what's going on.