for all people who want making access to Spamihilator from local network (for. ex. from any computer connected to our interface 192.168.0.1): one must download and install Fpipe http://www.foundstone.com, then run it with this command: fpipe -l 110 -r 110 127.0.0.1. Now Spamihilator can work for any client in our localnetwork . Bye.

(The documention is in english. Translated it with google to german just for fun. "Krauts" can so read something about "Brandmauern" and "Verkehr mit Quelltoren" *pfui* Bob - HELP - we need this autotranslator - translator tool fast! )

I'm very interested in the solution you suggested, but would like to check if i got it right. If my questions seem stupid, lets say I am forced to administer my network with absolutely no competence for that task:-(

1. Was your mail just an idea or did you implement it? You have that setup running now for some time and with no problems, right?

2. I run the fpipe at the server to redirect incoming traffic to localhost, the only host spami can use. Then in Eudora I specify the servers ip address as incoming mail server. Have I got this right?

3. I assume I have to make a bat file or something to run fpipe automatically when I restart my server?

FPipe works WONDERFUL but there is one problem. It remains open in a command window when run. I found a work around.
http://www.teamcti.com/trayit/trayit.htmFollow the directions. All your command windows will minimize to tray then but this is ok.

Hope this helps and THANK YOU THANK YOU for finding FPipe for me. It allows me to connect with my laptop WIFI at home without worrying about the spam

since some work has to be done on the spami host (train the learning area, restore misfiltered messages, put pepople in the white list, ...)
i think using spami like you did is perhaps not a good idea...

I have a 20 hosts network here and finaly decide to put spami on each station and train people to use it...

Maybe I'm missing something, but I think you can access Spami on one machine from other machines with no fpipe or other programs. For example, I have a machine called "A" with IP address 192.168.2.25 that is running Spami. That means it is running a server listening on port 110 for incoming POP3 requests.

On another machine, called "B" with IP address 192.168.2.26, I set up my Outlook Express account to access A or 192.168.2.25 instead of 128.0.0.1 for incoming mail. Then set up the user name and password as you would if Spami were on B, only use the pop.somplace.com&joeblow form and don't use the service provider.

The disadvantages I see are:

1. The trapped spam will reside on A, and you will have to check the Spami recycle bin on that computer.

2. If you access your account this way from machine B, then go to machine A later, your mail will not be there, but will still be on B.

If you have several people on the LAN all using different mail accounts, then you're probably better off installing Spami on each machine. But there would be an advantage, for example, if you're the only one who would bother to scan the recycle bin. Then you could have all the junk mail in one place.

However, suppose Spami traps an incoming piece of mail into the recycle bin, but you decide it's real mail and should go to the recipient. If you restore it from the recycle bin, it goes into your mailbox on A even if it's for the person on B. Then you somehow have to get it to him/her.

That means there won't be much privacy, and it'll be somewhat intrusively obvious to the various users. Also, it's a big responsibility to decide if somebody else's email is junk or not. You could easily throw away something they think is important.