LO68627: JOURNALLED MESSAGES ARE GOING DEAD WHEN USING MAIL-IN DB CONFIG

APAR status

• Closed as fixed if next.

Error description

• Error Description￘
  To reproduce the issue, you need to set up mail journalling on
  your Domino server.
  
  - Configure journalling to send to a mail-in database.
  - Populate the mail-in database with an internet address
  
  In this particular instance, the customer has a listing of
  Traveller users that are listed in the config doc under the
  field:
  
  Router/SMTP -> Restrictions and Controls -> SMTP Outbound
  controls ->
  
  Outbound Sender Controls
  Allow messages only from the following Internet addresses to be
  sent to the Internet:
  
  If the field is blank the messages are routed to the mail-in
  database address but, the Traveller users that were listed can
  not longer send outbound through the SMTP.
  
  If we populate the field with the traveller Internet addresses,
  the journaled messages fail with the error:
  
  04/06/2012 01:50:14 PM  Router: Message 0061F7DD from
  lisaMarie.michael@gmail.com state changing to DEAD. Reason:
  Router: Unable to deliver message to journal db [%s], marked as
  DEAD
  > 04/06/2012 01:50:26 PM  Opened session for notes admin/domain
  (Release 8.5.3)
  
  The messages end up as dead messages in the mail.box.
  
      SERVERNAME Mailbox  Dead Message
  
  From: lisaMarie.michael@gmail.com
  Recipients: lisa_michael@DOMAIN.com
  Subject:
  Date: 01:50:04 PM Today
  
  Failure Report
  Failure Reason: Router: lisaMarie.michael@gmail.com is
  restricted from sending mail through server xxxx/xxxx
  Dead Failure Reason: Router: Unable to deliver message to
  journal db [%s], marked as DEAD
  
  
  If the messages are sent from a notes client, this
  configuratoin will work. If the messages are sent from a POP3
  or IMAP mail client, messages end up dead.
  
  The customer wants the abilty to use the internet address for
  remote journalling and have her Traveler users have the ability
  to route through this server.
  

Local fix

• Local Fix￘
  none
  

Problem summary

• This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# LMIL8T4R28.
  This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R802 PSN

     UP