Port 1352

If you've encountered the following error message:

"You cannot enable your out-of-office notification because your mailbox has exceeded its quota.  Choose Tools > Quota Information for quota details and tips on decreasing your mailbox size."

...and you don't have a quota set on the database that is complaining of the problem...

It's an ACL issue.

-

Credit to Obinna for posting the answer in the ND8 Forum.

Technote 1266681 explains the issue and resolution, but it does not list the speciffic error message, so I was only able to find the technote after learning the solution.

-

Note that this problem only occurs when Out of Office runs as an agent; yet another good reason to configure Out of Office to run as a Service.

... automatically preventing the buildup of performance-robbing deposits.


Haven't seen this one before.  Happened while using Admin client version 8.0.2.  Hooray for increased detail in error messages.

I had to chuckle when I encountered the following when perusing this topic in the Sametime Info Center.  Good to know I'm not the only one that has thoughts like that when reviewing the documentation (or lack thereof).

You are probably already familiar with the advanced database property, "Don't allow simple search," introduced in Domino 8.  However, you might not realize that it is one of a few database properties that does not replicate.  So, if your intent is to set that property for any additional replica(s), you'll need to set it there, too.

According to this technote, the following database properties do not replicate (those marked with "**" are a special case).

BASICS TAB    
Replication settings
Encryption settings
Disable background agents for this database
   
DESIGN TAB    
List in Database Catalog**
Show in 'Open Database' dialog**
Do not mark modified documents as unread
Include in multidb indexing**
   
ADVANCED TAB - don't get beat by the beanie
Don't allow simple search (release 8)
Don't overwrite free space
Disable transaction logging
Don't allow headline monitoring

 ** It has been discovered that, in some cases, these three particular design settings do not replicate. This issue has been reported to Quality Engineering as SPR #GAPN79BQ3F and is under investigation. The issue has been reproduced in Domino 6.5.6 and 8.x.

One of these things is not like the others... 

Can you spot the difference?  I knew that you could.

Yep, X.PC goes the way of the Dodo in Notes/Domino 8.5. 

Here's how the Admin help sums it up:
Support for direct dialup modem (X.PC) connections is available only in releases of Domino earlier than release 8.5. You may continue to use Domino Administrator 8.5 to configure and maintain direct dialup modem support, but only on servers running pre-8.5 releases.

So, those of you out there that are still relying on XPC to connect users to servers or servers to servers (yes, I confess I was forced to connect two servers via dialup as a long term (and long distance) solution once myself  *shudder*), you'll need to make a few changes before your 8.5 rollout.

PS.  I almost titled this entry, Beep beep beep beep beep beep beep boop, WeeeeRRRR waaaaaa crrrrrrrrrrr, but my modemese is a little rusty. 

By definition, Sametime Entry 8.0.x only permits connections from a limited scope of client types.  If you are piloting Notes 8.5 (or are, like most Mac OS X users I've encountered, using Notes 8.5 beta in production) you'll need to append ",1333" to the VPS_ALLOWED_LOGIN_TYPES= line in the Sametime Entry server's sametime.ini.

Without this modification, the integrated client will refuse to connect, generating a somewhat misleading message: "Unable to access Sametime.  Please try again later."

Perhaps the error message will eventually be improved to something like: "The Lotus Notes version you are using is not permitted to use the specified Sametime server."