Ken, Would your issues be resolved if you set up a robot process to Email notification to your users when their box is X percent full? The Email could supply the full details of what they need to do to avoid having their Email service disrupted. I don't know if such a solution is possible in your environment but thought I'd pass on the idea. - Joe
On Tuesday, April 30, 2013 3:06 PM, Ken Dibble wrote: >>>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. > >Date: Tue, 30 Apr 2013 15:06:47 -0400 >From: Ken Dibble >To: [email protected] >cc: >Subject: Re: [NF] Standard Email Sender Verification Procedures > >That's the first time I've heard of using SMTP for incoming. We use POP3 to >retrieve incoming emails, and SMTP to send emails. Yes, I shouldn't have >said "address". The email host provider assigns a separate name to the SMTP >server based on the domain name, ie.: mail.MyDomain.org. However, this may >be an alias pointing to a centralized server and not really a separate >server instance, I don't know. > >>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 > >You have a point there. I'll have to think about that. > >> 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. > >Well the only other thing done with the domain is web hosting. I would hate >to have to propagate email address or web URL changes out to everybody who >uses them now. I think that would be way too disruptive. > >Of course, there's always early retirement... *LOL* > >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.
