At 10:59 AM 07/05/2002 +0200, Michael Penzkofer wrote: >Hi Danny, > >thanks for the try ;-( didn't help anyway. >Trace POP - disabled >Don't log IPs - disabled for internal range 192.168* 127.0.0.1 > >What I'm wondering about: > >ok, I'm calling via pop-server-call "pop.mydyndns.com" from within the >internal network. So I assume the call will be recognized as an incoming >external POP-call. >Should not be logged because of "TracePOP=no".... >But it is... additionally the source IP will be resolved to the machine >name calling: 192.168.0.7 - MYMACHINE_7 >Sambar main window shows: > >[POP3-Server] [time] [internal_machine_:name] - 200 - POP3-command 0 > >No idea why ! >Any more suggestions ?? > >Michael
I believe Don't Log IPs is a HTTP-specific entry - it does not apply to any of the other protocols. Regarding the internal/external issue, Sambar logs all connections. It doesn't matter of the connecting client is on a cable six feet from the server and on the same network or 2,000 miles away on a different network. It is likely you are running NetBIOS over IP (the default for Windows, I believe). Because the client is on the same network as Sambar, it is resolving the IP to the NetBIOS name. To eliminate this, you could disable NetBIOS over IP on the client or disable Resolve Host Names in Sambar. I did not notice before, but are you setting "Trace POP3 = false" in the mail.ini and not config.ini, aren't you? This was moved out of config.ini a long time ago. And finally, as to why you are getting POP information logged when Trace POP3 = false, I really can not say. A bug, perhaps, for Tod to look at? -Jeff ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/
