Messaging Gateway

 View Only
  • 1.  Spam Quarantine: AD integration query

    Posted Jun 09, 2010 11:14 PM

    I have a client and for multiple reasons they use a seconday email address attribute for all of their AD users.
    All email is sent to and from the secondary address and the primary address just exists as it is created when the user is generated.

    AD username: joe bloggs
    primary email addres: joe.bloggs@test.domain
    secondaryemail address: joe.bloggs@secondtest.domain

    When a spam message is sent to joe.bloggs@secondtest.domain and detected it is sent to spam quarantine ok!
    But the TO: address listed in the spam quarantine is the joe.bloggs@test.domain and the subsequent spam notification goes back to their primary email address.

    The start of the spam notification email also states - Quarantine Summary for joe.bloggs@test.domain

    Shouldn't the notification be sent back to the email address the spam was addressed to?
    Am I missing something here?

    thanks

    Z



  • 2.  RE: Spam Quarantine: AD integration query

    Posted Jun 11, 2010 05:12 AM

    Hi Zero,

    What you are seeing is by design.  When a message is determined to be spam and the action is to quarantine the message, the SBG then checks the recipients email address, resolves that email address to the primary email address of a user, then inserts the message into quarantine.  We do this to make sure messages for a recipient and all their alias addresses get stored in one central location for the user.

    We then send the notification to the primary email address, but we do show the spam messages that had been sent to the primary address and all aliases.

    When a user then logs into the quaratine to check their quarantined spam messages we effectively then run a query to show all spam messages associated to the users primary email address which guarantees we will then display all the quarantined messages for a user.

    I guess if you think about a scenario where a user could have about 20 or more aliases, it would make it very innefficient if when a user logged in we had to run a bunch of queries related to each alias address to succesfully display all of the messages in quarantine for the user.

    So basically that's the reason why we do it as we do it.

    One thing I would say, if when in the quarantine you can actually check the headers of the message you can see the original address(if it was an alias) that a message was sent to if an end user really wants to see the exact address the message was sent to.

    Hope that sorts you out.

    Kevin