ColdFusion 2023 Update 12 causing error Cannot find implementation class coldfusion.tagext.mail.Mail

[paul_durrant]

Last week we applied Update 12 to our ColdFusion 2023 and are now getting an error when trying to send emails from ColdFusion pages.

Error is : ColdFusion Cannot find implementation class coldfusion.tagext.mail.MailTag for the mail tag

Code example : 

<cfmail from="servicedeskplus@xxxx.uk" to="developer@xxxx.uk" subject="Test" type="html" server="smtprelay.xxx.uk">

Email sent

</cfmail>

C:\ColdFusion2023\cfusion\Mail\Undelivr and Spool are both empty

We had a problems (remote_user not found) following the Update 12 and Adobe support supplied these additional steps that resolved that issue (including clearing down folders ColdFusion2023\cfusion\wwwroot\WEB-INF\cfclasses and ColdFusion2023\cfusion\bin\felix-cache) : 

Step 16 : update jvm.config

Take the backup of existing the jvm.config file before making changes.

Add the below java flags in the jvm.config file under path C:\ColdFusion2023\cfusion\bin 

-Dcfdocument.metahttpequivrefresh.localfile=TRUE

-Dcoldfusion.encryption.useCFMX_COMPATAsDefault=TRUE

-Dcoldfusion.searchimplicitscopes=true

Add one by one without any extra gaps in the file.

Step 17 : Navigate to ColdFusion2023\cfusion\wwwroot\WEB-INF\cfclasses

Remove all the files

Step 18 : Clear the felix cache from the below directory:

ColdFusion2023\cfusion\bin\felix-cache.

[paul_durrant]

also checked packages installed.

cfpm>list
The packages repository https://www.adobe.com/go/cf2023_packages is not accessible. You can only load the packages that are available locally in the C:\ColdFusion2023\bundles directory.
adminapi, version : 2023.0.07.330663
administrator, version : 2023.0.11.330706
ajax, version : 2023.0.07.330663
awsdynamodb, version : 2023.0.05.330608
awslambda, version : 2023.0.11.330706
awss3, version : 2023.0.11.330706
awss3legacy, version : 2023.0.05.330608
awssns, version : 2023.0.05.330608
awssqs, version : 2023.0.05.330608
axis, version : 2023.0.11.330706
azureblob, version : 2023.0.11.330706
azureservicebus, version : 2023.0.11.330706
caching, version : 2023.0.11.330706
ccs, version : 2023.0.11.330706
cfmongodb, version : 2023.0.05.330608
chart, version : 2023.0.11.330706
com, version : 2023.0.05.330608
db2, version : 2023.0.07.330663
debugger, version : 2023.0.11.330706
derby, version : 2023.0.05.330608
document, version : 2023.0.08.330668
dotnet, version : 2023.0.05.330608
eventgateways, version : 2023.0.05.330608
exchange, version : 2023.0.11.330706
feed, version : 2023.0.05.330608
ftp, version : 2023.0.11.330706
gcpfirestore, version : 2023.0.05.330608
gcppubsub, version : 2023.0.05.330608
gcpstorage, version : 2023.0.05.330608
graphqlclient, version : 2023.0.05.330608
htmltopdf, version : 2023.0.11.330706
image, version : 2023.0.11.330706
mail, version : 2023.0.11.330706
mysql, version : 2023.0.07.330663
odbc, version : 2023.0.11.330706
oracle, version : 2023.0.11.330706
orm, version : 2023.0.11.330706
ormsearch, version : 2023.0.11.330706
pdf, version : 2023.0.11.330706
pmtagent, version : 2023.0.12.330713
postgresql, version : 2023.0.11.330706
presentation, version : 2023.0.08.330668
print, version : 2023.0.11.330706
redissessionstorage, version : 2023.0.11.330706
report, version : 2023.0.11.330706
saml, version : 2023.0.11.330706
scheduler, version : 2023.0.05.330608
search, version : 2023.0.11.330706
sharepoint, version : 2023.0.11.330706
spreadsheet, version : 2023.0.05.330608
sqlserver, version : 2023.0.05.330608
sybase, version : 2023.0.07.330663
websocket, version : 2023.0.11.330706
zip, version : 2023.0.11.330706

[Charlie Arehart]

Paul, it's not clear if you see the error indicated in this second response of yours, the report that: "The packages repository https://www.adobe.com/go/cf2023_packages is not accessible."

1) This is the first problem to solve for you. If you visit that url, you'll find it actually redirects to https://cfmodules.adobe.com/cf2023/bundlesdependency.json.  What happens if you visit that url? 

First, you can try it from a browser on the server (I see you're on windows). Second, and more important, visit it from WITHIN CF by way of using cfhttp:

<cfhttp url="https://cfmodules.adobe.com/cf2023/bundlesdependency.json">

<cfdump var="cfhtto">

What is the result of that?

2) If it fails, what is the error? Or does it hang?

You may have a firewall block that you need to open. 

Or if that's not an option,. you'd need to follow the steps for doing a manual offline update, as outlined on each update technote. 

3) FWIW, I suspect this happened also during your attempt to run the update. Sadly, cf updates now entail two steps, at least if the update (or any you are skipping) entailed any packages being updated.

This aspect of trying to download package updates is tracked at the END of the update log, which is the log file with the very long name, in the folder for the update created in cfusion/hf-updates. Is there any error there? 

Then the actual APPLICATION of the package update/s happens during the next cf startup (which is triggered by the cf update process), as logged during that startup in the cfusion/logs/coldfusion-out.log.

(For anyone reading this who may run multiple instances of cf within their cf deployment: depending on how you run your cf updates, you may find all the above not in the cfusion instance but in the folder for your instance, which is a SIBLING to the cfusion folder.)

Paul, let us know what you may find. 

[Charlie Arehart]

I tweaked my previous reply, adding the new sentence at the end of my point 2. I'm noting this in case Paul might get the email notification of my first reply and start replying without knowing of that addition (edits don't generate new email notifications by default here, iirc). 

[paul_durrant]

Hi Charlie, 

Our ColdFusion servers sit behind a firewall and are for internal use only.

We knew about this when we applied Update 12, which is why it was done manually.

We contacted Adobe Support and they gave us instructions for the manual install after we queried one of the instructions.

We downloaded both :
https://cfdownload.adobe.com/pub/adobe/coldfusion/2023/packages/hotfix-packages-cf2023-012-330713.zi...

https://cfdownload.adobe.com/pub/adobe/coldfusion/2023/updates/hotfix-012-330713.jar

That URL https://www.adobe.com/go/cf2023_packages is blocked from the browser.

Within a test page I added your code and it returned : cfhtto

There are no errors or warnings In log

C:\ColdFusion2023\cfusion\hf-updates\hf-2023-00012-330713\Adobe_ColdFusion_2023_Update_12_Install_01_08_2025_11_14_07.log

I also checked “mail” and “exchange” – no hits.

Last entries in log file are :

Custom Action:  com.adobe.ia.action.StartServersAction

                          Status: SUCCESSFUL

Custom Action: com.adobe.ia.action.UninstallServersListAction

                          Status: SUCCESSFUL

In cfusion/logs/coldfusion-out.log - These are the errors on the day it was installed :

Error [main] - Unable to install felixclassloader package: org.apache.http.conn.ConnectTimeoutException: Connect to www.adobe.com:443 [www.adobe.com/2.18.66.235, www.adobe.com/2.18.66.225] failed: Connect timed out

Error [http-nio-8500-exec-8] - Object Instantiation Exception.Class not found: coldfusion.print.PrinterInfo The specific sequence of files included or processed is: C:\ColdFusion2023\cfusion\wwwroot\CFIDE\administrator\settings\version.cfm, line: 507

Error [main] - Unable to install felixclassloader package: org.apache.http.conn.ConnectTimeoutException: Connect to www.adobe.com:443 [www.adobe.com/2.22.144.75, www.adobe.com/2.22.144.102] failed: Connect timed out

Error [main] - Unable to install felixclassloader package: org.apache.http.conn.ConnectTimeoutException: Connect to www.adobe.com:443 [www.adobe.com/2.19.117.34, www.adobe.com/2.19.117.8] failed: Connect timed out

Jan 8, 2025 15:15:22 PM

And then we see the first occurrence of this error the following day :

Jan 9, 2025 10:15:15 AM Error [ajp-nio-127.0.0.1-8022-exec-7] - Cannot find implementation class coldfusion.tagext.mail.MailTag for the mail tag. The specific sequence of files included or processed is: D:\peny\PENY_Schedule_clean.cfm''

I can supply these log files if they help.

The instructions supplied by Adobe Support to install Update 12 were (once I combined the 2 sets of comments steps 1-14, and 15- 19) :

Step1 : Download the package.

Download the packages, once downloaded, verifying the checksum is recommended (but optional) to ensure the integrity of the files.
https://cfdownload.adobe.com/pub/adobe/coldfusion/2023/packages/hotfix-packages-cf2023-012-330713.zi...

Copied to :

C:\temp\CF2023-update12\hotfix-packages-cf2023-012-330713

Step 2 : Extract the downloaded zip file and rename it to bundles.

Step 3 : Navigate to C:\ColdFusion2023 (ColdFusion Installation Directory)

Step 4 : Take the backup of existing bundles directory

Step 5 : Copy the extracted and renamed bundles directory to the C:\ColdFusion2023

Step 6 : Stop the ColdFusion services.

Step 7 : Open the command prompt as Admin

Step 8 : cd C:\ColdFusion2023\jre\bin

step 9: Download the jar file from below link
 https://cfdownload.adobe.com/pub/adobe/coldfusion/2023/updates/hotfix-012-330713.jar

copied to :

C:\temp\CF2023-update12\hotfix-012-330713.jar

Step 10: Copy the downloaded jar hotfix-012-330713.jar to the C:\ColdFusion2023\jre\bin

Step 11 : Run the below command 
java.exe -Djdk.util.zip.disableZip64ExtraFieldValidation=true -jar hotfix-012-330713.jar

Step 12 : Follow the on-screen instructions to complete the update installation.

Step 13 : Once the installation is finished, ColdFusion services will start in the background, but they may or may not appear in the Windows Service Management console.
You must manually stop or kill the ColdFusion-related processes in the Task Manager and restart the services via the Windows Service Management console.

Step 14 : Log in to the ColdFusion Administrator page and check the “Settings Summary” to confirm the update level and build number.

ColdFusion build number should be 2023,0,12,330713

Step 15 : Apply fix for remote_user error.  Stop the ColdFusion services.

Step 16 : update jvm.config

Take the backup of existing the jvm.config file before making changes.

Add the below java flags in the jvm.config file under path C:\ColdFusion2023\cfusion\bin

-Dcfdocument.metahttpequivrefresh.localfile=TRUE
-Dcoldfusion.encryption.useCFMX_COMPATAsDefault=TRUE
-Dcoldfusion.searchimplicitscopes=true

 
Add one by one without any extra gaps in the file.

 
Step 17 : Navigate to ColdFusion2023\cfusion\wwwroot\WEB-INF\cfclasses

Remove all the files

Step 18 : Clear the felix cache from the below directory:

ColdFusion2023\cfusion\bin\felix-cache.

Step 19 : Restart ColdFusion service

[Charlie Arehart]

XcPaul, you say:

Hi Charlie, 

Our ColdFusion servers sit behind a firewall and are for internal use only.

We knew about this when we applied Update 12, which is why it was done manually.

Just to clarify, you hadn't said anything about that manual offline update (emphasis mine) in your original post above.

And this is indeed where your problem has come in. And I've seen all the back and forth between you and bkbk below from yesterday. I see things remain unresolved for you, as of this morning. 

Because of the threaded nature of this forum, I'll offer a reply to that instead of elaborating here. 

[BKBK]

 Possibly an issue with packages? If so, tthere is one way to correct it. It involves downloading all the current ColdFusion 2023 packages yourself.

To do so, proceed as follows:

1.  Stop ColdFusion.
2.  Delete the Felix cache. In other words, open the directory C:\ColdFusion2023\cfusion\bin\felix-cache and delete all its contents.
3.  Check to make sure the directory C:/ColdFusion2023/bundles/ exists. If it does, then back it up by moving it, together with all its contents, to a location outside ColdFusion.
   Then ensure that C:/ColdFusion2023/bundles/ is empty.
   
   If the directory doesn't exist to start with, then that is already an issue. In that case, create the directory.
   
4.  Check the firewall rules and ensure that ColdFusion has full access to C:/ColdFusion2023/bundles/.
5.  Open the Command Prompt (cmd) as Administrator;
6.  Use the DOS cd command to navigate to  {CF2023_HOME_DIR}/cfusion/bin;
7.  Type cfpm and press ENTER. You should get ColdFusion's package manager prompt cfpm;
8.  Now use the downloadrepo command to download the packages repository. To do so, type 
   
   downloadrepo C:\ColdFusion2023\bundles 
   
   and press ENTER. It may take up to half an hour for the download to complete. So be patient. The cfpm cursor will reappear when the download is complete.
9.  Verify that the directory C:/ColdFusion2023/bundles indeed contains the downloaded packages.
10.  Edit /lib/neo-updates.xml and make sure it contains the following:

<packagesurl>file:///C:/ColdFusion2023/bundles/bundlesdependency.json</packagesurl>
<defaultpackagesurl>file:///C:/ColdFusion2023/bundles/bundlesdependency.json</defaultpackagesurl>

11.  Restart ColdFusion 2023.
12.  Check whether you can now send mail in ColdFusion 2023.

[paul_durrant]

Hi, 

Giving the server access to the web will be a problem.  Is there a way I can download the packages manually, copy them to the server, and then install them?

Thanks

Paul

[BKBK]

From what you say about restricted access to the web, it just might be that that affects the download of packages. So, let's do a test.

Assume for the moment that all the required packages have been downloaded. 

Do the following:

1.   Stop ColdFusion 2023.

2.  If the file C:/ColdFusion2023/bundles/bundlesdependency.json exists, then back it up by moving it to a location outside ColdFusion. Manually download the file https://cfmodules.adobe.com/cf2023/bundlesdependency.json and save it on the server as the file C:/ColdFusion2023/bundles/bundlesdependency.json.

3.  Edit /lib/neo-updates.xml and make sure it contains the following:

<packagesurl>file:///C:/ColdFusion2023/bundles/bundlesdependency.json</packagesurl>
<defaultpackagesurl>file:///C:/ColdFusion2023/bundles/bundlesdependency.json</defaultpackagesurl>

4..  Restart ColdFusion 2023.
5.  Check whether you can now send mail in ColdFusion 2023.

[paul_durrant]

Same error.

For info :

in bundlesdependency.json the differences are pmtagent and administrator bundles are not in the downloaded version 

in neo-updates.xml  the differenes are the 2 lines above replaced 

<packagesurl>https://www.adobe.com/go/cf2023_packages</packagesurl>                    <defaultpackagesurl>https://www.adobe.com/go/cf2023_packages</defaultpackagesurl>

[BKBK]

Same error.

By paul_durrant

Then you really should find a way to run downloadrepo. That is, find a way to complete the 12-step process I gave earlier.

[Charlie Arehart]

Paul, what is your packageurl value in neo_updates.xml? It's unclear from what you've written here. Do you have it pointing to the bundlesdependency.json found in the folder where you should have extracted the zip you downloaded manually?

I appreciate how frustrating this must be: you've gotten 16 steps from Adobe, which never mention setting that value. Then you've gotten 12 steps from bkbk, which hinge on the cfpm downloadrepo that you can't run for being offline. 

But the process is discussed more succinctly (if perhaps tersely) in each update technote, under "Install the update in offline mode manually", which clearly says, "Update "packagesurl" in cfusion/lib/neo_updates.xml of cfusion and all its child instances to point to <InstallerRepositoryUnzippedPath>/bundles/bundlesdependency.json present inside the downloaded folder."

To be clear, that info is used not only for the update process (whether done from the admin or commandline via java - jar), but also by the cfpm install/update commands, and most importantly by the startup of cf itself.

(Note also that one doesn't HAVE to edit or view that neo_updates.xml file: there's also a field for it in the cf admin--assuming one can access the admin ui, of course. It's a field on the settings tab of the package manager page. Also, bkbk, your replies refer to  the file as neo-updates.xml, with a dash. You might want to correct the 3 references above for that, in case some folks don't read down to this.) 

Getting those packages in place and that packageurl pointing to the right place with the packages for this update seems the crux of your issue. Let us know how it goes.

PS Folks need to be aware that if they point packageurl to a folder having the files for cf update x, they'll need to correct that before applying cf update y, to make sure that path has the downloaded/unzipped package files suited to THAT update. 

[paul_durrant]

Hi Charlie, 

When I ran Update 12 in neo_updates.xml the values were

                                <defaulturl>https://www.adobe.com/go/coldfusion-updates</defaulturl>

                                <packagesurl>https://www.adobe.com/go/cf2023_packages</packagesurl>

I have now set them to

                <packagesurl>file:///C:/ColdFusion2023/bundles/bundlesdependency.json</packagesurl>                <defaultpackagesurl>file:///C:/ColdFusion2023/bundles/bundlesdependency.json</defaultpackagesurl>

I copied the contents of https://cfdownload.adobe.com/pub/adobe/coldfusion/2023/packages/hotfix-packages-cf2023-012-330713.zi...

To C:\ColdFusion2023\bundles

Do I now try and install Update 12 again? ie : 

Copy the downloaded jar hotfix-012-330713.jar to the C:\ColdFusion2023\jre\bin

run : java.exe -Djdk.util.zip.disableZip64ExtraFieldValidation=true -jar hotfix-012-330713.jar

[paul_durrant]

I tried to install Update 12 again (to overwrite the existing Update 12), but it stated that the Update already installed, and cannot progress it any further.

So need to wind back somehow (or override the check).

(the Virtual Machine checkpoints from the update work last week have since been disposed of since we though it was working)

Tried the “check updates” button in ColdFusion Admin, but nothing happened.

• Even though neo_updates.xml now points to the local folder on c drive, not sure what it could have done.
• Package site : file:///C:/ColdFusion2023/bundles/bundlesdependency.json
• But update site still : https://www.adobe.com/go/coldfusion-updates

[BKBK]

Did you try the 12-step process I suggested? If so, what was the result?

[paul_durrant]

Hi BKBK, 

Getting internet access to for these servers will take some time (need to go through IT Security, Networks and Infrastruture teams).   

Adobe support have suggested an uninstall of Update 12 followed by a reinstall - assume they want the 

neo_updates.xml value to now be :

<packagesurl>file:///C:/ColdFusion2023/bundles/bundlesdependency.json</packagesurl>

<defaultpackagesurl>file:///C:/ColdFusion2023/bundles/bundlesdependency.json</defaultpackagesurl>

note - wondered if the path name slashes are correct for WINDOWS?? eg : 

<packagesurl>file:C:\\ColdFusion2023\\bundles\\bundlesdependency.json</packagesurl>

<defaultpackagesurl>file:C:\\ColdFusion2023\\bundles\\bundlesdependency.json</defaultpackagesurl>

And that the BUNDLES folder is first replaced by the content of 

https://cfdownload.adobe.com/pub/adobe/coldfusion/2023/packages/hotfix-packages-cf2023-012-330713.zi...

Adobe help pages state 

If the core server hotfix installation is successful and if there are errors or issues with packages, packages can be installed/updated from the package manager client(cfusion\bin\cfpm.bat).

But I cannot see how to do that.  Tried : cfpm>downloadrepo C:\ColdFusion2023\bundles, and got

The packages repository file:///C:/ColdFusion2023/bundles/bundlesdependency.json is not accessible. You can only load the packages that are available locally in the C:\ColdFusion2023\bundles directory.

followed by errors.

[BKBK]

@paul_durrant , Thanks for your answer. Manually replacing the BUNDLES folder in the way you describe is actually equivalent to the 12-step process I suggested. So I think something else is blocking the package process.

To answer your question on URL:  no, file:C:\\ColdFusion2023\\bundles\\bundlesdependency.json is not a URL

The correct URL is

file:///C:/ColdFusion2023/bundles/bundlesdependency.json

 You can confirm this by opening the URL in File Explorer.

I can think of one likely reason why you get the error message, "The packages repository file:///C:/ColdFusion2023/bundles/bundlesdependency.json is not accessible. You can only load the packages that are available locally in the C:\ColdFusion2023\bundles directory.". It probably is because the Package Manager (cfpm) process does not have access to the C:\ColdFusion2023\bundles directory.

So, grant cfpm access to the directory. Then restart ColdFusion, and see whether the issue is resolved. 

[Charlie Arehart]

2 things:

1) Paul, no, you did not need to run the install again, only the package updates (in the admin or via cfpm)--once you pointed the packagesurl value at the json file in the folder with the packages. 

2) If the file:// protocol bkbk proposes doesn't work, just put the file name. I'm almost positive that's worked for me before, and it's what's shown in the update release notes manual offline update steps I'd quoted.

Sadly I'm writing from a phone and can't test things. 

[BKBK]

2) If the file:// protocol bkbk proposes doesn't work,

By Charlie Arehart

@Charlie Arehart , you are apparently confusing two file URI schemes: file://{FULLY_QUALIFIED_DOMAIN_NAME } and file:///{FULLY_QUALIFIED_FILE_PATH} .  You wrongly attribute the former to me; I had referred to the latter.

[paul_durrant]

Thank you both for your continuing support - have made progress of a sort.  Focusing just on the packages I replaced the bundles folder with the original folder and ran cfpm > install all.

I was then able to run the email logic!

Next question : are the new packages from download https://cfdownload.adobe.com/pub/adobe/coldfusion/2023/packages/hotfix-packages-cf2023-012-330713.zi... a replacement Bundle folder or are the contents added to the existing Bundle folder?

[Dave Watts]

are the new packages from download https://cfdownload.adobe.com/pub/adobe/coldfusion/2023/packages/hotfix-packages-cf2023-012-330713.zi... a replacement Bundle folder or are the contents added to the existing Bundle folder?

I don't know, but I think you could find out by downloading it in a browser and unzipping it.

[paul_durrant]

Original CF2023 (no updates) folder has 569 files

Update 12 folder has 496 files

Combined folder has 710 files, of which 355 have the same names (so overwrites) with 355 being new files.

So it could be a replacement folder or is expected to be merged.  Don't know how the ColdFusion logic works behind the scenes - unless anyone has a successful CF 2023 Update 12 and lets me know how many files are in their Bundles folder.

Since the original folder has more files than Update 12, I'm tempted to say its a merge?

[BKBK]

Original CF2023 (no updates) folder has 569 files

Update 12 folder has 496 files

Combined folder has 710 files, of which 355 have the same names (so overwrites) with 355 being new files.

...

Since the original folder has more files than Update 12, I'm tempted to say its a merge?

By paul_durrant

No, you should not merge anything. As I said a moment ago, unzipping the downloaded package files results in a replacement or substitute Bundles directory.

You cannot read much into the number of files in the directory. That is because the directory includes older versions of some packages, some of which are currently redundant.

For example, there are the following 4 versions of the administrator Jar:

and 3 versions of the caching Jar:

[BKBK]

Focusing just on the packages I replaced the bundles folder with the original folder and ran cfpm > install all.

I was then able to run the email logic!

By paul_durrant

Great news. 

Next question : are the new packages from download https://cfdownload.adobe.com/pub/adobe/coldfusion/2023/packages/hotfix-packages-cf2023-012-330713.zi... a replacement Bundle folder or are the contents added to the existing Bundle folder?

By paul_durrant

Taken together, the files you download from that URL actually comprise a replacement or substitude for the Bundles folder.  

[paul_durrant · Accepted solution]

Got it working using cfpm install all with old Bundles folder.

Ensure original Bundles folder is the one being used (update 12 Bundle folder archived off).

Cd c:\ColdFusion2023\cfusion\bin
Cfpm
install all

New packages only for updates 1 to 11. No new packages included in Update 12.
Since we only need update 12 for the security update this is not an issue. May not apply to everyone, but worked for us.