Database Maintenance on MF1 and MF2
by Ken ForstromWe need to run a database check on MF1 and MF2 today. This may cause some messages to be delayed, but no mail will be lost.
We will post again when this is completed.
Categories
- General (107)
- Service Status (57)
- Spamfighters Podcast (11)
Feeds
Full feed for this blog
Feed of only the system status related messages
Archives
Tag Cloud
account-manager add-in Add new tag antispam aol api backup beta billing bounce branding catch-all catch-alls changes complete coupon delays digest discount dns domainprotect downtime easy-antispam edge fixed g1 gateway George-Roberts happy holidays holiday-hours hostingcon infrastructure Interjuncture interop interview issue jobs las-vegas live mf1 mf2 new-features new engine news new services outage outlook overage party phone-support planned-outage plans power problem protectedmail pubcon quarantine RBL recovered report reports resolved scheduled-maintenance security Security News sender-verify-callout service SORBS spam-levels spamfighters Spamfighters Podcast status-normal support tagging toolbar tradeshow unscheduled-maintenance UserProtect user protect whitelistsOptions
|
Contact Us Purity Networks, Inc.1651 Linden Park Ln Aurora, IL 60504 Toll-free: 1-888-NOSPAM-9 (1-888-667-7269) Direct: +1 815 893-7285 Fax: +1 815 425-2446 Send us a message |
How We Can Help Antispam Service· Features & Benefits · Quick & Easy Setup · Packages & Pricing Antispam Appliances · Features & Models · Information Request |
Connect With Us  Facebook Twitter LinkedIn Blog Feed
|
March 19th, 2008 at 9:23 am
Why in the world are you running these checks in the middle of a business day? I like your service overall, but I don’t think you take these repeated delays seriously enough. It matters a LOT to businesses when messages are delayed for hours and hours (which has become a regular occurance here).
Do your maintenance at 3AM on a weekend like everyone else does.
March 19th, 2008 at 9:28 am
Joe,
I appreciate your position, but the delays are being caused by a glitch in the database.
So, we could allow it to go unchecked for the remainder of the day, and let the database become corrupted to the point of a complete shutdown, or we could run the check now, and be done before lunch, aleviating further delays.