On Sat, May 22, 2010 at 01:05:12AM -0400, Mike A. Leonetti wrote:
> I posted here before but here is a continuation (in a different issue)
> of what's going on.
>
> All aliases are in LDAP. An e-mail is looked up with virtual_alias_maps
> and the username (based on the way webmin has it) and not the user's
> e-mail.
User names are NOT email addresses. The virtual alias table translates
input RFC 2821 forward-path addresses, to one or more RFC2821 forward-path
addresses.
Bare user names are understood by Postfix only as a short-hand for a
local email address obviating the need to hard-code @$mydomain in
various tables when the output is a local (as in $mydestination)
address.
If your LDAP table returns bare non-local addresses, fix the table.
If your LMTP server expects bare user-names with no @domain part, it is
a non-compliant LMTP server, since LMTP requires the same address syntax
as SMTP.
> But, in the end I would really like to deliver it using lmtp (see the
> virtual_transport line) to Zarafa which is its destination, and every
> time it tries to deliver it it delivers it as
> "username-domain....@mydomain.com" which obviously doesn't exist.
>
> So my question is, is it possible to clean out the @$myorigin or
> convince it not to append it so I can then just pass it through LMTP to
> Zarafa?
Your configuration is wrong. If Zarafa's LMTP server expects bare
RCPT TO:<user> comands, fix that software, otherwise rewrite to the
domain that this software considers local (to it).
--
Viktor.
P.S. Morgan Stanley is looking for a New York City based, Senior Unix
system/email administrator to architect and sustain our perimeter email
environment. If you are interested, please drop me a note.
