(no subject)

[justsomegurl.livejournal.com]

I could scream! I transfered a call to our "NOC" department. I have been specifically instructed not to trouble-shoot any calls that come in from our domain customers. Instead of realizing that it is not my job to check the mailbox, my co-worker sends me this degrading message. It is hush-hush at the moment, but he is rumored to be losing his job soon along with the rest of our "business office". I can't wait.

Getting email with 20mb attachments tend to do that *laugh*. As for the account beig pop-locked, I've repeatedly stated using the web interface to check an account when the spool is too big will generate a pop-lock, that is why I always recommend instead to telnet in on port 110. Here's a link to a tutorial on this.

telnet://mail.villageofwestbaraboo.us:110
http://pages.prodigy.net/michael_santovec/pop3telnet.htm

I'll give *** a call, assuming it's the same phone number in ISIS, and see if she wants the message removed.

Thanks!

Comments

[buckaction.livejournal.com]

i'm surprised that your company doesn't have a "fix pop lock" tool scripted up to automate such nonsense.

When i had to deal with that sort of thing manually years ago, I didn't give the customer a choice about what they could keep and what they would lose as far as mail was concerned - they were told to either telnet in and manually delete some messages themselves (our service was a shell server - *most* of our customers knew how to use a shell), and if they didn't want to, or didn't know how to do that - they either lived with having their mailbox being inaccessible due to the poplock, or, i deleted the entire contents of the box for them.