Found that article:
http://www.msexchange.org/articles/customizing-mailbox-limit-warnings-quota-message-service.html
The other thing i see is misbehaving is that we did set the Issue Warning on
System Policies for all users to 350Mb.
When this limit is reached users receive the message that their
Outlook 2003
Exchange 2003
Windows XP clients
We have had reports of some users in outlying sites (connected via ATM
155mps line) that Outlook 2003 is sometimes freezing when sending emails
and getting a balloon popping up regarding retrieving data etc.
I have been sent a screen shot of the Excha
From: Ellis, John P. [mailto:johnel...@wirral.gov.uk]
Sent: 23 May 2011 13:56
To: MS-Exchange Admin Issues
Subject: Outlook freezing
Outlook 2003
Exchange 2003
Windows XP clients
I was sent a screen shot, but didnt send it to the list just in case.
Ive not check thed GC yet, we have about 4500 users and a few GCs
I am yet to try the Exchange Trouble shooter yet. Ours Comms team are
checking some stats on their switches etc so fingers crossed they may
spot something.
Cheers
Would like to point out that there are a lot of legit companys using .info.
We have 4 clients with .info domains,
Regards
Graeme
On 23 May 2011 15:01, Jean-Paul natola wrote:
>
> Hi all,
>
> I've been monitoring the the spam and noticed that over 98% is coming from
> some bogus *.info domai
I am aware of that, which is why I wanted initially to raise the scl and
quarantine it.
Date: Mon, 23 May 2011 15:03:20 +0100
Subject: Re: Blocking by domain types
From: loonyto...@gmail.com
To: exchangelist@lyris.sunbelt-software.com
Would like to point out that there are a lot
Generally one uses sender filtering to block an entire domain or specific
senders in a domain.
http://technet.microsoft.com/en-us/library/bb125179.aspx
Carl
From: Jean-Paul natola [mailto:jnat...@hotmail.com]
Sent: Monday, May 23, 2011 10:02 AM
To: MS-Exchange Admin Issues
Subject: Blo
but that is only for a whoile domain (specific domain and / or email address),
it wont allow wildcard
Ideally i'd like to do *.info
below are a couple of the domains im referring to
@tyumanimo.info
@qqo92.superiorcompound.info
@overviewrealization.info
It would not be feasible to manual
I dont know what I am missing but when i try to add it I get
Some controls arent valid
Error while converting string '*.info" isnt a valid smtp domain
Error while converting string '@*.info" isnt a valid smtp domain
Error while converting string '*@.info" isnt a valid smtp domain
We have been receiving spam from a certain MS customer for several months
now, sent to a couple role email addresses that clearly have been scraped
from our website or garnered through purchased lists. No way this went
through confirmed opt-in... It's not terribly high volume, but it's also
not goi
Report the domain to any of several BLs, including spamcop, spamhaus, etc.
On Mon, May 23, 2011 at 09:56, Jason Gurtz wrote:
> We have been receiving spam from a certain MS customer for several months
> now, sent to a couple role email addresses that clearly have been scraped
> from our website o
Try forwarding the message with full headers to .
The number the provide to customers is 1-866-291-7726. I'm not sure they will
talk to you if you are not a customer but the call is on their dime so it might
be worth a shot.
-jim
James Rupprecht
Senior Systems Specialist
Microsoft Exchange &
We are testing the procedure for shutting down Exchange 2003 in an Exchange
2007 environment. We had to keep E03 for a while due to a software connector
pointing to the Public Folders that wasn't compatible with E07 for a long time.
That has been resolved, so we're ready to move the PF's to E07
Yes, I figured out one way to fix it on my support call with Microsoft when we
first started migrating to Exchange 2010. For us, the issue stemmed from a
particular MAPI attribute that was not stamped in Exchange 5.5. For us it was
the MAPI attribute: PR_PF_PROXY_REQUIRED
First, get PFDAVAdmi
Currently within Exchange 2010, we do not allow anonymous relaying of mail to
the outside except from specific internal IPs via the Relay Connector.
The problem I have is a network application being used that attempts to send
mail from the local workstation via an SMTP tool from within the "fat
I haven't tried this, so don't hold me to it - but I think you could manage
this with a transport rule. It might take two working together, but I think you
could make it happen.
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
From: Robert Peterson [mailto:
Hi All,
A big thank you to the forum!
I transitioned my Exchange to 2010 from 2007 without any issues with the help
of the forum.
I am looking for a backup solution for my Exchange 2010. What are my options?
I have 13 database. Right now I am using Windows 2008 R2 SP1 Windows Server
Backup.
17 matches
Mail list logo