I now understand the relevance of a .DRPM file, however when its compiled its an .RPM file. When tested against its header via SMIME checking it reports itself as an RPM file. Hardware security devices run checks on all downloaded file to make sure, for example, someone hasn���t renamed a dangerous .exe file at a jpg file and this is how they ensure file integrity of downloaded files. I understand why you have .DRPM files now and I thank you, however when checked against their header via SMIME checking, they all report themselves as .RPM file. I believe this fundamental issue will raise it head again some time in the future and whilst convenient for identification of delta .RPM files, they remain .RPM files. Most all serious Hardware security made by Cisco and Dlink have this feature as as their reported SMIME check is invalid the filed are denied being downloaded by online update. File integrity via SMIME checking is done on the fly in real time by security devices. I accept your reason code of invalid, however I just hope this complication doesn���t come back and bight us later on in development.