List,
This issue doesn't relate to exchange, it more relates to Outlook itself but
if anyone could help, it would be you guys.
I have a workstation here that has Outlook 2007 installed on it. (It
connects to our exchange server via POP / SMTP because this person has a
unique situation). The perso
On Wed, Aug 19, 2009 at 1:43 PM, Rimmel, Carl wrote:
> We all agree that this is a ridiculous subject line but the
> Peoplesoft developers refuse to alter this because
> all other email programs are working fine", only Outlook
> has an issue.
Then it's time to tell them you'll be taking your bu
I did a bunch of research a while back, and concluded 20s suited my
needs fine. It's been working great. Most spammers give up after 5 or
so, and most bulk spammers don't queue for retry anyway.
Sam
From: Bill Songstad (WCUL) [mailto:administra...@waleague.org
Very good article on greylisting (Not quite the same but close enough):
http://en.wikipedia.org/wiki/Greylisting
Given the majority of mail servers default their retry queue to ~15 minutes
earlier than that is simply making it more spam prone.
Don't know sh!t about exchanges built in spam feature
Can anyone verify for me if the Blackberry Professional software
Express, formerly known as Blackberry Small business edition will run on
SBS 2008? I have a customer wanting to upgrade from SBS03 to 08.
Looking at the info on this site does not indicate 2008 compatibility.
Maybe I'm going blind?
Nice call Carl, looks like this may have been user error. Though I set
up the recipient filtering on the Global Settings -> Message Delivery, I
neglected to get the check boxes on the SMTP Virtual Server ->
properties -> general tab -> advanced ->IP addresses -> edit ( and here
I thought that was
Does anybody have any strong opinions about how long to set your tarpit?
I've seen numbers as low as 5 seconds and as high as 30. What are the
drawbacks to using a longer tarpit?
Thanks for any feedback,
Bill
I am assuming you're using Exchange 2003, from one of the articles you linked.
Are you using a Frontend and Backend, or is everything on a single Exchange
server?
In IIS under the Secure Communications settings, are you set to "Require client
certificates"? If so, change this to ignore (unle
Ok, I was able to clean up my Public Folders.
Now however I'm trying to move the replicas to my E2K7 server using the "Move
all Replicas" command on the E2K3 server, I did this last Thursday and the
Public Folder Instances is still the same (not empty). I know it may take a
while but this long>
Still having fits with this.
We can get to my owa using https://servername.domain.com/exchange
When we try to go to https://servername.domain.com/microsoft-server-activesync
it tells me the page needs a client certificate, but I installed the
certificate on the workstation.
If we try to hit htt
Haven't used it, but I'd call it a major flaw if it causes non-existent
recipient filtering to be bypassed without providing a similar replacement
feature within its own realm.
Carl
From: Bill Songstad (WCUL) [mailto:administra...@waleague.org]
Sent: Wednesday, August 19, 2009 2:32 PM
To:
It has been awhile since I had done all that, and the other poster
jogged my memory a bit. I had also done recipient filtering, and I
believe that it will help your problem, too. That said, I am very fond
of the IronMail appliance and appreciate the workload that it takes off
the Exchange server
I'm using Sunbelt's Ninja. Crawling their forum isn't giving me any
love yet.
I'm putting together a post to see if someone on that list has an idea.
Bill
From: Carl Houseman [mailto:c.house...@gmail.com]
Sent: Wednesday, August 19, 2009 11:19 AM
To: MS-Exchange Admin Issues
Subject
They now have to go ask the Oracle?
-Original Message-
From: Rimmel, Carl [mailto:crimm...@hfhs.org]
Sent: Wednesday, August 19, 2009 11:18 AM
To: MS-Exchange Admin Issues
Subject: RE: Changing Subject Line Limits
Problem has reared its ugly head again. Turn around from Peoplesoft tech
You do have recipient filtering enabled on the SMTP VS, right? If so, then
your 'thwarting' analysis is probably right. Perhaps if this mystery spam
filter was given a name, it might lead to more suggestions about how to deal
with this. J
Carl
From: Bill Songstad (WCUL) [mailto:administr
Problem has reared its ugly head again. Turn around from Peoplesoft tech
support isn't quite what it used to be.
Carl Rimmel
-Original Message-
From: Ben Scott [mailto:mailvor...@gmail.com]
Sent: Wednesday, August 19, 2009 12:03 PM
To: MS-Exchange Admin Issues
Subject: Re: Changing Su
Yes that is what is happening. Your spam filter is what is doing the talking to
the outside mail servers, so it needs to be aware of your recipient lists in
AD. Most good ones that work with Exchange are. Take a look at its settings and
options.
From: Bill Songstad (WCUL) [mailto:administra...
LOL, brushing up on your Cobol "skills" huh?
-Original Message-
From: Doug Rooney [mailto:d...@sonomatilemakers.com]
Sent: Wednesday, August 19, 2009 9:13 AM
To: MS-Exchange Admin Issues
Subject: RE: Changing Subject Line Limits
Sorry, been busy getting ready for Y2K
-Original Me
Thanks for all the insight.
I am filtering recipients who are not in the directory, but the SMTP
queue is full of retrying messages from postmaster to addresses like
"SMTP:w...@201-232-13-44.epm.net.co".
I wonder if these messages are being accepted by the spam filter (it
sits in an SMTP
+1
From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org]
Sent: Wednesday, August 19, 2009 10:48 AM
To: MS-Exchange Admin Issues
Subject: RE: NDRs backscatter and such
Carl gave you the correct answer. I'll just add that his way will also
take a huge loa
Carl gave you the correct answer. I'll just add that his way will also take a
huge load off your server. What you are doing now is accepting the whole
message...then sending an entire new message for the NDR.
His way your server tells the sending server during the initial SMTP
conversation that
I'm not so sure. Everything I do shows a complete subject line being submitted
to the Exchange MBX store but only a truncated version being available for
retrieval no matter what client or method I use.
Carl Rimmel
Senior Engineer, HFHS Messaging
Email: carl.rim...@hfhs.org
Desk: 248-853-3620
I do have tarpitting enabled, and it helped a bit. But my Antispam
solution is signature based. I have considered implementing SPF
solutions, but many of our clients have domains that don't comply, so
that would cause more trouble.
Bill
From: Mayo, Bill [mailto:bem...@pittcountync.gov]
S
Couldn't agree with you more but the developers are unwilling to change to pure
ASCII because the change would affect other reports that require UTF-8.
We all agree that this is a ridiculous subject line but the Peoplesoft
developers refuse to alter this because "all other email programs are wor
Enable recipient filtering and tick the box for "filter recipients who are
not in the directory". That will eliminate all of the NDRs from spam sent
to non-existent addresses.
The senders who make a typo will still get NDRs, but those NDRs will be
generated by the sending servers instead of y
Inspecting the logs reveals that the message is delivered to the MBX server in
its entirety - subject line fully intact. But, when you try to retrieve it you
get a truncated subject line. It appears that Exchange stores the message with
a 255 character limit imposed.
I have tried 2 different
You can use "tarpitting" to help foil the spammers sending to
non-existent addresses, and that may help some. However, I humbly
suggest that you need an anti-spam solution that handles this. Like
you, my queue used to be monopolized by attempted NDRs to non-existent
domains. Since implementing a
Okay, backscatter is an annoyance at the very least. So I want to do
something about it. My messaging queue is 90% NDRs to domains and
subdomains with no MX records.
Of course the easy solution is to just uncheck "allow Non-Delivery
reports" in Internet Messaging formats within ESM. But my
Sorry, been busy getting ready for Y2K
-Original Message-
From: Ben Scott [mailto:mailvor...@gmail.com]
Sent: Wednesday, August 19, 2009 9:03 AM
To: MS-Exchange Admin Issues
Subject: Re: Changing Subject Line Limits
That thread's a month old. Are you trapped in a time warp or somet
That thread's a month old. Are you trapped in a time warp or something? ;-)
On Wed, Aug 19, 2009 at 11:30 AM, Rimmel, Carl wrote:
> I couldn't agree with you more. Regardless, it appears that Yahoo and others
> have no issue with these same subject lines - it's just Exchange\Outlook that
>
I couldn't agree with you more. Regardless, it appears that Yahoo and others
have no issue with these same subject lines - it's just Exchange\Outlook that
do.
Carl Rimmel
-Original Message-
From: Micheal Espinola Jr [mailto:michealespin...@gmail.com]
Sent: Tuesday, July 14, 2009 11:3
Hello all,
We want to move to Exchange 2007 in a few months. Currently we are running a
postfix server as primary mail server.
Needless to say that shared calendars and so are not possible :-)
Exchange and Groupwise where the two system we looked into. Groupwise
because we are running a Novell cor
Are you using an ISA server?
-Original Message-
From: Steven Peck [mailto:sep...@gmail.com]
Sent: Tuesday, August 18, 2009 6:49 PM
To: MS-Exchange Admin Issues
Subject: Re: Microsoft Exchange ActiveSync Mobile Administration Web Tool
install
We just turned on the ActiveSync. Enabled t
33 matches
Mail list logo
