Submitted by sam on Wed, 06/21/2006 - 14:46.
Okay, due to some stupid crap on my end (GAH! I misconfigured Postfix!) ClanAM.org has not been sending password requests for a while (a couple of weeks). What does this mean? This means that they have been queing up for a couple of weeks.
Well, I fixed it this morning, and suddenly it started delivering. There's SO MUCH to deliver in fact, that it nearly took my server down (yay! I DoS'ed myself!).
Anyway, if you get a password reminder delivered from this site, and I've already fixed your account previously, just ignore it. And I'm sorry about the trouble.
![[ Home ]](http://ffxi.clanam.org/themes/clanam/images/home-off.png)
![[ Archives ]](http://ffxi.clanam.org/themes/clanam/images/archives-off.png)
![[ Blogs ]](http://ffxi.clanam.org/themes/clanam/images/blogs-off.png)
![[ Guides ]](http://ffxi.clanam.org/themes/clanam/images/guides-off.png)
![[ Forums ]](http://ffxi.clanam.org/themes/clanam/images/forums-off.png)
![[ Image Galleries ]](http://ffxi.clanam.org/themes/clanam/images/image-off.png)
![[ Older Polls ]](http://ffxi.clanam.org/themes/clanam/images/polls-off.png)
![[ Advanced Search ]](http://ffxi.clanam.org/themes/clanam/images/barsearch-off.png)
![[ My Account ]](http://ffxi.clanam.org/themes/clanam/images/my_account-off.png)
Worst is over
Okay, as of "Wed Jun 21 11:36:56 EDT 2006" the worst seems over. The server is responsive again, and the mail queue is sitting squarely at zero.
Sorry for the problems, everyone :-)
Vis Maior's Journeys
http://maior.samhart.net/
YAAAAAAAAAAAAAAA
D DoS ATTACKS RULZ! :P
Yeah...
If you're a nub-ass script kiddie, who becomes leetz hax0rz by either a) visiting stupid hax0rz sites, or b) purchases a stupid "how to hax0rz" book.
DoS is the equivalent of a whiney kid, crying for hours until either folks begin to ignore his ass or folks just give up and give him what he wants.
How would a self-inflicted DoS attack be categorized? Possibily as a /emo kid?
Awesome work Sam.
Self-inflicted DoS
1) Have a dual server mail system for load balancing.
2) Have your mail delivery server get attacked.
3) Tighten up your SMTPD rules for sender/recipient restrictions.
4) Fail to add one (maybe either will work, didn't check this) server to your permitted networks.
5) Forget about it and let it churn for a few weeks (yay! backlogged messages as one server says "No, no, no, this mail is for you!" and the other replies "Nonesense! I don't know you! Get the fuck away from me!")
6) Realize the mistake through diagnosing a silly side-effect (messages from Drupal sites stop being delivered) and fix it.
7) Viola! Umpteenbillion queued messages get crammed through the pipes at once!
BTW, it also didn't help that as I flushed the Postfix queue I was checking/fixing my Drupal databases.
Vis Maior's Journeys
http://maior.samhart.net/
nice
nice XD