On 04/30/2013 12:13 PM, Ken Dibble wrote:
I know when an account goes over quota, when a user informs me his
account isn't working, and I check his quota status, and see its over
limit. I then ask the user to clean up his emails to free up disk
space, or in some situations, I up that users quota. Some accounts
are set to unlimited emails.
Do you know exactly the account(s) causing the problem?
Yes I do, though many users really have trouble following the simple
directions I provide on how to clean up their boxes. I try to get them
to do it but there is a persistent percentage who will mess it up. And
if they're using multiple accounts on Thunderbird (which happens if
they work part-time for more than one department), they will also
sometimes do it for the wrong account. *sigh*
So sometimes I just go into the webmail and clean it myself, and if
there's a persistent problem with one account I will increase the quota.
Last December, a few people who correspond with us unleashed viruses
on their machines and/or had their Yahoo email accounts hacked (Yahoo
email really, really, really sucks), and suddenly the daily influx of
spam messages across all accounts in my domain went from about 400 to
about 4000, and the influx of malware went from near zero to a couple
dozen. Since then over-quota situations have increased significantly.
It's one thing if a user can't *receive* email for a day or two until
I can get around to dealing with it. It's another if that user can't
*send* email when the mailbox is full due to the email provider's
insane method of verifying users. That's what prompted this whole thread.
So I'm giving serious thought to using another SMTP address. My email
hosting provider is not the same as my connectivity provider; the
connectivity provider may have an SMTP server I can use, so I'm
looking into that.
SMTP is the protocol, (eg "Simple Mail Transfer Protocol"), and the
email address is the username, followed by a "@", followed by the domain
name. The outgoing SMTP server is the server that delivers emails going
out from the email client and the SMTP incoming server is the server
that has all the email accounts, (eg inbox and other folders). In my
situation the SMTP incoming and outgoing servers are one and the same,
but they can be completely different computers with different IPs.
I'm not sure having a separate server to deliver emails would solve your
problem. if an email was sent by a user, whose account was over quota,
to be delivered by a separate outgoing server, any reply from a
recipient would fail, due to quota limits, and the user whose account
was over quota might not be notified of the problem. LOL
From what I've gather from reading the threads, you're currently
running on an ISP mail server that services accounts under multiple
domains, (eg a single mail server servicing multiple domains), and you
can administer your own domain with the HTML interface provided by your
ISP. You might consider setting up another domain with your ISP devoted
strictly for email services.
Regards,
LelandJ
Thanks.
Ken Dibble
www.stic-cil.org
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
