|
Hi
I was also getting the same error on local clients
501 and I have tried what you said to Ken but its not working, whats the
story
Thanks
TM
----- Original Message -----
Sent: Monday, September 23, 2002 11:55
PM
Subject: [VOPmail Beta] 501 unable to
relay
Hi Steve,
I would highly recommend either adding your users
class C to the allow mail for relay feature or have your users use smtp
authentication. POP-B4-You drop requires that a user pops. If their ip is in
cache they can send if not they cannot, it's as simple as that therefore no
matter what amount of time you set you will still get those errors
periodically because some clients always try to send b4 poppping which will
result in the error below.
Thank you
--
----- Original Message -----
Sent: Monday, September 23, 2002 5:52
PM
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
Toll Free
1-866-758-0744
|
