Hi Jeff, Just wondering if your server's down or something -- any report attempt leads to Purify just sitting there with the watch showing. There's no apparent network activity. I end up having to force-quit.
Cheers, Mike.
Jeff Hendrickson
Oct 29 2009, 02:20 AM
QUOTE (mike_hore @ Oct 28 2009, 03:06 AM)
Hi Jeff, Just wondering if your server's down or something -- any report attempt leads to Purify just sitting there with the watch showing. There's no apparent network activity. I end up having to force-quit.
Cheers, Mike.
During the process of hardening my server, I closed port 26 for SMTP access, if that is what you were using, try 25. I'm reporting on port 25 with no problem here.
Hkim
Oct 29 2009, 01:54 PM
I also have had a problem reporting on port 26. Changing to port 25 solved the problem.
mikaelf
Oct 29 2009, 03:05 PM
Please open port 26 again, I can only use port 25 at home and work most ISPs here block port 25 (you have to send mail using only their server)
Jeff Hendrickson
Oct 30 2009, 01:38 AM
Port 25 and port 26 are open for reporting on purify.cc.
Hkim
Oct 30 2009, 11:15 PM
Get this Jeff:
I get a spam from a Russian hosting service that reads
QUOTE
. . . If you are using our host service, you have guarantee that we will never delete, suspend or turn off your server. Our data-center is protected from any internet police, even like SpamHaus.org.
and now port 25 does not work when I try to report it and I have to force quit with a "server error" in the log.
Coincidence?
Jeff Hendrickson
Oct 31 2009, 01:12 AM
QUOTE (Hkim @ Oct 30 2009, 07:15 PM)
Get this Jeff:
I get a spam from a Russian hosting service that reads and now port 25 does not work when I try to report it and I have to force quit with a "server error" in the log.
Coincidence?
If you don't get any email from Russia, I would just block the country. I do. I would need to see the email headers to see if this is anything related to something that they are doing ...
mike_hore
Oct 31 2009, 12:06 PM
Hi Jeff, sorry, I was tied up there for a couple of days. Yes, I was using port 26 but as you indicated, everything's working again. If this happens to me again, I'll switch to 25 (I'm reporting via purify.cc so I'm not restricted :-)
Cheers, Mike.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.