Feedback by UserVoice

Povl H. Pedersen

My feedback

  1. 31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Povl H. Pedersen commented  · 

    policy=reject MUST be handled as per RFC. REJECT the mail.
    As it is now, I can not test my SPF/DMARC records against O365, and company users using shady mailservers do not get the same experience as most end-users by the failure to implement the RFC correct.
    Please handle DMARC policy=reject as per RFC
    And please add support for sending RUA reports. Not that critical though.
    As a help to others, Get-PhishFilterPolicy will return domains sending spoofed mails to your tennant (dmarc fail)

    Povl H. Pedersen supported this idea  · 
  2. 3,492 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Povl H. Pedersen commented  · 

    Please connect to the real world. We need reporting.
    Especially since O365 does treat reject as quarantine, and allows users to whitelist senders, thus allowing users a complete override. We need to know how big the problem is.

  3. 275 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Povl H. Pedersen commented  · 

    Allow this or regex.
    eDiscovery searching today is way too limited.
    Having to export all mails to flat files, and using Powershell / bash to search is way too complicated. Enterprise customers are not stupid. They can write RegEx or get assistance from someone who can.

  4. 246 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  Office 365 Security & Compliance » Reports  ·  Flag idea as inappropriate…  ·  Admin →

    1. Click into “details”.
    2. Choose “connector report”.
    3. Choose “request report”.
    4. Answer the questions in the wizard, clicking “Next”, “Next”, and “Save”.
    5. Wait for the report to come to the email address specified. It will contain the following fields:
    message_id, direction, sender_address, recipient_address, connector_name, connector_type, tls_version, tls_cipher

    With the Message_Id value, you can combine this with MessageTrace to get the Subject.

    If this does not help, please provide more information as to the scenario and detail that is missing. Thank you for the feedback!

    An error occurred while saving the comment
    Povl H. Pedersen commented  · 

    We need this as well.
    At least for outbound we need a list of recipient domain names, such that we can either make excemptions up front, or contact them.
    It is an official legal GDPR requirement to use TLS from January 1st 2019 here in Denmark on all mails containing personal data. So we need to make the step. Right now we have no clue of the impact to business.

Feedback and Knowledge Base