just forward (not store localy) has a bug?

[lfarkas]

suppose i've got a domain example.com in zimbra and would like to add an email address x@example.com for which i'd like to accept mails, but don't store localy the incoming emails just forward to another address x@another.com. how can i do that? we try to add an account x in example.com, the add a forwarding address x@another.com and in x's preferences we try to set "Don't keep a local copy of messages". it seems to working i.e. sending a mail from sender@example.com to x@example.com, then x@another.com got the mail and the mail is not stored in x@example.com.
BUT the sender@example.com who send the original mail got back a message from zimbra's postmaster as "Mail Delivery System <MAILER-DAEMON@example.com>".
why? how can i fix it? and what is the right way to do so?
thanks in advance.
yours.

in maillog we see this:
May 4 13:27:52 server postfix/smtpd[28264]: initializing the server-side TLS engine
May 4 13:27:52 server postfix/smtpd[28264]: connect from server.example.com[192.168.1.3]
May 4 13:27:53 server postfix/smtpd[28264]: 1BC7C6EC0698: client=server.example.com[192.168.1.3]
May 4 13:27:53 server postfix/cleanup[28268]: 1BC7C6EC0698: message-id=<15747292.31146742072030.JavaMail.root@server.e xample.com>
May 4 13:27:53 server postfix/qmgr[5559]: 1BC7C6EC0698: from=<sender@example.com>, size=497, nrcpt=2 (queue active)
May 4 13:27:53 server postfix/smtpd[28264]: disconnect from server.example.com[192.168.1.3]
May 4 13:28:03 server postfix/smtpd[28323]: initializing the server-side TLS engine
May 4 13:28:03 server postfix/smtpd[28323]: connect from localhost[127.0.0.1]
May 4 13:28:03 server postfix/smtpd[28323]: 773176EC06AD: client=localhost[127.0.0.1]
May 4 13:28:03 server postfix/cleanup[28268]: 773176EC06AD: message-id=<15747292.31146742072030.JavaMail.root@server.e xample.com>
May 4 13:28:03 server postfix/smtpd[28323]: disconnect from localhost[127.0.0.1]
May 4 13:28:03 server postfix/qmgr[5559]: 773176EC06AD: from=<sender@example.com>, size=1240, nrcpt=2 (queue active)
May 4 13:28:03 server postfix/smtp[28336]: 773176EC06AD: to=<x@another.com>, relay=sender.example.com[192.168.0.1], delay=0, status=sent (250 Ok: queued as
C7BEA37654A)
May 4 13:28:03 server postfix/error[28335]: 773176EC06AD: to=<x@example.com>, relay=none, delay=0, status=bounced (example.com)
May 4 13:28:04 server postfix/cleanup[28268]: 0065A6EC06AF: message-id=<20060504112804.0065A6EC06AF@server.example.com >
May 4 13:28:04 server postfix/qmgr[5559]: 0065A6EC06AF: from=<>, size=2822, nrcpt=1 (queue active)
May 4 13:28:04 server postfix/qmgr[5559]: 773176EC06AD: removed
May 4 13:28:04 server postfix/smtp[28269]: 1BC7C6EC0698: to=<x@another.com>, orig_to=<x@example.com>, relay=127.0.0.1[127.0.0.1], delay=11, status=sent (250 2.6.0 Ok, id=04341-01, from MTA([127.0.0.1]:10025): 250 Ok: queued as 773176EC06AD)
May 4 13:28:04 server postfix/smtp[28269]: 1BC7C6EC0698: to=<x@example.com>, relay=127.0.0.1[127.0.0.1], delay=11, status=sent (250 2.6.0 Ok, id=04341-01, from MTA([127.0.0.1]:10025): 250 Ok: queued as 773176EC06AD)
May 4 13:28:04 server postfix/qmgr[5559]: 1BC7C6EC0698: removed
May 4 13:28:04 server postfix/lmtp[28348]: 0065A6EC06AF: to=<sender@example.com>, relay=server.example.com[192.168.1.3], delay=0, status=sent (250 2.1.5 OK)
May 4 13:28:04 server postfix/qmgr[5559]: 0065A6EC06AF: removed

[lfarkas]

You'll probably need to post the headers for one of the zimbra guys to comment on, right-click/show original and post the details here.

A quick test on my system confirms that it gets delivered but does return a failed message if you don't keep a copy, if you uncheck the 'don't keep copy' it goes through without the failure message.

which header?
anywhy imho the bug is somewhere in the deliviery lookup.

[lfarkas]

some further testing it's turn out that zimbraPrefMailLocalDeliveryDisabled attrs only appear in /opt/zimbra/conf/ldap-transport.cf which is only used in postfix transport map. and if i test it with:
---------------------------
# /opt/zimbra/postfix/sbin/postmap -q "x@example.com" ldap:/opt/zimbra/conf/ldap-transport.cf
---------------------------
than it give no result, while other case it gives back an ltmp transport. which would be good, but
---------------------------
# /opt/zimbra/postfix/sbin/postmap -q "x@example.com" ldap:/opt/zimbra/conf/ldap-vam.cf
x@example.com, x@another.com
# /opt/zimbra/postfix/sbin/postmap -q "x@example.com" ldap:/opt/zimbra/conf/ldap-vmm.cf
x@example.com
---------------------------
imho this last two query shouldn't have to contains x@example.com. i.e. zimbra's the postfix ldap query settings are wrong in this case!
in /opt/zimbra/conf/ldap-vmm.cf it should have to be:
query_filter = (&(zimbraMailDeliveryAddress=%s)(zimbraMailStatus= enabled)(!(zimbraPrefMailLocalDeliveryDisabled=TRU E)))
in /opt/zimbra/conf/ldap-vmd.cf it should have to be:
query_filter = (&(|(zimbraMailDeliveryAddress=%s)(zimbraMailAlias =%s)(zimbraMailCatchAllAddress=%s))(zimbraMailStat us=enabled)(!(zimbraPrefMailLocalDeliveryDisabled= TRUE)))
or is it not the case?

[lfarkas]

after testing it and read again the postfix docs i find the conclusion. in this case:
- virtual_mailbox_maps should return empty result
- virtual_alias_maps should return just the forwarding address
the first requirement is easy just modify /opt/zimbra/conf/ldap-vmm.cf:
---------------------------
query_filter = (&(zimbraMailDeliveryAddress=%s)(zimbraMailStatus= enabled)(!(zimbraPrefMailLocalDeliveryDisabled=TRU E)))
---------------------------
but the second one is not so easy. currently it's not possible to solve this situation with zimbra's postfix's ldap conf file, i.e. in postfix's main.cf has this line:
virtual_alias_maps = ldap:/opt/zimbra/conf/ldap-vam.cf
but the assumption which has to be satisfied:
if ! zimbraPrefMailLocalDeliveryDisabled=TRUE then
query_filter = (&(|(zimbraMailDeliveryAddress=%s)(zimbraMailAlias =%s)(zimbraMailCatchAllAddress=%s))(zimbraMailStat us=enabled)(!(zimbraPrefMailLocalDeliveryDisabled= TRUE)))
result_attribute = zimbraMailDeliveryAddress,zimbraMailForwardingAddr ess,zimbraPrefMailForwardingAddress,zimbraMailCatc hAllForwardingAddress
else
query_filter = (&(|(zimbraMailDeliveryAddress=%s)(zimbraMailAlias =%s)(zimbraMailCatchAllAddress=%s))(zimbraMailStat us=enabled)(zimbraPrefMailLocalDeliveryDisabled=TR UE))
result_attribute = zimbraMailForwardingAddress,zimbraPrefMailForwardi ngAddress,zimbraMailCatchAllForwardingAddress
fi

but here not only the query_filter differes but the result_attribute is also! so you can't (or at least i can't) create such a query which satisfied this. therefore we should have to use two maps here in main.cf:
virtual_alias_maps = ldap:/opt/zimbra/conf/ldap-vam-local.cf ldap:/opt/zimbra/conf/ldap-vam-remote.cf
where the local is the first case of the if and remote is the else.

imho it's a bug in the current zimbra implementation and should have to be fixed. i open a bugzilla entry for this http://bugzilla.zimbra.com/show_bug.cgi?id=7474
i hope this'll be fixed soon.

[lfarkas]

the current situation is even wors! since zimbra restart rewrite main.cf so my changes are lost after the first restart:-(((
is there any solution?

[KevinH]

Looking at the log above you may have a mail loop. Are you sure X@another doesn't have any forwarding or redirect rules/settings?

[lfarkas]

Looking at the log above you may have a mail loop. Are you sure X@another doesn't have any forwarding or redirect rules/settings?

have you try it? the reconstruction steps:
- simple create a new account test
- add a forward address to test
- set "Don't keep a local copy of messages"
- try to send a mail to test
and you'll got it!
i already show the solution above since there is no simple ldap query for this. therefore do:
zmlocalconfig -e "postfix_virtual_alias_maps=ldap:/opt/zimbra/conf/ldap-vam-local.cf ldap:/opt/zimbra/conf/ldap-vam-remote.cf"
and put the above two different ldap query to these files, restart zimbra and it's working!
BUT still it's a bug! without it the "Don't keep a local copy of messages" not working!

[KevinH]

Please file it in bugzilla then.

[lfarkas]

http://bugzilla.zimbra.com/show_bug.cgi?id=7474

[PNE]

Yesterday I set my first forward-and-not-store account and immediately ran into the same problem. Didn't try lfarkas's workaround yet. Is there a chance for quick fix? Lfarkas is right, with this bug is this feature not usable at all.