[itdiscuss] [BULK] RE: help!

Wed Feb 3 18:01:46 EST 2010

Darin, 

Sounds like you need to use a file send type application rather than
email... you can try to use one of the free solutions filesend.net,
rapidshare.net etc..or purchase a product like this for ongoing use..
http://www.xigla.com/afilesend/

We are rolling out the afs product currently, if you need to use ours
for one time use drop me a note and we'll get you the info you need to
use it.

- jason

From: discuss-bounces at itdiscuss.org
[mailto:discuss-bounces at itdiscuss.org] On Behalf Of Darin Rohatinsky
Sent: Wednesday, February 03, 2010 4:54 PM
To: IT Discussion Forum
Subject: Re: [itdiscuss] [BULK] RE: help!

Well there are two problems.  First is the ability to send a 20MB
attachment to an outside address.  Because I increased the limit to
35MB, as a test, the end user sent one to me (same Google Apps domain).
That's what the error below is from.  Is there a way to find out for
sure if it's possible?

2010/2/3 Lou Hablas <Lou.Hablas at rzim.org>

or perhaps Google Apps won't allow it.

If inhouse, can't you just drop the file on a file share?

________________________________

From: discuss-bounces at itdiscuss.org
[mailto:discuss-bounces at itdiscuss.org] On Behalf Of Darin Rohatinsky
Sent: Wednesday, February 03, 2010 1:19 PM
To: IT Discussion Forum
Subject: [itdiscuss] help!

I have a user trying to send an attachment that is 10-20MB just inhouse,
via Google Apps.  I have set the limit of attachments to 35MB and he
gets this error: 

---------- Forwarded message ----------
From: Mail Delivery Subsystem <mailer-daemon at googlemail.com
<mailto:mailer-daemon at googlemail.com> >

Date: Fri, Jan 22, 2010 at 2:18 PM
Subject: Delivery Status Notification (Failure)
To: shawnl at livinghopechurch.com <mailto:shawnl at livinghopechurch.com> 

Delivery to the following recipient failed permanently:

    darinr at livinghopechurch.com <mailto:darinr at livinghopechurch.com> 

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the
recipient domain. We recommend contacting the other email provider for
further information about the cause of this error. The error that the
other server returned was: 552 552 Message too large - psmtp (state 18).

----- Original message -----

MIME-Version: 1.0

Received: by 10.142.8.38 with SMTP id 38mr2390668wfh.58.1264198720959;
Fri, 22
       Jan 2010 14:18:40 -0800 (PST)
Date: Fri, 22 Jan 2010 14:18:22 -0800
Message-ID: <efad1761001221417j723daaf8vf26ec4efc1e1686d at mail.gmail.com
<mailto:efad1761001221417j723daaf8vf26ec4efc1e1686d at mail.gmail.com> >
Subject: Testing, testing
From: Shawn Lewis <shawnl at livinghopechurch.com
<mailto:shawnl at livinghopechurch.com> >

To: Darin Rohatinsky <darinr at livinghopechurch.com
<mailto:darinr at livinghopechurch.com> >

Content-Type: multipart/mixed; boundary=00504502b240b108ec047dc833a8

-- 
Thanks,

Darin
IT Department
Living Hope Church
(360) 944-3905

LEGAL DISCLAIMER
This email (and any attachments) is confidential and intended solely for
the use of the intended recipient(s).  If you are not the intended
recipient, any disclosure, copying, distribution or action taken in
reliance on it is prohibited and may be unlawful.  If the reader of this
transmission is not the intended recipient, you are hereby notified that
any dissemination, distribution or copying of this communication is
strictly prohibited. In addition, any unauthorized copying, disclosure
or distribution of the material in this e-mail and any attachments is
strictly forbidden.The views expressed are those of the author and may
not necessarily be the views of Ravi Zacharias International Ministries.
Email transmission cannot be guaranteed to be secure or error-free,
information could be intercepted, corrupted, lost or contain viruses.
Though we scan out-bound email for viruses, we cannot accept liability
for any technical errors caused by the receipt of this email.

Spam detection software, running on the system optimus.thompsonic.com,
has
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or block
similar future email.

If you are using Outlook you can create a Rule to automatically route
email identified as spam to your Junk-Folder by adding a rule to look
for
'Spam-Status: Yes' in the email header and move the email to the
Junk-Folder

If you have any questions, see
jthompsonic at gmail.com for details.

Content preview:  or perhaps Google Apps won't allow it. If inhouse,
can't you
  just drop the file on a file share? [...]

Content analysis details:   (3.7 points, 5.0 required)

 pts rule name              description
---- ----------------------
--------------------------------------------------
 3.4 FH_DATE_PAST_20XX      The date is grossly in the future.
 0.0 HTML_MESSAGE           BODY: HTML included in message
 1.8 MIME_QP_LONG_LINE      RAW: Quoted-printable line longer than 76
chars
-1.5 AWL                    AWL: From: address is in the auto white-list

_______________________________________________
it discuss mailing list: discuss at itdiscuss.org
Mailing List: http://itdiscuss.org/discuss
Internet Relay Chat: irc://irc.freenode.net/citrt

-- 
Thanks,

Darin
IT Department
Living Hope Church
(360) 944-3905

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://optimus.thompsonic.com/pipermail/discuss/attachments/20100203/2bb61b04/attachment-0001.htm 