Shachar Shemesh wrote:
Jonathan Ben Avraham wrote:
What should we do next?
Oh, and I almost forgot.
When you talk to tech support, if after 10 minutes on the line you
realize that the rep will not or cannot help you, ask for a supervisor.
In most cases, if the rep cannot help you, the super cannot either, but
he is more equipped to direct you to the part of the company that can.
A few useful emails:
[EMAIL PROTECTED] - if you can frame the request is any way you turn it
as "an attack", that's a good address. They usually understand more
about the infra than the reps. Examples from my recent history - an ISP
has a local zone file for a client's domain, which contains the wrong
IP. Rep tries to tell me that since I am not their client, they cannot
help me. I tell him that what they are effectively doing is a denial of
service for my site. Abuse were not the right address in this case, but
they knew which was (the next one).
hostmaster@ - I know, the time we used to read the RFCs that said that
every machine should have an active hostmaster account receiving email,
and that every SMTP server must have a postmaster@ address. It seems
that these days are gone and no one remembers them, but most ISPs
actually honor these RFCs. If it's a configuration problem, hostmaster@
should be contacted.
Shachar
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
