Ok, so I'm finally stepping out to consult on a more regular basis...sort
of. my father passed away, and I'm taking over some of his business. He ad
a local land line, a local fax line, and an 800 number. I need (and want)
to move all three of those from the PRI they presently run on to a cloud
Hi guys,
I'm having issues with sending some very large attached files.
the issue is that i'm not sure where the issue really is.
I have upped the limit in Exchange 2007 to 30M, Set-TransportConfig
-MaxReceiveSize 30MB -MaxSendSize 30MB
and there are no limits on the Users mailboxes.
On our
On Wed, Oct 17, 2012 at 8:05 AM, S Powell powe...@gmail.com wrote:
Hi guys,
I'm having issues with sending some very large attached files.
the issue is that i'm not sure where the issue really is.
I have upped the limit in Exchange 2007 to 30M, Set-TransportConfig
-MaxReceiveSize 30MB
My guess is that the attachment is increasing in size as it's encoded.
Take a look at this:
http://searchexchange.techtarget.com/tip/Outbound-message-size-changes-due-to-format-conversions
I've never used that utility before, but I think you need to figure out
the size that Exchange is
Did you restart the Transport service?
On Wed, Oct 17, 2012 at 11:05 AM, S Powell powe...@gmail.com wrote:
Hi guys,
I'm having issues with sending some very large attached files.
the issue is that i'm not sure where the issue really is.
I have upped the limit in Exchange 2007 to 30M,
Okay, thank you all, I found one answer, It was the IronPort that was the issue.
it was a rule in the Relay settings.
now I can send, just not encrypt our large files... sigh...
calling cisco now
-
Sub ubi semper ubi
On Wed, Oct 17, 2012 at 10:19 AM, Candee
I hate it when two things go wrong at once, or I just notice them at once and
think they went wrong at once.
The NSLookup issue was because somehow my IPV6 nics had given themselves an
entry for dns lookups. That causes the issue I saw with NSLookup according to
google. I will look more into
I don't know about IronPort specifically, but its not uncommon for e-mail
encryption solutions to enforce a specific size limitation on messages to
be encrypted.
- Saen
On Wed, Oct 17, 2012 at 1:07 PM, S Powell powe...@gmail.com wrote:
Okay, thank you all, I found one answer, It was the
I've got two healthcare clients where this is a major problem.
They don't even attempt to debug. If someone reports a problem, any problem,
they immediately re-image; and then forensically examine network traces and log
files to see if any info can be gleaned.
From: Roger Wright
Did you attempt to reboot everything at once?
The Exchange errors occur because Exchange cannot determine what its AD site
should be. Exchange 2010 SP2 should fix this automagically about 10 minutes
after netlogon finally starts. If it doesn't, you can hardcode the site that
Exchange should be
10 matches
Mail list logo