Mathematical Auditing Of Email Broadcasts

  • Comments posted to this topic are about the item Mathematical Auditing Of Email Broadcasts

    R Glen Cooper

  • ...are you working for http://www.wolframalpha.com/ !!!

    ============================================================
    SELECT YOUR PROBLEM FROM SSC.com WHERE PROBLEM DESCRIPTION =
    http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]

  • Phew........I didn't get the article ! ! ! May be I am week at Mathematical analytical.

    SQL DBA.

  • Very well done.

    A great example of practical math and DB tools.

  • Very interesting approach!

    I'm not quite clear on the final practical step though-- do you avoid the multiple messages and circular references by making the person doing the mailing manually clean up their list, or could you solve the problem by resolving all distribution lists to their "final" addresses and selecting the distinct address?

    Brian

  • Thank you for the kind replies.

    This work was motivated by a problem I had with a marketing company in Vancouver, where the database administrator was frequently interrupted by requests to fix their broadcasts. Although there weren't a lot of errors given the size of the weekly mailouts, each one was a serious annoyance that consumed a lot of time.

    It took a while before I realized that their problems were simply anomalies in directed graphs, which made things easier to visualize.

    But for really large graphs, we might need a more efficient way to process them.

    R Glen Cooper

  • Good question.

    Nothing automatic is done to resolve the issues, so that's worth investigating.

    R Glen Cooper

  • Awesome article and very interesting.

    But it seems a simpler way of dealing with your problem is to change your e-mail broadcast system internally. Instead of the broadcast system every broadcasing to a list, have it expand all lists and remove all duplicates at the time it is sent. That way a broadcast list never receives anything from another internal broadcast list and no person ever receives a message twice. Am I missing something?

    ---
    Timothy A Wiseman
    SQL Blog: http://timothyawiseman.wordpress.com/

  • That's an interesting reply.

    I should have made a subtle distinction between mailing lists and re-directions. Although the latter may be viewed as a special case of the former, you can't delete someone's re-direction on the email server just because it causes conflicts elsewhere.

    Suppose we have one broadcast submitted by Arnold:

    A --> b

    A --> c

    and two re-directions submitted individually by Bob and Calvin (which you can't delete because these people don't want ANY emails):

    b --> A

    c --> b

    Althoug A is a valid email address, it's meant to represent a mailing list (eg. customers@myCompany.com) while b, c are real people (eg. Bob@myCompany.com).

    There are no duplicates in this list, but both circularity and redundancy exist.

    We could remove the second re-direction, but then Calvin would start getting emails.

    If we expand mailing lists on the right hand side, we would get:

    A --> b

    A --> c

    b --> b

    b --> c

    c --> b

    Eliminating self re-directions gets us:

    A --> b

    A --> c

    b --> c

    c --> b

    Since we can't eliminate the last re-direction submitted individually by Calvin, how do we get rid of the duplicates on the right hand side? We could eliminate b --> c, but then Bob's now getting emails.

    Already my head's spinning.

    You may be correct in your approach, but it looks a bit messy (to me, anyway).

    That's why I viewed these things as graphs, where mailing lists and re-directions are the same thing.

    R Glen Cooper

  • Yes, that makes sense in that situation. If redirection, and not simply mailing lists that need to be expanded, then you could wind up with a circular reference like that that would be awkward and with no clean way to resolve it automatically.

    ---
    Timothy A Wiseman
    SQL Blog: http://timothyawiseman.wordpress.com/

  • Hello,

    Since this article is as interessing and usefull as "Ordering Tables To Preserve Referential Integrity" article, I ask the same question that I asked for the "Ordering Tables To Preserve Referential Integrity" article :

    would it be possible to have the same script for sql server 2000 ? Badly I am not able to do the transformation (there is no Common Table Expressions in sql2000).

    Thank you very much.

  • Thank you for the reply.

    I can do this, but it will take a couple of weeks before I can get to it.

    I will reply when it's done.

    Glen Cooper

    R Glen Cooper

  • Thank you very much !!!

    Best regards

  • I love this article. DAGs seem to show up everywhere. I used them in a gene assembly program I wrote.

    I am now working on groom email lists and this article is worth it's weight in platinum to me.

    I do see a challange though. The redirects may not occur in an email system you have access to. If you send a broadcast to a group of customers, you will not see the redirects because they occur in the customer's email system.

    At my former employer, when an employee quit, we made a redirect from the salesperson's mailbox to the sales manager's mailbox. When the sales manager quit, the redirect went to his boss.

    So the question is how to track the redirects from the marketing communications company. I do not think you can.

    I still loved the article though.

    Nick Stein

    nstein@bizcad.com

  • Hi Nick,

    Thank you for your response.

    You are correct in that we have no way to see redirects in other email systems, so redirections from them to your own are possible.

    I assume that your salesperson, sales manager, and his boss are using the same system so there shouldn't be an problem here (unless I'm confused about what you meant).

    Glen

    R Glen Cooper

Viewing 15 posts - 1 through 15 (of 16 total)

You must be logged in to reply to this topic. Login to reply