The changes in this version are:

• Worked around a change in the forthcoming macOS 26.4 that caused EagleFiler to crash at launch. If you’ve updated to macOS 26.4 before updating EagleFiler, you won’t be able to launch EagleFiler to use its auto-update feature, but you can download and install the update manually as described in the Updating From a Previous Version section of the manual.
• When launching EagleFiler on macOS 26.4 or later, macOS may show a “Support Ending for Intel-based Apps” notification. Currently, EagleFiler relies on Rosetta 2, which Apple has committed to supporting until macOS 28 in fall 2027. EagleFiler’s indexer has been ARM-native for a long time. The rest of the app relies on some third-party Intel-based libraries that will not be ported. We’ve been working on removing these dependencies and rewriting the app in Swift. This is a big project, but it should provide many advantages, both in performance and in a newer architecture that can serve as a foundation for many years to come. We expect to finish this and have EagleFiler running fully natively on Apple silicon before macOS 28 is released.
• Added the Import From Paperless script. This lets you import files from Mariner Software’s Paperless app (formerly called ReceiptWallet), which has been discontinued. The categories, collections, and other metadata will be translated to folders, tags, and notes in EagleFiler.
• When importing from Evernote, EagleFiler is better at handling attached files that have no filename extension and notes that contain an attached file but only whitespace for the note text.
• The capture key now works with the Apple Creator Studio versions of Keynote, Numbers, and Pages.
• Added the Append Current Date to Filename and Append Prior Month Date to Filename scripts.
• The Keywords header of e-mail messages is now indexed for searching.
• You can now change the name of a tag via AppleScript.
• Deleting a tag now deletes its child tags instead of just changing their parents.
• Added the Differing Message Counts Importing From Apple Mail section of the manual.
• Updated the following sections of the manual:
  • Applications That Support Capture
  • How can I rebuild a library?
  • Import Bookmarks…
  • Importing Mail From Apple Mail
  • Importing Mail from MailMaven
  • Merge Mailboxes/Message Files
• Updated the Remove Duplicate Messages script to fix a problem where it could time out if EagleFiler was already very busy with other tasks.
• Worked around an issue with macOS Tahoe 26 where windows would still receive mouse clicks after they were closed, preventing them from going through to the app below EagleFiler.
• Worked around a macOS bug that could cause a crash when viewing a Web archive on a Mac with a Touch Bar.
• Made some changes to try to prevent a crash when displaying a table cell.
• Fixed an internal error that could occur when checking whether a record needed to be indexed.
• Fixed a bug where audio or video files could be left open after closing a library (thus preventing the volume from being ejected).
• Fixed an error that could occur when launching a second copy of EagleFiler at the same time.
• Fixed a regression where the diagnostic report didn’t include the error log.
• Updated to version 1.6.3 of the SkimNotes framework.

• Create an alias of ~/Documents.
• Add it to the disk folder to be turned into DMG.
• From there, add it to the layout.

Worked at least once.

hstriepe:

I configure a setting, and the layout, and both are gone after relaunch.

Do you mean in the Settings window in the DropDMG app?

That won’t work (the way Applications does) because every user’s Documents folder is at a different path.

I configure a setting, and the layout, and both are gone after relaunch.

I added a document folder as a drag target, and it is not there on the DMG.

This has all worked for many macOS revs.

I guess the best approach would be to: (1) shut down SpamSieve, but leave the drone feature enabled (2) in Apple Mail, delete the folders created automatically when I reenabled “Train messages in TrainSpam and TrainGood”, then shut down Apple Mail and (3) recreate the two folders in Outlook for Web. [Sorry, I just had to quickly rewrite this section.]

Hopefully the folders will then successfully propagate from Outlook to Apple Mail. Maybe that’s how I did it years ago but I don’t remember. Let’s see how it goes…

steppinwolf:

Unfortunately, IMAP Path Prefix does not appear in the indicated path on macOS or iOS.

The IMAP Path Prefix setting is only available for IMAP accounts, not Exchange accounts.

It does not, but presumably you could log into the webmail at outlook.com or wherever your mail provider is. Or create the mailboxes using one of your iOS devices.

I carefully followed the instructions at 4.3 Drone Setup and Remote Training and see the TrainSpam and TrainGood folders recreated under the Exchange mailbox in Apple Mail for Mac. However, the folders never appeared in the Apple Mail app on my iPhone (iOS) or iPad (iPadOS).

So, I went to 6.3.3.1 Train messages in TrainSpam and TrainGood, specifically the section:

What If I Don’t See the Train Mailboxes on All Devices?

For IMAP accounts, it’s important that the IMAP Path Prefix be set the same way on all devices. Here’s where the setting is located:

• Apple Mail for Mac: Mail ‣ Settings… ‣ Accounts ‣ [account name] ‣ Server Settings ‣ Advanced IMAP Settings ‣ IMAP Path Prefix
• Apple Mail for iOS: Settings ‣ Apps ‣ Mail ‣ Mail Accounts ‣ [account name] ‣ Account Settings ‣ Advanced ‣ IMAP Path Prefix

Unfortunately, IMAP Path Prefix does not appear in the indicated path on macOS or iOS. Also, the subsequent tip “If you see the Train mailboxes in Apple Mail on your Mac, but not on other devices, this could be because Mail created the mailboxes but did not sync them to the server. You can fix this by deleting them on your Mac, quitting Mail, and then creating TrainSpam and TrainGood mailboxes using Webmail” only applies to Apple Mail. iCloud Mail doesn’t seem to have any way to add additional mail accounts.

Perhaps I missed something, or maybe drone is no longer possible for this configuration. I understand it’s not supported using the modern Outlook client. But I did use the drone feature successfully a long time ago in SpamSieve version 2.

• SpamSieve 3.2.2
• macOS, iOS and iPadOS 26.3.1

I changed to Quick Look earlier, but it didn’t do anything (because I didn’t also uncheck the Raw Source).

But they display as just a bunch of text if I am just navigating through them and not double-clicking. Is there a way to have them displayed without double-clicking? Maybe import them differently or adjust view settings?

This particular EagleFiler Library is a collection of emails that I receive from security cameras, and I would like to use the up/down navigation to browse through and look for particular things.

Thanks!

Would there be a way to trigger an app?

I really prefer drag install over old-style installers.

Cheers,

– Harald

Slinky:

I would like to add all these files to EagleFiler. Should I just File→Import Files… ?

You can, but it’s faster (and avoids duplicate copies) to just use Finder to move the files into the desired folder in your EagleFiler library.

Yes, EagleFiler will pick up the new files the next time you open the library or if you choose Scan for New Files.

Yes, EagleFiler will automatically detect if another app adds to the Finder tags.

I would like to add all these files to EagleFiler. Should I just File→Import Files… ?

In the future, I will save all new files to a Dropbox folder called CLAUDE, and will periodically use LLM to rename and sort files into appropriate folders inside that folder. How would you move the files from there into EagleFiler? Is it as easy as moving files from /Dropbox/CLAUDE/Cottage/Receipts/ into the /EagleFilerLibrary/Files/Cottage/Receipts

Next, I would like to have LLM apply tags to these files. Is it ok to make these types of modifications to existing EagleFiler records, or should I be asking LLM to put hashtags and metadata in the notes files instead?

Thanks for your wisdom, this is very exciting for me!

Frank

tansey:

Just to confirm the last step, you are say to uncheck the SpamSieve extension in Apple Mail.

Yes, uncheck SpamSieve in Mail’s settings:

Or, I guess it’s probably off by default if you had not specifically installed SpamSieve for Apple Mail.

Just to confirm the last step, you are say to uncheck the SpamSieve extension in Apple Mail.

I so missed having SpamSieve in Postbox after version 5.

Frank

I don’t know of a way to do this sort of filtering with MailMaven, and it doesn’t provide enough AppleScript access for us to write a script. I suggest sending the developers a feature request.

For now, one option would be to also run Apple Mail in the background so that it can filter these messages with SpamSieve:

• Select Enable spam filtering using Mail extension in SpamSieve.
• Uncheck Check inboxes for new messages not sent to Mail extension in SpamSieve.
• Check (and configure) Filter spam in other mailboxes in SpamSieve.
• Uncheck the Mail extension in Apple Mail.

I saw an AppleScript that solves this problem in Apple Mail, but I don’t think it works with Mailmaven.

Any solution to this situation?

is there a way to set up a time for files, after which they will deleted by ef?
Very often I do have documents I know, I may need for a few month (or I have to save by tax reasons for up to ten years), but I don’t want to keep them indefinety. Is there a way to set an expiration date (or time period, e.g. 2 years)?

Thanks in advance,

Tom

While debugging a script that needed to bring the correct EagleFiler window to the front, I discovered a useful diagnostic snippet that makes the two window contexts visible.

EagleFiler exposes browser windows in two scopes:

• Application level → all open browser windows
• Library document level → only the windows belonging to that library

This short script shows both lists:

tell application "EagleFiler"
	
	log "---- Application level windows ----"
	repeat with i from 1 to count of browser windows
		log ("App window " & i & ": " & name of browser window i)
	end repeat
	
	log "---- Library level windows ----"
	repeat with L in library documents
		log ("Library: " & name of L)
		tell L
			repeat with j from 1 to count of browser windows
				log ("   Lib window " & j & ": " & name of browser window j)
			end repeat
		end tell
	end repeat
	
end tell

Typical output might look like:

---- Application level windows ----
App window 1: Snippets Library
App window 2: Developer
App window 3: Snippets Library (4)

---- Library level windows ----
Library: Snippets Library.eflibrary
   Lib window 1: Snippets Library
   Lib window 2: Snippets Library (4)

Library: Developer.eflibrary
   Lib window 1: Developer

This immediately shows that:

application → browser windows = all windows
library document → browser windows = only that library's windows

Which means that to bring forward the main window for a library you can simply do:

tell application "EagleFiler"
	tell library document "Snippets Library.eflibrary"
		set browser window 1's index to 1
	end tell
end tell

This will save a lot of trial-and-error when dealing with multiple windows for the same library.

├─ library documents

│ └─ browser windows (for that library)

└─ browser windows (all windows in the app)

At the document level, browser window 1 is the first window that was opened for that library (i.e. the one without a number in its title).

The window level is controlled by the index property.

So if you want to bring forward the first window for a given library you could do something like this:

tell application "EagleFiler"
    tell library document "Snippets Library.eflibrary"
        set browser window 1's index to 1
    end tell
end tell

That part works fine, but I then need to bring the correct browser window for the target library to the front.

The complication is that EagleFiler allows multiple browser windows for the same library (e.g. Snippets Library and Snippets Library (4)). The AppleScript dictionary exposes library documents and browser windows, but there’s no direct way to say “bring the window for this library document to the front”.

Calling:

tell application "EagleFiler"

    open (file of tgtLib)

end tell

does bring the library forward, but if multiple windows are open for that library it can raise the wrong one (e.g. the (4) window).

After a lot of experimentation I ended up using a routine that:

1. Uses the short library name (e.g. Snippets Library)

2. Iterates through browser windows

3. Finds the window whose title matches that name (preferring the unnumbered one)

4. Sets its index to 1 to bring it to the front

In simple terms, the routine just searches the open browser windows and raises the one whose title matches the target library.

This works reliably, but it feels a bit indirect.

So my question is:

Is there a more direct AppleScript way to bring the browser window for a specific library document to the front?

For example something like:

tell library document "Snippets Library.eflibrary"

    make its browser window frontmost

end tell

—or any other recommended approach.

Thanks for any suggestions.

Many thanks. Folder selection in the source list was the aim. Eventually figured my solution was being thwarted by the default preference RevealRecordInParent=No.

Solved it by getting the folder’s record and using x-eaglefiler://open?library=…&recordGUID=. That highlights the folder in the source list and its records in the browser.

Cheers,

• When importing from Evernote, EagleFiler is better at handling attached files that have no filename extension and notes that contain only whitespace along with an attached file.
• Made some changes to try to prevent a crash when displaying a table cell.
• Fixed an internal error that could occur when checking whether a record needed to be indexed.

If you have not installed a beta version of EagleFiler before, first click here to enter the beta key. Thereafter, you can just launch EagleFiler or choose Software Update from the EagleFiler menu to auto-install the beta. EagleFiler will also notify you about future betas automatically. You can click here to stop receiving in-app notifications of beta versions.

Previously: Beta 4.

It’s also possible that some other filter is moving the messages out of the inbox before SpamSieve sees them. For more information, please see this page.

I get regular emails from several accounts, some of which get marked as GOOD, and some as SPAM.

I always train the SPAM ones as good.

Is there a way to mark all emails from an email address as always GOOD?

Thanks

Darren.

I didn’t realize that Tahoe has a MENU BAR pane, where you can turn on/off menubar items; I turned SS on there, then launched it, went into SS settings, re-enabled it, and it’s showing up.

User error.

longterm:

Well… no joy. I know that SpamSieve is running (see it in Activity Monitor); when I go back to settings/Advanced, the menubar option is OFF, even though I enabled it before.

What happens if you turn that option on?

You could also click here to enable some extra debug logging, and then restart SpamSieve and save a diagnostic report so that we can see what’s happening on your Mac.

eranthomson:

I turned off “Allow in Menu Bar” in System Settings > Menu Bar, but when I turned it back on, the menu bar icon does not come back. “Show menu bar” is ticked in SpamSieve prefs as shown in the enc screenshot.

Does it help if you toggle Show menu bar icon? Could you share a screenshot of your menu bar?

When importing from Evernote, if EagleFiler detects that a note has no text content (or just whitespace) it will extract the attachment and import it as a freestanding file (Image), so that you can view and work with it directly. If there is other text content, EagleFiler will import it as a rich text file with an attachment (RTF Document) to preserve whatever text you’d entered, too.

You normally wouldn’t end up with a plain Document, which is what happens when EagleFiler imports a freestanding file but doesn’t know what type of file it is.

Based on your screenshots, it looks like there’s something odd in your Evernote data, where the attachments are missing both the file extension (e.g. .png) and MIME type (e.g. image/png) so EagleFiler and macOS don’t know what kind of file they are. I think that’s why you’re getting just an icon (no thumbnail) for the attachments in the RTF as well as generic freestanding icons like for 68be522378bff0c2f0c0e2ffc6cbe620.

You may want to try cleaning things up in Evernote first—making sure there are filenames/types and removing extraneous text content so EagleFiler will import attachments as freestanding—and then import again.

I even removed a couple of menu bar items, but the menu doesn’t show up…