You can't. The spam detection is done at the client end, using rules the client has set up. For example, my spam filter is set to detect anything which contains "$$$" or the word "Rolex". If a Codeproject email arrived with those in, it would be treated as spam.
The best you can do it send actually useful information, and hope that the client adds you to the non-spam list himself. If you "send lots of email" to people though, there is an increasing chance that you will go straight onto the spam list - you would with me.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Manfred R. Bihy: "Looks as if OP is learning resistant."
As you said I khow that don't send emails fast and at this moment in my site I send some email and afterward send again but I want to sent lots of them at once I'm sure it has another solution so do you have any solution?
I have a web page that invokes a web service methods to get records displayed on the web page. What happens if two website users vistit the web page at the same time. Two simultaneous requests will be sent to the web service. Should a mechanism be used to enforce exclusive invokation of the web service ?
Currently no such mechanism is used in the web page and some times timeout error generated when invoking the web service. I doubt such error is caused by lack of mutal exclusion support when invoking web service.
What is the best practice when implementing the web page in question ?
when two separate webpages perform a request to the server either by calling a webservice or some other request medium, you have no control over what happens once a request is sent to the server. It is two different REQUESTS transmitted in TWO different REQUEST CHANNELS, IIS on your server will manage all of this for you.
Your server will respond to these two requests separately and simultaneously. Remember that both your clients are important so you don't want to serve one client and deny the other, the only way to resolve this is to make your server a much faster machine.
I can imagine that one day your site will be "live" and 1000+ people will make requests to the webservice at the same time! implementing a mechanism to control which request is served first is really something done by IIS(internet Information Service) and you shouldn't bother, you will kill yourself.
Thanks for reply.
Maybe I couldn't explain well. The web page in the website invokes a remote web sevice. When two users visit the same web page it means two simultaneous requests are made to the web service both of which are originated from the same Ip address. The matter is they are from the same Ip address. I doubt wether the web service can handle that or a machanism must be used in web page. Or maybe the server can be cofigured to allow such simultanous requests or not ?
Last Visit: 31-Dec-99 19:00 Last Update: 3-Dec-21 13:11