On the December 18, 2006, the DNS blacklist ORDB.org (relays.ordb.org) has been shut down.

 

Quote from http://www.ordb.org/news/?id=38:

"It's been a case of a long goodbye as very little work has gone into maintaining ORDB for a while. Our volunteer staff has been pre-occupied with other aspects of their lives. In addition, the general consensus within the team is that open relay RBLs are no longer the most effective way of preventing spam from entering your network as spammers have changed tactics in recent years, as have the anti-spam community.”

 

As of March 25, 2007, ORDB.org started confirming all requests done to the blacklist, which will result in the incorrect blocking of emails.

If you hav

On the December 18, 2006, the DNS blacklist ORDB.org (relays.ordb.org) has been shut down.

 

Quote from http://www.ordb.org/news/?id=38:

"It's been a case of a long goodbye as very little work has gone into maintaining ORDB for a while. Our volunteer staff has been pre-occupied with other aspects of their lives. In addition, the general consensus within the team is that open relay RBLs are no longer the most effective way of preventing spam from entering your network as spammers have changed tactics in recent years, as have the anti-spam community.”

 

On the December 18, 2006, the DNS blacklist ORDB.org (relays.ordb.org) has been shut down.

 

Quote from http://www.ordb.org/news/?id=38:

"It's been a case of a long goodbye as very little work has gone into maintaining ORDB for a while. Our volunteer staff has been pre-occupied with other aspects of their lives. In addition, the general consensus within the team is that open relay RBLs are no longer the most effective way of preventing spam from entering your network as spammers have changed tactics in recent years, as have the anti-spam community.”

 

As of March 25, 2007, ORDB.org started confirming all requests done to the blacklist, which will result in the incorrect blocking of emails.

If you hav

On the December 18, 2006, the DNS blacklist ORDB.org (relays.ordb.org) has been shut down.

 

Quote from http://www.ordb.org/news/?id=38:

"It's been a case of a long goodbye as very little work has gone into maintaining ORDB for a while. Our volunteer staff has been pre-occupied with other aspects of their lives. In addition, the general consensus within the team is that open relay RBLs are no longer the most effective way of preventing spam from entering your network as spammers have changed tactics in recent years, as have the anti-spam community.”

 

As of March 25, 2007, ORDB.org started confirming all requests done to the blacklist, which will result in the incorrect blocking of emails.

If you have checks against relays.ordb.org configured in your mail server or spam filtering software (example Lotus Domino), please stop querying the list immediately.




Read more about what's new in Lotus Notes and Domino V8 on the new IBM Website: http://www.ibm.com/developerworks/lotus/library/notes8-new/Read more about what's new in Lotus Notes and Domino V8 on the new IBM Website: http://www.ibm.com/developerworks/lotus/library/notes8-new/




IBM released today the public beta version from Lotus Notes/Domino 8. The public beta is designed to offer such features as a choice in office productivity tools and the ability to group related email messages together based on conversation threads, under Lotus Notes/Domino 8.

IBM expects its Lotus Notes/Domino 8 program to be available in the middle of this year. For more infos visit the IBM Website here .




If you install a fixpack or a hotfix for a domino server running on Linux/Unix you might see the following message:

You must create the environment variable NUI_NOTESDIR as path of the directory
that contains notes/latest. E.g., for the default path /opt/lotus/notes/latest
NUI_NOTESDIR=/opt/lotus
export NUI_NOTESDIR


To fix this issue on a domino server running on Debian (yes unsupported ;-) ) you could for example edit the:

/etc/profile

via "nano /etc/profile"

and add the line:

export NUI_NOTESDIR=<path_to_lotus>

where <path_to_lotus> is the full path to the 'lotus' directory for the server to receive the hotfix installation

for example

export NUI_NOTESDIR=/opt/ibm/lotus

After that relogin and the issue is solved.




You can use a desktop policy settings document to add or set NOTES.INI variables for Notes client users. This is an easy way to assign NOTES.INI variables to all Notes client users, or to a specific subset of Notes client users, at one time. You can also use desktop policy settings documents to set field values in Location documents for users.

for more infos see the IBM Technote 1196837