Because the anti-spam frontend is so effective, there is hardly any junk accepted and Outlook’s filters can be minimized. I deleted the Jink sender list on Aphrodite – it contained almost 7000 entries!
There is something weird, thoug, and perhaps it’s gone now: There have been messages marked as “junk” where the sender was NOT in this list, and as far as I could detrmine, there is no field in the message header that would cause it te be marked as such.
Keep it to the Mantra: It’s Windows (well, Office, in this case) and therefore, it is to be expected.
Thgough my ISP and the company do have spam blockers, these seem not half as effective as PMAS. But these few messages can easily be handled.
De-Samba
I don’t know yet what went wrong but the share I created can no longer be accessed. Back to the drawing board and reso the SAMBA configuration from the beginning. It doesn’t help if the knowlegde of Windows is limited and the CIFS documentation limited. Back to the olde Digital days, where the company supplied good software (assuming Samba IS good software) but fails to deliver documentaion in sufficient detail??? Well, we’ll get there some day. But for now CIFS has been disabled.
One thing I could figure out was that the disk wasn’t mounted. No wonder I couldn’t access it. But CIFS silent;ly tried, and tried, and tried – given the operatorlog:
%%%%%%%%%%% OPCOM 13-APR-2008 01:02:21.88 %%%%%%%%%%%
Message from user INTERnet on DIANA
INTERnet ACP SMBD Accept Request from Host: 192.168.0.205 Port: 2708
%%%%%%%%%%% OPCOM 13-APR-2008 01:02:25.34 %%%%%%%%%%%
Message from user INTERnet on DIANA
INTERnet ACP SMBD Accept Request from Host: 192.168.0.205 Port: 2710
%%%%%%%%%%% OPCOM 13-APR-2008 01:34:27.17 %%%%%%%%%%%
Message from user INTERnet on DIANA
INTERnet ACP SMBD Accept Request from Host: 192.168.0.205 Port: 2714
%%%%%%%%%%% OPCOM 13-APR-2008 01:34:30.61 %%%%%%%%%%%
Message from user INTERnet on DIANA
INTERnet ACP SMBD Accept Request from Host: 192.168.0.205 Port: 2716
and this goes on all day. The share is shown in the network places list, although the disk is not mounted. Ok, CIFS will note the share, but when trying to access it, it’s just telling you’re not allowed to access teh location. Not that theer is something wrong with the hardware.
Perhaps, Unix isn’t capable of detecting the path is not accessable at all, in stead of a privilege problem – but VMS is an, IMHO, it should mention it. This is something I would consider “a bad port”.
Now it’s way more quiet on the system.
The WordPress 2.2.3 admin frontpage normally would show a list of RSS feeds – and since a few days, only that part of the form will not display because the PHP engine is at it’s allowed memory limit of 10M on allocation of 11 bytes. This is a part I can do without anyway, it’s not missed. I like the idea the application limits it’s own memory usage, but a requirement for 10M – for a fairly basic page – and still need 11 bytes more?? Well, Unix thought: Get all memory you need….No wonder you’ll need to set a limit. But VMS already has it: PGFLQUO…
Oh well…