The server had a hiccup today and became fairly unstable, but we should be back to normal now and I learned some valuable lessons to avoid this type of problem in the future.
Live and learn!
Cheers,
Seraph0x
Well, if you're interested, here goes:Foxhawke wrote:You don't want to share your lessons? :)
Code: Select all
function cut_at_word($text, $len) {
$text = str_replace('<br />', ' ', $text);
$text = preg_replace('/\<.*?\>/', '', $text);
if(strlen($text) <= $len) return $text;
$i = $len;
while(substr($text, $i, 1) != ' ') {
$i--;
}
return substr($text, 0, $i).'...';
}

Hehe, that's a classic.seraph0x wrote:Anybody see anything wrong with that code?

Aww, such a tease!seraph0x wrote:Everyone else: Don't worry, I'm not about to turn Milovana into a blog about programming.
hahaha damn i bet that hurt when he got back!After two days, 250,000 emails have passed the spamfilter, and 620,000 emails were still in queue.
Doesn't work nearly as well anymore. Mailservers are much better at handling large amounts of emails suddenly appearing and will usually discard them and blacklist the sender (the server, not the email) for a while (a few hours to a few days or more). In this day and age when spam is such a rampart problem these things doesn't work nearly as well as they used to five or ten years ago.omssx wrote:Good way to disrupt a mail server though! Ill remember that ;)