Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 10 replies
  • Subscribers 0 subscribers
  • Views 30648 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

PureMessage Blocking Valid Message, "Invalid Recipients"

mbjoe

Sophos is blocking a valid inbout email but only blocking it for some recipients, in the Acvitiy Monitor only we see the error: Blocked Message '<---@domain>' for invalid recipients 'example@.com....'

When looking at who should be receiving the email, the first seven recipients receive the email ok, but after that everyone else is blocked.

The message does not get quarantined and does not appear in any other Sophos log. It does however appear in the Exchange Message Tracking log with an error of FAIL and pme12transport.

:9869


This thread was automatically locked due to age.
  • 0

    I found that the reason the emails are being blocked is due to the Recipient Validation setting. Disabling this option allows the emails to be sent through.... but it still doesn't explain why it is blocking it in the first place.

    For example, the user sends to: A@Domain.com, B@Domain.com, C@Domain.com and D@Domain.com

    The email to A@Domain.com will go through OK, but then the other three will be blocked and show in Activity Monitor with:

    Blocked Message <Message ID> for invalid recipients 'B@Domain.com, C@Domain.com, D@Domain.com'

    Another odd thing is that whenever the user adds/removed an address to the list of people being emailed, the number of those who receive it changes.

    The first email was sent to 18 people, 3 received it and 15 were blocked.

    The second email was sent to 19 people, 4 received it and 15 were blocked.

    The third email was sent to 22 people, 7 received it and 15 were blocked.

    It seems like 15 messages always get blocked with the "Blocked Message" while the rest go through. I'm so confused as to why this is happening. I would rather not disable the Validation Filter but that is all that seems to be fixing it.

    :9923
  • 0

    HI Mbjoe

    Usually if recipient Validation is rejecting emails its related to incomplete routing.

    I've found if there is a pop3 connector on the mahcine the domain.local needs to be added into the routing domains list,

    Else the local ip address needs to be added into the list.

    This could aswell apply if the users email address was created differently to the others, which might be the reason for allowing the email to some and not all.

    Good luck.

    :)

    :10057
  • 0

    I ended up talking to tech support to find a solution, but it is a known bug in PureMessage that they hope to fix with the next update.

    The problem occurs when sending/receiving a message with 15 or more recipients. We noticed that each time a message was sent with more then 15, the last 15 recipients would not receive the message while the rest would. So if you sent to 20 people, the first 5 would recieve the email and the last 15 wouldn't. If you send to 21, the first 6 would receive the message and the remaining 15 wouldn't.

    So tech support basically said we had to turn off the Validation Filter until the update is released.

    :10077
  • 0

    Hi Mbjoe

    Good to know - Thanks for the update

    Enjoy your day.

    :10079
  • 0

    Hey guys,

    is there already an update?

    :11581
  • 0

    When I spoke to tech support a few weeks ago about the problem they said the next update isn't scheduled until June.

    :11583
  • 0

    great...

    thank you for your reply!

    :11585
  • 0

    I am having this problem too. It's way past June now. Does anyone know when an update will be available to fix this issue?

    Thanks!

    :17183
  • 0

    We currently have a team working on a maintenance release for Puremessage for Exchange, which will be 3.1.1.  We hope to have this available to our customers early 2012, pending successful QA tests.

    This specific item is tracked internally as DEF66465 , and the fix is planned to be in 3.1.1.

    :17185
  • 0

    I take it that QA tests didn't go so well, since it is now April and still no update. Do we have any more information on a timetable for the update?

    Seems rediculous that it is taking so long.

    :23389
Unfiltered HTML