D HCL Domino Daily
All Posts Search Class Map About
A 文
  • Domino Server Security +2
    Domino's eMudhra Certificate Alert: What the 9.1 Really Means, and Which Trust Store to Clean

    In late October HCL published a security bulletin that lists Domino Server as affected, with a CVE carrying a 9.1 CVSS. But this isn't a bug in Domino's code — it's that the private keys of a set of eMudhra intermediate CAs can be recovered, and those CAs are trusted by Java's trust store and by the trust chain Domino uses for outbound connections. Three things actually matter: how to read that 9.1 (Oracle says 9.1, Red Hat says 6.8), whether your environment is really exposed (most servers trust these CAs in the bundled Java cacerts, not in certstore.nsf), and which certificates to pull from which trust stores. This lays out how CVE-2026-91403 / 114820 / 108014 map together, the affected versions, the removal list, and how to verify.

    2026.11.05 →
  • Java
    Opening a Notes Database in Java: Many Paths, One Trap

    In LotusScript, session.GetDatabase returns Nothing when the open fails, and your reflex Is Nothing check covers you. The same line in Java does NOT return null — getDatabase hands you a Database object anyway, one whose isOpen is false, a shell pointing at a database that isn't there. This covers how to get and hold a Database handle in Java: where it comes from, the open paths (getCurrentDatabase / getDatabase / DbDirectory), how to catch the 'returned an object but didn't open' trap, and where Database sits in the recycle parent-child chain — recycle it too early and the Views and Documents you're holding die with it.

    2026.11.05 →
  • XPages SSJS
    XPages Has Two Documents — Don't Edit the Wrong One

    When you write document1 in XPages SSJS, you're holding the data-source wrapper (NotesXspDocument). But document1.getDocument() hands you a different object — the back-end NotesDocument. Both point at the same note, but they're two APIs: the wrapper uses getValue / setValue, the back end uses getItemValue / replaceItemValue, and each has its own save. This piece is about the back-end one: how to get it in SSJS, what it does (replaceItemValue / computeWithForm / save / remove / universalID), where the line between it and the wrapper sits, and why saving on both sides spawns a save-conflict document.

    2026.11.04 →
  • XPages SSJS
    Three Kinds of Date in XPages — You Have to Know Which One You're Holding

    The thing that bites you with dates in XPages SSJS isn't a method you can't call — it's not noticing that three different 'dates' are in play at once: the back-end NotesDateTime, the Java-layer java.util.Date, and JavaScript's own Date. What you read from a document is a NotesDateTime; what @Today hands you might be something else, and putting the wrong one in the wrong place throws or stores a bad value. This covers building a NotesDateTime in SSJS (session.createDateTime), converting between the three types (toJavaDate), the common methods (adjustDay / setNow / timeDifference / convertToZone), and the two classic traps — 'Today has no time' and '@Today isn't necessarily a NotesDateTime'.

    2026.11.03 →
  • Domino Server Admin
    Domino Message Disclaimers: Why to Add Them Client-Side

    Many organizations want a legal disclaimer appended to every outgoing message. Domino does this built in, but the setup spans two documents — and there's a real trap: adding it on the server breaks messages that are already signed or encrypted. This piece covers how the two documents split the work (the disclaimer text, position, and format live on a mail policy settings document; the server on/off switch is on the Configuration Settings document's Router/SMTP → Message Disclaimers tab), that disclaimers are added only to outgoing SMTP messages (not incoming), that the position can be Append or Prepend, that they can be added by the client, the server, or both, and the key point: the server adds the disclaimer after the message is signed, so it breaks S/MIME signatures and encryption — HCL recommends using the Notes client wherever possible (the client adds it before signing, so the signature stays valid), which matters especially where signing is required or where you send multibyte character sets like Chinese. Finally: mail policy changes are applied by AdminP (every 12 hours by default, or tell adminp process mail policy to apply now).

    2026.11.02 →
  • Domino Server Admin
    Domino Message Tracking: Where Did That Message Actually Go?

    A user says 'the message I sent didn't arrive' — how do you find where it actually went, where it's stuck, or whether it ever left? That's message tracking. It records each message's handling trail — who sent it, where it went, what state it's in — so you can trace a single message in the Message Tracking Center. It's different from last time's mail journaling: journaling keeps a full copy of the message, tracking keeps the metadata about where it went. This piece covers how to turn it on (the Configuration Settings document's Router/SMTP → Message Tracking, off by default), how the MTC (Mail Tracking Collector) task gathers the tracking logs the Router produces into MTSTORE.NSF, the options worth knowing (collection interval default 15 minutes, logging subjects off by default for privacy, who's allowed to track defaulting to LocalDomainServers, retention controlled by replication settings), and the tell mtc console commands.

    2026.11.01 →
  • Domino Server Admin +1
    Don't Let Domino Become an Open Relay: Inbound SMTP Controls

    An open relay is a misconfigured SMTP server that relays mail from anyone to anywhere — spammers love it as a free waystation, and the result is your IP on a blocklist and even your legitimate mail not getting out. Domino actually blocks external relaying by default, but you should understand how. This piece covers the inbound relay controls' four fields (allow/deny × destination domain / originating host), how allow and deny interact (allow takes precedence, but an identical entry in both lists has deny win), that Domino checks the original sender, not just the last hop, the enforcement scope (by default only hosts outside the local Internet domain, authenticated users exempt by default, relaxing is not recommended), the add-on DNS blacklists (DNSBL: log only / log and tag / log and reject) and private blacklists / DNS whitelists, and the reverse-DNS check (no PTR, no mail accepted).

    2026.10.31 →
  • Domino Server Admin
    Domino Mail Quota: What Happens When a Mailbox Is Over Quota

    You set a quota on each mailbox and assume mail stops when it's full? Not necessarily — Domino's default is 'Deliver anyway,' so a quota alone delivers regardless. What actually decides what happens to new mail for a full mailbox is the over-quota enforcement you choose separately. This piece covers the two limits (a hard quota and an optional warning threshold, which you can only set once a quota exists), when the Router compares size (on each delivery), the three enforcement options (Deliver anyway, Non delivery to originator which returns an NDR, and Hold mail and retry which holds mail in MAIL.BOX until space frees and returns it after a default one-day expiration), the Hold-and-retry sub-options (deliver what fits vs hold everything, maximum messages to hold per user), and an easily missed detail: the default size calculation counts white space, so deleting messages doesn't free quota right away — the used-space method is more immediate and recommended with transaction logging.

    2026.10.30 →
  • Domino Server Admin +1
    Domino Mail Journaling: Capturing Mail for Compliance, and Two Encryption Traps

    Audit and compliance often require keeping a copy of every message in and out. Domino does this built in — mail journaling: as the router delivers a message normally, it also copies it into a dedicated database. This piece covers how to turn it on (off by default, enabled on the Router/SMTP → Advanced → Journaling tab of the Configuration Settings document), which messages to journal (all of them, or selectively via the previous piece's Journal this message mail rule), where the copy goes (a local database, MAILJRN.NSF, created automatically, or a mail-in database that must already exist), and two easy-to-hit encryption traps: local journaling encrypts with the public key of the 'Encrypt on behalf of user' and encrypts the Subject by default, so the Subject column is blank in the journal's views; mail-in journaling is NOT auto-encrypted — you have to enable encryption on the Mail-in database document's Basics tab yourself. Plus: a message already encrypted for its recipients isn't re-encrypted with the journal key, and the database is hidden from the Open Database dialog by default.

    2026.10.29 →
‹ Previous1234…25Next ›
Powered by Astro and GitHub Actions