The protocol IMAP has no feature translating mailaddresses! It's something like a filesystem for your mailbox.
To solve that problem, you have to avoid users from using Netware usernames for addressing. There is no other way to solve it.
The way I've gone years ago is to install a SMTP-Configuration for my Pegasus users. If in place, two things happen. The module SMTPS in Mercury shows up on such a mail:
Connection from 129.217.xxx.xxx, Tue Jul 21 07:39:10 2015
EHLO xxx.xxx.tu-dortmund.de
STARTTLS
EHLO xxx.xxx.tu-dortmund.de
MAIL FROM:<xxx.xxx@xxx.tu-dortmund.de> SIZE=1840
RCPT TO:<netwareuser>
QUIT
Seems normal, but SMTPS denies receipt (the protocol entry DATA is missing, which indicates SMTPS to accept the mail) and Pegasus produces an internal errormessage including the line:
553 Invalid RFC821 mailbox specification.
So your local users can't send with netware usernames any more.
bye Olaf
<p>The protocol IMAP has no feature translating mailaddresses! It's something like a filesystem for your mailbox.</p><p>To solve that problem, you have to avoid users from using Netware usernames for addressing. There is no other way to solve it.</p><p>The way I've gone years ago is to install a SMTP-Configuration for my Pegasus users. If in place, two things happen. The module SMTPS in Mercury shows up on such a mail:</p><blockquote><p>Connection from 129.217.xxx.xxx, Tue Jul 21 07:39:10 2015
EHLO xxx.xxx.tu-dortmund.de
STARTTLS
EHLO xxx.xxx.tu-dortmund.de
MAIL FROM:&lt;xxx.xxx@xxx.tu-dortmund.de&gt; SIZE=1840
RCPT TO:&lt;netwareuser&gt;
QUIT</p></blockquote><p>Seems normal, but SMTPS denies receipt (the protocol entry DATA is missing, which indicates SMTPS to accept the mail) and Pegasus produces an internal errormessage including the line:</p><blockquote><p>553 Invalid RFC821 mailbox specification.</p></blockquote><p>&nbsp;So your local users can't send with netware usernames any more.</p><p>bye &nbsp; Olaf</p><p>&nbsp;</p>