Forum Discussion

Spidey_29396's avatar
Spidey_29396
Icon for Nimbostratus rankNimbostratus
Oct 06, 2013

Is there a way for a single request to be received by all pool members

we are setting up an anti-spam server farm and to be load balanced by F5, but to determine that the mail is valid, there is a Radius AVP that is to be received by all anti-spam servers. In this case, we might need a Virtual server that all pool members shall receive the Raduis AVP. Is this possible?

 

18 Replies

  • Hi Kevin,

     

    actually we only need client's email to go to the same (single) anti-spam server that received the AVP message. But as Sam said, this was not yet tested.Would you recommend to have just universal persistence instead of using HSL??

     

    Thanks! Ferdz

     

  • The HSL method (and sideband method for that matter) would certainly get the AVP message to all of the servers, but that definitely seems like a lot of unnecessary overhead (sending AVP messages to servers that will never see the client traffic). The alternative would probably be some form of persistence. The question then is, what's in the AVP message that could be tied back to the client? Since the GGSN is actually sending the first message and the client is sending the second, is there something in the payload that can be used to correlate the two?

     

  • Hi Kevin,

     

    They are using USer-name to identify valid e-mails.

     

    Thanks! Ferdz

     

  • Ferdz, what you're asking for is not a simple thing to do. In order to assist we need MUCH more information. You have basically two options:

     

    1. Capture the AVP request from GGSN and relay it to all of the anti-spam servers, most reasonably using a sideband call.

       

    2. If there's a way to correlate the AVP message to the email message, you could potentially send the AVP to one anti-spam server, create a persistence record, and then send the email request to the same anti-spam server. For this option you must provide more detail and if there is some correlation between the two messages, preferably something in the request data that is unique and pervasive.