|
Glenn,
We had adjust Post.Office 3.5.3b20 to use Restrict Mail Relay by
default.
The HTML docs indicated shutdown up Post.Office with:
/usr/local/post.office/post.office shutdown
For starting post.office, you may want to use
/usr/local/post.office/post.office
without any parameter.
However, we still recommend that you restart the system after a
new
installation to make sure that there is no existing Pop program
running
on your system.
regards,
Eric
On Wednesday, February 27, 2002, at 09:25 PM, Glenn A.Bookout
wrote:
Howdy:
Unfortunately, after my
install of the recent P.O update (
Post.Office-3.5.3b19 ) somehow the
"Restrict Mail Relaying" settings got
wiped out, allowing a SPAMmer to sneak
through.
I think we reset them to
what they were before the install, but am not
sure, any suggestions?
Also, the
"Pop-before-SMTP" setting was left on, but obviously was
ineffective ( it didn't seem to work in
the previous version either ).
Another thing I noticed,
though it existed on the previous version of
P.O ( per my tests ) also, concerns the
documented method for starting
P.O.
According to the HTML docs
the following command should be executed
from root:
/usr/local/post.office/post.office startup
Unfortunately it results in
the following:
pop_before_smtp db
=/var/spool/post.office/pop-before-smtp/PopHosts
Startup Problem:
Invalid command line option
post.office Exiting!
Not good, no P.O
running!
Fortunately, a complete
system re-boot DOES successfully start
Post.Office, though the above may explain
why Pop-before-SMTP doesn't
work.
Tenon's help in these
matters would be greatly appreciated.
Glenn
--------------------------------------------------------------------------------------------------
Eric
Yang
Senior Software Engineer
Tenon
Intersystems
eyang@xxxxxxxxx
1123 Chapala
Street
805-963-6983
Santa Barbara, CA
93103
http://www.tenon.com
--------------------------------------------------------------------------------------------------
|