01-Nov-2022

A lot less spam
No surprises in the monthly maintenance job, just that the number of (spam) messages that pass the filter has dropped dramatically:

PMAS statistics for October
Total messages    :   3738 = 100.0 o/o
DNS Blacklisted   :      0 =    .0 o/o (Files:  0)
Relay attempts    :     49 =   1.3 o/o (Files: 25)
Accepted by PMAS  :   3689 =  98.6 o/o (Files: 31)
  Handled by explicit rule
         Rejected :   2555 =  69.2 o/o (processed),  68.3 o/o (all)
         Accepted :    158 =   4.2 o/o (processed),   4.2 o/o (all)
  Handled by content
        Discarded :    296 =   8.0 o/o (processed),   7.9 o/o (all)
     Quarantained :    376 =  10.1 o/o (processed),  10.0 o/o (all)
        Delivered :    304 =   8.2 o/o (processed),   8.1 o/o (all)
.
What I also noticed is that some of the servers from where these messages were sent, have likely been hacked, or abused. At some point, these servers were no longer in the list (not even in the PMAS logs) so I think these have been recovered; of some have been taken off-line. Another thing: the number of messages increases in the weekend, during the week the number of messages is (somewhat) lower.

No relay attempts – except on 10-Oct-2022; 10 from 115.223.19.84, sent from (bogus?) account test@freedominter.net, sent to garymanages@gmail.com, and 3 from 185.28.39.4, stating to be me (so must have been forged) end sent to jacksb841@gmail.com.

08-Sep-2022

PMAS rules updated
In order to limit the amount of spam messages that have the same visual characteristics: subject, content-type of MIME attachment is “text/html”, I checked what they have in common according PMAS. And I found there are four properties:

  • X-PMAS-BDY-IMAGE_LINK3: Web site link image is attached (5.000)
  • X-PMAS-BDY-TEENY_FONT: Message tries to hide text in teeny-tiny font (10.000)
  • X-PMAS-BDY-NONSENSE_STYLE5: Message hides text with useless <STYLE> tags (10.000)
  • X-PMAS-META-IMAGE_ATTACHED: Embedded HTML image is attached (2.000)

There are some more properties that most have in common, but not all, so to block all of the messages that contain the given properties, the others are irrelevant.
By adding this rule to the local test-file:

meta BLOCKTHESE (IMAGE_LINK3 && TEENY_FONT && NONSENSE_STYLE5 && __IMAGE_ATTACHED)
describe BLOCKTHESE This is real spam
score BLOCKTHESE 300

PMAS will close the connection when the combination of these properties is found, as is found in the logfile: where messages would have a score, based on what PMAS scanning would find, due to the combination of these properties, 300 is added to the score – causing rejection:

8-OCT-2022 18:23:53.60: RS|344.000000|em.errihani@encgsettat.ac.ma|willem@grootersnet.nl|Tonita41||VMF_NO_SMTP,__FROM_NO_AT,__HAS_X_MS_EXCHANGE,__CT,__MIME_VERSION,__SUBJ_RE_SPAM03,__RETURN_PATH01,__FROM_HERE,__TO_HERE,__DATE_HERE,__SUBJECT_HERE,__RCVD_MS,__CTYPE_HAS_BOUNDARY,__MULTIPART,__SANE_MSGID,__HAS_MSGID,__PHISHING_WU3,__PHSHCOMMBANK02,__POSTCARD06,__NOT_CNN_URI,__HTTP_URI,__NOT_IRS_URI,REPUTATION_URI_NONSPAM,__TAG_EXISTS_BODY,__TAG_EXISTS_HEAD,__TAG_EXISTS_HTML,__TAG_EXISTS_META,__TAG_EXISTS_END_BODY,__TAG_EXISTS_END_HEAD,__TAG_EXISTS_END_HTML,__BASE64_HTML,__BODY_EXISTS,__BODY_CT_HTML,__ONEPART,__ENDPART,__IMAGE_JPEG,__RAWBODY_EXISTS,__8BIT_BODY,__END_HTML_MESSAGE,IMAGE_LINK3,TEENY_FONT,__SOME_HTML_TAG,__WHITE_BG1,__WHITE_TEXT01,NONSENSE_STYLE5,__FULL_BODY_EXISTS,__IMAGE_ATTACHED,__BDATE003,__DOCTYPE_URI,__1601M01,BLOCKTHESE,RETURN_PATH,WHITE_TEXT,IMAGE_ATTACHED|
8-OCT-2022 18:26:52.37: RS|330.000000|lhoralek@zshalkova.cz|willem@grootersnet.nl|Susy||VMF_OK,__FROM_NO_AT,__HAS_X_MS_EXCHANGE,__CT,__MIME_VERSION,__SUBJ_RE_SPAM03,__RETURN_PATH01,__FROM_HERE,__TO_HERE,__DATE_HERE,__SUBJECT_HERE,__RCVD_MS,__CTYPE_HAS_BOUNDARY,__MULTIPART,__SANE_MSGID,__HAS_MSGID,__PHISHING_WU3,__PHSHCOMMBANK02,__POSTCARD06,__NOT_CNN_URI,__HTTP_URI,__NOT_IRS_URI,REPUTATION_URI_NONSPAM,__TAG_EXISTS_BODY,__TAG_EXISTS_HEAD,__TAG_EXISTS_HTML,__TAG_EXISTS_META,__TAG_EXISTS_END_BODY,__TAG_EXISTS_END_HEAD,__TAG_EXISTS_END_HTML,__BASE64_HTML,__BODY_EXISTS,__BODY_CT_HTML,__ONEPART,__ENDPART,__IMAGE_JPEG,__RAWBODY_EXISTS,__8BIT_BODY,__END_HTML_MESSAGE,IMAGE_LINK3,TEENY_FONT,__SOME_HTML_TAG,__WHITE_BG1,NONSENSE_STYLE5,__FULL_BODY_EXISTS,__IMAGE_ATTACHED,__BDATE002,__RUM017,__DOCTYPE_URI,__1601M01,BLOCKTHESE,RETURN_PATH,IMAGE_ATTACHED|
8-OCT-2022 18:34:26.28: RS|362.000000|betty@pickupflowers.com|willem@grootersnet.nl|Judie||VMF_OK,__FROM_NO_AT,__CT,__MIME_VERSION,__SUBJ_RE_SPAM03,__FROM_HERE,__TO_HERE,__DATE_HERE,__SUBJECT_HERE,__CTYPE_HAS_BOUNDARY,__MULTIPART,__SANE_MSGID,__HAS_MSGID,__PHISHING_WU3,__PHSHCOMMBANK02,__POSTCARD06,__NOT_CNN_URI,__HTTP_URI,BLIND_DATE_URI,__NOT_IRS_URI,REPUTATION_URI_NONSPAM,__TAG_EXISTS_BODY,__TAG_EXISTS_HEAD,__TAG_EXISTS_HTML,__TAG_EXISTS_META,__TAG_EXISTS_END_BODY,__TAG_EXISTS_END_H
EAD,__TAG_EXISTS_END_HTML,__BASE64_HTML,__BODY_EXISTS,__BODY_CT_HTML,__ONEPART,__ENDPART,__IMAGE_JPEG,__RAWBODY_EXISTS,__8BIT_BODY,__END_HTML_MESSAGE,IMAGE_LINK3,TEENY_FONT,__SOME_HTML_TAG,__WHITE_BG1,__WHITE_TEXT01,NONSENSE_STYLE5,__FULL_BODY_EXISTS,__IMAGE_ATTACHED,__DOCTYPE_URI,__1601M01,BLOCKTHESE,BASE64_HTML,WHITE_TEXT,IMAGE_ATTACHED|
8-OCT-2022 18:34:58.87: RS|350.000000|405968049@ms.yru.ac.th|willem@grootersnet.nl|Trudy5||VMF_OK,__FROM_NO_AT,__HAS_X_MS_EXCHANGE,__CT,__MIME_VERSION,__ID_RETURN_PATH,__SUBJ_RE_SPAM03,__RETURN_PATH01,__FROM_HERE,__TO_HERE,__DATE_HERE,__SUBJECT_HERE,__RCVD_MS,__CTYPE_HAS_BOUNDARY,__MULTIPART,__SANE_MSGID,__HAS_MSGID,__PHISHING_WU3,__PHSHCOMMBANK02,__POSTCARD06,__0704_CLICK_ME02,__NOT_CNN_URI,__HTTP_URI,__NOT_IRS_URI,REPUTATION_URI_NONSPAM,__TAG_EXISTS_BODY,__TAG_EXISTS_HEAD,__TAG_EXISTS_HTML,__TAG_EXISTS_META,__TAG_EXISTS_END_BODY,__TAG_EXISTS_END_HEAD,__TAG_EXISTS_END_HTML,__BASE64_HTML,__BODY_EXISTS,__BODY_CT_HTML,__ONEPART,__ENDPART,__IMAGE_JPEG,__RAWBODY_EXISTS,__8BIT_BODY,__END_HTML_MESSAGE,IMAGE_LINK3,TEENY_FONT,__SOME_HTML_TAG,__WHITE_BG1,NONSENSE_STYLE5,__FULL_BODY_EXISTS,__IMAGE_ATTACHED,__BDATE003,__PHOTOS,__BDATE245A,__DOCTYPE_URI,__1601M01,BLOCKTHESE,RETURN_PATH,IMAGE_ATTACHED,BLIND_DATE3|
8-OCT-2022 18:35:28.81: RS|370.000000|c.aknine@lutetia.paris|willem@grootersnet.nl|Myesha|(no msgid)|VMF_NO_ADDRESS,__FROM_NO_AT,__CT,__MIME_VERSION,__FROM_HERE,__TO_HERE,__DATE_HERE,__SUBJECT_HERE,__CTYPE_HAS_BOUNDARY,__MULTIPART,__PHISHING_WU3,__PHSHCOMMBANK02,__POSTCARD06,__NOT_CNN_URI,__HTTP_URI,BLIND_DATE_URI,__NOT_IRS_URI,REPUTATION_URI_NONSPAM,__TAG_EXISTS_BODY,__TAG_EXISTS_HEAD,__TAG_EXISTS_HTML,__TAG_EXISTS_META,__TAG_EXISTS_END_BODY,__TAG_EXISTS_END_HEAD,__TAG_EXISTS_END_HTML,__BASE64_HTML,__BODY_EXISTS,__BODY_C
T_HTML,__ONEPART,__ENDPART,__IMAGE_JPEG,__RAWBODY_EXISTS,__8BIT_BODY,__END_HTML_MESSAGE,IMAGE_LINK3,TEENY_FONT,__SOME_HTML_TAG,__WHITE_BG1,__WHITE_TEXT01,NONSENSE_STYLE5,__FULL_BODY_EXISTS,__IMAGE_ATTACHED,__DOCTYPE_URI,__1601M01,BLOCKTHESE,BASE64_HTML,WHITE_TEXT,IMAGE_ATTACHED|

I’ll have to keep an eye on this, because it could mean that otherwise valid messages are rejected as well. But given what I expect, this is unlikely to be the case.

A similar action will be taken on mail that is sent via hotmail.com – which I blocked entirely, for the same reason. For that, I’ll have to re-allow hotmail.com as a sender.

06-Oct-2022

Maintenance problems
Though normal backup works fine (no errors) the monthly cleanup-job ran into problems: It seems that the target disk for storage of the logs was not available. Found that also during the week; there was an issue with the latest reboot (required because I had to power the system down due to work on the power grid at home) that some processes didn’t start, because it was still commented out in the startup procedure. This was started manually and thge startup procedure was corrected. But I didn’t get into the fact that that one disk (DKA0) was not available: to be checked later; another power down (for the same reason) was to be done o I could get into that at that point.
Today, I had this second power down – and I did the archiving of logfiles by hand, on the pagedisk (that has sufficient room).
Mail log was run anyway:

PMAS%nbsp;statistics%nbsp;for%nbsp;September
Total%nbsp;messages%nbsp;%nbsp;%nbsp;%nbsp;:%nbsp;%nbsp;%nbsp;2122%nbsp;=%nbsp;100.0%nbsp;o/o
DNS%nbsp;Blacklisted%nbsp;%nbsp;%nbsp;:%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;0%nbsp;=%nbsp;%nbsp;%nbsp;%nbsp;.0%nbsp;o/o%nbsp;(Files:%nbsp;%nbsp;0)
Relay%nbsp;attempts%nbsp;%nbsp;%nbsp;%nbsp;:%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;28%nbsp;=%nbsp;%nbsp;%nbsp;1.3%nbsp;o/o%nbsp;(Files:%nbsp;20)
Accepted%nbsp;by%nbsp;PMAS%nbsp;%nbsp;:%nbsp;%nbsp;%nbsp;2094%nbsp;=%nbsp;%nbsp;98.6%nbsp;o/o%nbsp;(Files:%nbsp;24)
%nbsp;%nbsp;Handled%nbsp;by%nbsp;explicit%nbsp;rule
%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;Rejected%nbsp;:%nbsp;%nbsp;%nbsp;1457%nbsp;=%nbsp;%nbsp;69.5%nbsp;o/o%nbsp;(processed),%nbsp;%nbsp;68.6%nbsp;o/o%nbsp;(all)
%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;Accepted%nbsp;:%nbsp;%nbsp;%nbsp;%nbsp;130%nbsp;=%nbsp;%nbsp;%nbsp;6.2%nbsp;o/o%nbsp;(processed),%nbsp;%nbsp;%nbsp;6.1%nbsp;o/o%nbsp;(all)
%nbsp;%nbsp;Handled%nbsp;by%nbsp;content
%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;Discarded%nbsp;:%nbsp;%nbsp;%nbsp;%nbsp;204%nbsp;=%nbsp;%nbsp;%nbsp;9.7%nbsp;o/o%nbsp;(processed),%nbsp;%nbsp;%nbsp;9.6%nbsp;o/o%nbsp;(all)
%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;Quarantained%nbsp;:%nbsp;%nbsp;%nbsp;%nbsp;195%nbsp;=%nbsp;%nbsp;%nbsp;9.3%nbsp;o/o%nbsp;(processed),%nbsp;%nbsp;%nbsp;9.1%nbsp;o/o%nbsp;(all)
%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;%nbsp;Delivered%nbsp;:%nbsp;%nbsp;%nbsp;%nbsp;108%nbsp;=%nbsp;%nbsp;%nbsp;5.1%nbsp;o/o%nbsp;(processed),%nbsp;%nbsp;%nbsp;5.0%nbsp;o/o%nbsp;(all)

I added a number of lines to the PMAS filter to block notorious domains but there is still a quite number of messages that are too random in text and header that blocking them is a lot of work. So I leave it as it is, for now.

After the last reboot, DKA0 was available but I missed the web-entries: Found out that the location of the containers of web-related locations was wrong so these could not be loaded: Not on the unit I expected them to be, but on another. I know I moved them but they are not on that drive. Luckily, there is still another version onj another unit, so I could use that; but I had to redo one of the previous activities, but both blogs and the admin pages can now be accessed. But it is weird one is missing… I have to find out why.

Update
Running DFU on the disk where I expected both containers revealed these files were “marked for deletion”. No idea what could have caused this, or it could be that something went wrong in “unproper dismount” due to power failure, or during boot of the controller? Anyway, I could restore both containers, will check them and
since the startup-procedure was correct after all, I have to revert the changes. Next step after that will be enable both containers.

15-Sep-2022

Issues with Dione
Just before we would take a short stay abroad, Dione stalled for some reason, but this was noticed hours later. The system did not respond to any input, not even ^P (to return to console). So the only fast way out was to cycle power (via RMS) and reboot. This did work but shortly after, the system stalled again. So I started Diana – which was still missing a number of required updates in configuration-based files, but at least e-mail did work properly, the websites were accessible, the only problem found was that the blogs didn’t work, but only this blog was updated and not yet copied; most of the images of the “trips, tracks and travels” site could be seen but the blog was not accessible either. I could do some investigation and found that the PHP environment was missing data, but repairing had to wait until the end of our trip.

During the trip, the LetsEncrypt certificates on Diana have been updated.

The first thing after return was to repair the problem in the PHP directory: copying the environment from a logical disk to real hardware caused a [.000000] directory that contained the files that should reside on the root of the environment: the issue was solved my moving these files one level up and delete 000000.dir;. Now the blogs worked again.

Another things that needed to be updated on Diana required Dione to be started, but that stalled during boot. So booted it minimal, to check what was going on. No problem at all! Next, usingĀ  DFU I checked operator.log files to see if that contained any resaon: and behold: though DIR showed operator.log;7035 (the previous one) it could not be found using TYPE. So I checked all disks with DFU VERIFY /Directory and /FIX that found a number of inconsistencies, and fixed them, but the files was still there. Next DFU/REPAIR which again found a number of inconsistencies but the file was now gone. Checked the other disks as well (using /REBUILD), reset Startup_P1 to “” and rebooted. Now the system started immediately.

Next action is about the PMAS configuration files where I store my own lists of accepted, quarantined, discarded and rejected messages. This has been updated just before the trip and so needed to be moved to Diana as well. I left the files that Process sends in because I had no way of knowing which one are really new. Next compiled the files so these are fine as well.

Finally, I copied the latest MySQL backup from Dione to Diana to have this blog up-to-date and add this entry.

To finalize the action, I had to submit batch-jobs – the PMAS jobs were started and running when Diana was started and email-activity activated, but the maintenance jobs were missing, so I added them, but there still may be a number of issues with them, to be solved tomorrow.

On Dione, I stopped most jobs – but left the PMAS jobs run: there is no problem with that, it will keep the PMAS files up-to-date. Since Diana now holds the cluster IP address (where all Internet traffic is forwarded to) there is no problem for both systems to run active-active.

Update (19-Sep-2022)
I put the issue with Dione on the VMS-SIG mailing list, asked for causes. It seems that if one of the disks in the RAID configuration starts to fail, writes to the RAID set is stalled: actually blocking all activity until the write finally succeeds. However, the controller should remove the failing disk from the set. It can also be caused by the accelerator-option failing, or the cache batteries. So I checked Diana first:
$ mc msa$util
MSA> set contr pkc0
MSA> sho cont

Adapter: _PKC0: (DEFAULT)
Smart Array 5300 (c) COMPAQ P2313ABFFOA1F6 Software 2.86
SCSI_VERSION = X3.131:1994 (SCSI-2)
Supported Redundancy Mode: Sym Active/Active Asym Active/Active
Current Redundancy mode: Not Available/Not currently redundant
Current Role: Standby
Cache:
45 megabyte read cache 179 megabyte write cache
Cache is enabled and Cache is GOOD.
No unflushed data in cache.
Battery:
Battery is fully charged.
Controller Mode:
Controller is in HBA Mode.
MSA> sho disk

Parallel SCSI device [Disk]
Disk 0: SCSI bus 0 id 0 size 279.40 [300.00] GB
Disk 000, # 0, size 52420095 blocks, (25.00 [26.84] GB), Unit 0.
Disk 000, # 1, size 52420095 blocks, (25.00 [26.84] GB), Unit 1.
Disk 000, # 2, size 52420095 blocks, (25.00 [26.84] GB), Unit 2.
Disk 000, # 3, size 428662395 blocks, (204.40 [219.48] GB), Unit 3.
Disk 000, # 4, size 13732 blocks, (6.71 [7.03] MB), Unused.

Parallel SCSI device [Disk]
Disk 1: SCSI bus 0 id 1 size 279.40 [300.00] GB
Disk 001, # 0, size 52420095 blocks, (25.00 [26.84] GB), Unit 0.
Disk 001, # 1, size 52420095 blocks, (25.00 [26.84] GB), Unit 1.
Disk 001, # 2, size 52420095 blocks, (25.00 [26.84] GB), Unit 2.
Disk 001, # 3, size 428662395 blocks, (204.40 [219.48] GB), Unit 3.
Disk 001, # 4, size 13732 blocks, (6.71 [7.03] MB), Unused.
MSA> sho unit

Unit 0:
In PDLA mode, Unit 0 is Lun 0.
Cache status : enabled
Max Boot Partition: Unknown
Volume status : VOLUME OK
2 Data Disk(s) used by lun 0:
Disk 0: Partition 0; (SCSI bus 0, SCSI id 0)
Disk 1: Partition 0; (SCSI bus 0, SCSI id 1)
Spare physical drives:
No spare drives are designated.
Logical Volume Raid Level: RAID 1. Mirroring
stripe_size=128.0KB
Logical Volume Capacity : 25.00 [26.84] GB

Unit 1:
In PDLA mode, Unit 1 is Lun 1.
Cache status : enabled
Max Boot Partition: Unknown
Volume status : VOLUME OK
2 Data Disk(s) used by lun 1:
Disk 0: Partition 1; (SCSI bus 0, SCSI id 0)
Disk 1: Partition 1; (SCSI bus 0, SCSI id 1)
Spare physical drives:
No spare drives are designated.
Logical Volume Raid Level: RAID 1. Mirroring
stripe_size=128.0KB
Logical Volume Capacity : 25.00 [26.84] GB

Unit 2:
In PDLA mode, Unit 2 is Lun 2.
Cache status : enabled
Max Boot Partition: Unknown
Volume status : VOLUME OK
2 Data Disk(s) used by lun 2:
Disk 0: Partition 2; (SCSI bus 0, SCSI id 0)
Disk 1: Partition 2; (SCSI bus 0, SCSI id 1)
Spare physical drives:
No spare drives are designated.
Logical Volume Raid Level: RAID 1. Mirroring
stripe_size=128.0KB
Logical Volume Capacity : 25.00 [26.84] GB

Unit 3:
In PDLA mode, Unit 3 is Lun 3.
Cache status : enabled
Max Boot Partition: Unknown
Volume status : VOLUME OK
2 Data Disk(s) used by lun 3:
Disk 0: Partition 3; (SCSI bus 0, SCSI id 0)
Disk 1: Partition 3; (SCSI bus 0, SCSI id 1)
Spare physical drives:
No spare drives are designated.
Logical Volume Raid Level: RAID 1. Mirroring
stripe_size=128.0KB
Logical Volume Capacity : 204.40 [219.48] GB
MSA>

and after Dione was started, did the same on that one:

$ mc msa$util
MSA> set contr pkc0
MSA> sho cont

Adapter: _PKC0: (DEFAULT)
Smart Array 5300 (c) COMPAQ P2313ABFF0683X Software 3.56
SCSI_VERSION = X3.131:1994 (SCSI-2)
Supported Redundancy Mode:
Not currently Redundant
Current Role: Active
Cache:
45 megabyte read cache 179 megabyte write cache
Cache is enabled and Cache is GOOD.
No unflushed data in cache.
Battery:
Battery is fully charged.
Controller Mode:
Controller is in RAID Mode.
MSA> sho disk

Parallel SCSI device [Disk]
Disk 100: SCSI bus 1 id 0 size 279.40 [300.00] GB
Disk 100, # 0, size 104856255 blocks, (50.00 [53.69] GB), Unit 0.
Disk 100, # 1, size 104856255 blocks, (50.00 [53.69] GB), Unit 1.
Disk 100, # 2, size 104856255 blocks, (50.00 [53.69] GB), Unit 2.
Disk 100, # 3, size 271353915 blocks, (129.39 [138.93] GB), Unit 3.
Disk 100, # 4, size 13732 blocks, (6.71 [7.03] MB), Unused.

Parallel SCSI device [Disk]
Disk 101: SCSI bus 1 id 1 size 279.40 [300.00] GB
Disk 101, # 0, size 104856255 blocks, (50.00 [53.69] GB), Unit 0.
Disk 101, # 1, size 104856255 blocks, (50.00 [53.69] GB), Unit 1.
Disk 101, # 2, size 104856255 blocks, (50.00 [53.69] GB), Unit 2.
Disk 101, # 3, size 271353915 blocks, (129.39 [138.93] GB), Unit 3.
Disk 101, # 4, size 13732 blocks, (6.71 [7.03] MB), Unused.
MSA> sho unit

Unit 0:
In PDLA mode, Unit 0 is Lun 0.
Cache status : enabled
Max Boot Partition: Unknown
Volume status : VOLUME OK
2 Data Disk(s) used by lun 0:
Disk 100: Partition 0; (SCSI bus 1, SCSI id 0)
Disk 101: Partition 0; (SCSI bus 1, SCSI id 1)
Spare physical drives:
No spare drives are designated.
Logical Volume Raid Level: RAID 1. Mirroring
stripe_size=128.0KB
Logical Volume Capacity : 50.00 [53.69] GB

Unit 1:
In PDLA mode, Unit 1 is Lun 1.
Cache status : enabled
Max Boot Partition: Unknown
Volume status : VOLUME OK
2 Data Disk(s) used by lun 1:
Disk 100: Partition 1; (SCSI bus 1, SCSI id 0)
Disk 101: Partition 1; (SCSI bus 1, SCSI id 1)
Spare physical drives:
No spare drives are designated.
Logical Volume Raid Level: RAID 1. Mirroring
stripe_size=128.0KB
Logical Volume Capacity : 50.00 [53.69] GB

Unit 2:
In PDLA mode, Unit 2 is Lun 2.
Cache status : enabled
Max Boot Partition: Unknown
Volume status : VOLUME OK
2 Data Disk(s) used by lun 2:
Disk 100: Partition 2; (SCSI bus 1, SCSI id 0)
Disk 101: Partition 2; (SCSI bus 1, SCSI id 1)
Spare physical drives:
No spare drives are designated.
Logical Volume Raid Level: RAID 1. Mirroring
stripe_size=128.0KB
Logical Volume Capacity : 50.00 [53.69] GB

Unit 3:
In PDLA mode, Unit 3 is Lun 3.
Cache status : enabled
Max Boot Partition: Unknown
Volume status : VOLUME OK
2 Data Disk(s) used by lun 3:
Disk 100: Partition 3; (SCSI bus 1, SCSI id 0)
Disk 101: Partition 3; (SCSI bus 1, SCSI id 1)
Spare physical drives:
No spare drives are designated.
Logical Volume Raid Level: RAID 1. Mirroring
stripe_size=128.0KB
Logical Volume Capacity : 129.39 [138.93] GB
MSA>

Apart from the unit sizes (Dione was setup this way when I got it, on Diana I defined the sizes myself), the major difference is that on Diana, the unit is in HBA mode, where on Dione, the controller is in RAID mode. And there is no indication of a failing, or failed disk. Or could the RAID mode on Dione cause the problem? Something to ask on VMS-SIG.

03-Sep-2022

It’s all the same.
Nothing strange on the maintenance job, even mail has no surprises (though I have added quite a few rules in the past weeks):

PMAS statistics for August
Total messages    :   3012 = 100.0 o/o
DNS Blacklisted   :      0 =    .0 o/o (Files:  0)
Relay attempts    :     42 =   1.3 o/o (Files: 31)
Accepted by PMAS  :   2970 =  98.6 o/o (Files: 31)
  Handled by explicit rule
         Rejected :   1989 =  66.9 o/o (processed),  66.0 o/o (all)
         Accepted :    102 =   3.4 o/o (processed),   3.3 o/o (all)
  Handled by content
        Discarded :    277 =   9.3 o/o (processed),   9.1 o/o (all)
     Quarantained :    366 =  12.3 o/o (processed),  12.1 o/o (all)
        Delivered :    236 =   7.9 o/o (processed),   7.8 o/o (all)

No relay attempts – at least, just a few files had some lines in them but none exceeded 2Kb (4 512-byte blocks) which is the minimal size when something is written to the file. So it could hold one line, or at most 10 to 12 lines or so.