Problem

SPART in the SEND command

NSPART from the CFTPART macro still used for the notification

SenderID attribute contains the NSPART

Resolution

The behavior observed is 'normal' and not in contradiction to what is documented.

It ensure the correct value is set for the SenderID when SPART is use by the middle-man for transfer commutation type=SERVER is used

Only the notification sent by the final receiver contains the SPART value of the adjacent sender (with or without commutation).