* This is the vopmailbeta mailing list *
Though we were initially excited about the POPB4UDrop feature, I've since had a change of heart. We've had a lot of trouble with that feature to the point where we're going to disable it. The only problem is that we have several large accounts who are using the feature and need to be migrated to SMTP Auth. FYI, the problems we are having involve Klez, NAT and various other unusual circumstances that make troubleshooting problems impossible. On the customers' end, they experience intermittent problems sending mail. We could increase the timeout to assuage the latter, but the feature itself has been so problematic that we are probably just going to drop it altogether. Don't get me wrong, the problems with POPB4UDrop are inherent to the concept, not the implementation. I can see how the feature would be useful for some people, but it simply won't work for us. It may not work for you either. Benjamin S. Rogers http://www.c4.net/ v.508.240.0051 f.508.240.0057 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Ken Gardner Sent: Monday, September 23, 2002 5:52 PM To: Vopmailbeta@Vircom. Com Subject: [VOPmail Beta] 501 unable to relay I am constantly getting 501 errors and I am getting frustrated. These are all local clients on the primary domain. I increased the timeout for pop-before-drop to 90 minutes and STILL seems to creep in almost randomly - rarely the same client over extended time. What am I missing!!! The IP pool is always within my pool and the users(senders) are all primary users! ---- SMTPRS log entry made at 09/23/2002 10:15:30 SMTP command failed when talking to 208.187.244.119: >>> RCPT TO: < snip > <<< 501 This system is not configured to relay mail from < snip > for 208.187.244.119 Ken Gardner A Better View Online (916) 536-9500 [EMAIL PROTECTED] www.abvonline.com Toll Free 1-866-758-0744 ** To leave this list, send an email to [EMAIL PROTECTED] and put the word "LEAVE" in the BODY of the email.
