<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Died big time.
>
> This is the first time that they have ever admitted that mail might be
> lost.
>
> Perhaps some of the experts could comment on what this tells us about
> the resiliency of the Pipex system.
>
> Seems dodgy to me.
>
> MJK
Don't be too harsh with them unless it's a regular occurance. Sometimes
things just don't go to plan.
Imagine this: Some little bastards in a far away country are nailing the
mail server because they found a formail.cgi exploit on a customers website
which you host. The server is used for both sending and receiving mail, but
because the server's on it's knees trying to cope with all this outgoing
mail, it's too busy to accept the incoming mail. Effectively, it's having a
fit and can't do anything.
Meanwhile, customers are ringing up left right and center totally irate
about not being able to get any email.
The system administrators are pulling their hair out because they know how
pissed the customers are AND that their network isn't running smoothly (most
important factor ;o). In order to fix the problem, the offending formail.cgi
script has to be found and patched but that wont help the mail server which
has locked up by now. The mail server gets restarted but there are still
many thousand messages in the queue, within the queue might be genuine
emails from customers but to fix the problem, the queue must be purged -
customers lose mail.
Just when the admin thinks he's in the clear, he hears the distant barrage
of more irate customers yelling about how their emails aren't being sent.
Okay, I know this (probably) isn't what happend with Pipex, but it hopefully
shows that sometimes it isn't always their fault.
However, I do think ISP's should be honest wth their customers, if there's a
problem tell them what it is and when it should be fixed.
|
Similar Threads
Linear Mode
