Re: Legitimate Messages Reaching Junk Folder
- From: "Diane Poremsky [MVP]" <outlookmvp@xxxxxxx>
- Date: Tue, 6 Oct 2009 16:31:09 -0400
Did users add the address to their safe list? What is the SCL on these messages? How short are the messages?
Is Outlook the culprit? In Outlook 1007 SP2, when messages are in the junk folder, it will say if outlook's spam filter or something else did it (but not what that something else is).
--
Diane Poremsky [MVP - Outlook]
Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com/
Outlook Tips by email:
mailto:dailytips-subscribe-request@xxxxxxxxxxxxxxxxxxxxx
EMO - a weekly newsletter about Outlook and Exchange:
mailto:EMO-NEWSLETTER-SUBSCRIBE-REQUEST@xxxxxxxxxxxxxxxxxxxx
Do you keep Outlook open 24/7? Vote in our poll:
http://forums.slipstick.com/showthread.php?t=22205
"mcintoshs" <mcintoshs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:557A3B76-5573-4C63-9E66-2E035D3903E9@xxxxxxxxxxxxxxxx
This is a cross-post from the Outlook discussion group..
mcintoshs wrote:We have an emergency notification web service called AlertNow which notifies
parents and internal staff within our school district of emergencies.
Administrators from our school district compose and send the messages within
the external AlertNow web servers and then the message is sent to parents'
addresses outside the district and to selected individuals within the
District.
Regardless of where the message is sent from the AlertNow email
servers, the 'From' address is from our internal mail domain (I will call it
school1.org). Since such emails coming back into our district appear to be
'spoofed,' we had to configure special 'IP Lock' settings within our
Google-Postini spam filtering service to allow such messages to be deivered.
Now, however, we are finding that users with Outlook03 and 07 are seeing
such messages go to their 'Junk folder.' Is there a setting within our
Exchange Server 03 Enterprise SP2 which can eliminate this behavior? For
example, all such messages have a 'from' address of 'noreply@xxxxxxxxxxxx' We
need to circumvent whatever spoofing settings may currently exist in the
Exchange server configuration.
"VanguardLH" wrote:
mcintoshs replied:
When the domain in the return-path headers (e.g., From) don't match the
source Received header, that e-mail looks to be spoofed by some filters.
It is not invalid to use return-path headers pointing at a different
domain than from where the e-mail originated, like when using Reply-To,
but some filters will up the scoring on those e-mails, and that score
could approach and exceed the ham/spam threshold.
Are ALL the recipients using the same mail server as you? Or are they
off-domain and using their own SMTP servers to which your Exchange
server is transferring your message? You mention Exchange but then you
also mention Google. Are all recipients insiders to your Exchange
domain or are there outsiders getting your alerts? I've never
administered an Exchange server so I'm only looking at your problem from
the client end. If every recipient is using the same Exchange server
(or the same organization of Exchange servers), a group that discusses
Exchange rather than the client might offer more help, like the
microsoft.public.exchange.* groups.
Is there a reason that the recipients cannot whitelist your e-mails?
Seems they could add you to their Safe Senders list, or enable the
option in Safe Senders to include contacts in their address book, or
define a whitelist rule that checks if the sender is listed in that rule
or the rule checks against contacts in the address books (where they
would add you to their address book). This assumes your e-mail actually
arrives to their mailbox (which would seem true for it to end up in the
Junk folder).
Our Exchange server is only receiving and delivering messages to our
internal administrator users once received from the AlertNow email server via
the Postini mail servers which shows our own internal domain as the 'From'
address. Other external recipients don't seem to experience this issue
because messages from the AlertNow server go via their individual ISP's mail
servers and are not seen as spoofed.
We have many internal users and many of them are very technically unsavvy
and I don't want to inconvenience them with making whitelist configuration
changes within Outlook folders.
- References:
- Legitimate Messages Reaching Junk Folder
- From: mcintoshs
- Legitimate Messages Reaching Junk Folder
- Prev by Date: Re: Mailbox size 18+ gb
- Next by Date: Quick and dirty recovery network
- Previous by thread: Legitimate Messages Reaching Junk Folder
- Next by thread: free/busy time
- Index(es):
Relevant Pages
|
