lunedì 18 aprile 2011 18:42
I'm currently assessing FOPE as a replacement for our current on-premise SPAM filtering appliance. In particular, I think the ability to do away with digest emails and route spam to the junk-email folder is pretty compelling. I'm hoping someone can give me more info on this, though:
- If I'm using the on-premise quarantine feature, do I need to have FPE installed locally?
- Is it possible to establish a threshold for what messages to pass along? In other words, can I disregard the really obnoxious stuff, but quarantine the usual newsletters and such?
- Is it possible to convert SPAM to plaintext before quarantining it?
- Are local outlook whitelists/blacklists synchronized to FOPE?
Thanks for your help!
Tutte le risposte
lunedì 18 aprile 2011 23:07Moderatore
I'm guessing that for question 1 you meant the Junk E-mail feature in outlook for "on-premise quarantine". This is done with Exchange transport rules and doesn't require FPE to be installed.
For question 2, there isn’t a configurable threshold, if FOPE determines the message to be spam; it will add the x-header.
Assuming Junk E-mail feature in Outlook for question 3, Outlook restricts messages that are in the Junk E-mail folder to prevent links and images from being viewed.
Unfortunately, no, for question 4, if you want to whitelist or blacklist in FOPE, you'll have to manually create policy rules in FOPE.
Kemper - MSFT
- Contrassegnato come risposta Kemper - MSFTMicrosoft Employee, Moderator lunedì 18 aprile 2011 23:07
mercoledì 1 giugno 2011 21:57
Your instruction we a bit too vague for me.
I've setup FOPE; and am routing all email to my Exchange 2007 CAS/MBX/X-Port server.
In my message that are known spam there are several X-Headers added by FOPE:
X-CustomSpam: This message was filtered by custom spam filter option - From SPF error
Received-SPF: error (temporary) (mail57-am1: encountered temporary error during SPF processing of domain of domain.com) client-ip=xxxxx; firstname.lastname@example.org; helo=domain.com ;main.com;
I even have a custom X-Header of X-DOMAIN-SPAM, but I don't see that show up anywhere.
When I try to establish a Transport Rule it wants me to define the message header, and the message header value in the 'condition'. In which case I would gladly have all X-SpamScore equal to <anything> set the SCL to value of X-SpamScore; but how do I do that?
Directory of Technology
venerdì 9 marzo 2012 05:45
Actually I have a workaround. Instead of forcing FOPE to inject a X-Header we can change the SPAM Action to Modify Subject and mention the word [Detected SPAM] in the subject line.
Now on the On-premise Exchange Server create a Transport Rule stating that any email having the word [Detected SPAM] in the subject line should be rated with SCL value as 5.
Any email which has got the SCL rating between 4-6 is been delivered to Junk email folder. This threshold can be changed on the On-premise Server.
So I think that might help you out and even easy to identify the emails which are been marked as SPAM by FOPE and deloiver them to the Junk email folder in Outlook/ OWA.
giovedì 6 dicembre 2012 16:45
Correction - you can sync whitelists if using safelist aggregation on Exchange and FOPE's Directory synchronization tool. This will pull the users white list from Outlook 2007 and 2010 in to AD and then push to FOPE via the DST. This DOES not sync blackliststhose are handled locally by the outlook client.
NOTE - Exchange 2010 by default runs safelist aggregation. You must schedule the EMS command to run safelist aggregation in Exchange 2007 or just run it manually.
venerdì 7 dicembre 2012 14:44
The bit that is missing from the earlier answer is the value of the header in addition to the name of the header. You can set the header name to anything you like (i.e. X-Detected-Spam) but the value of the header will always be "This message appears to be spam.". Therefore you can write a transport rule in Exchange that increases the SCL for all emails that contain the header X-Detected-Spam with the value "This message appears to be spam.". Then users process their probable spam in Outlook rather than in a quarantine, and without having modified the original message subject.
I cover this more on http://blog.c7solutions.com/2012/12/forefront-online-protection-for.html as I found when I was looking for the name and value of the header yesterday it was not documented completely anywhere online.
Brian Reid - Exchange MCM
Brian Reid C7 Solutions Ltd (www.c7solutions.com)
- Proposto come risposta BrianReid-MCM venerdì 7 dicembre 2012 14:44
lunedì 10 dicembre 2012 14:47
ask to ms fope team a DCR for accept the user receive spam for he can add domain spams in white list .
some good new like new designe in fope V15 J and after ms tell me is a joke the DCR and they have rejected LNÿÿÿ
The DCR has now been reviewed and is set to be considered for the first service release of FOPE v15.
FYI, the current FOPE version is 14 and within the coming months (under 4, I anticipate) we will move to v15. After that, a service release will be planned, but I do now have any dates for you. At this point, the DCR will be considered for implementation. The good news is that it has not been immediately rejected J.
I have now taken this support case as far as I can. We have submitted the DCR, which will be considered for a future release, as above. I would therefore ask you to approve closure of this case. Please let me know if you have any further questions.
Can you give me an official roadmap about fope 15 .
I’m afraid I don’t know of any roadmap or official release date for FOPE 15, however I am sure that it is to be released within the first 6 months of next year.
If you don t have rodmap for fope 15 .
Can you give me another solution.
We have no other solution. It is why we have request this change of design to the developpement team.
Can we have a official mail that speak the user fope can add domain spams in white list in FOPE 15 .
The request was for a Design Change Request, which has been created and processed. We cannot provide any statement like this. As I mentioned before, the DCR will be considered for the first Service Release (like a Service Pack) of FOPE 15. There is no chance of any change being implemented in the initial FOPE 15 release.
- Modificato cambier lunedì 10 dicembre 2012 14:47