Wietse Venema via Postfix-users <[email protected]> wrote: > Michael Grimm via Postfix-users: >> Wietse Venema via Postfix-users <[email protected]> wrote: >>> Michael Grimm via Postfix-users:
>>>> Until now, I failed in getting the following mappings done: >>>> >>>> (1) [email protected] >>> [email protected] >>> >>> Which of the above email addresses is an original SMTP RCPT TO >>> address? >> >> (1) received from an webmail account, sent to [email protected] > > which of these two addresses is an original SMTP RCPT TO, which > one is derived, how is the address derived? Sorry, but I do have to admit that I don't understand your question. This is all from that receiving mail I find in my logfile: ############################# Feb 7 14:54:33 mail dovecot[7350]: imap-login: Login: user=<mike>, method=PLAIN, rip=2003:fb:4f2f:de01:c001:12c0:a6d1:4824, lip=fd00:a:a:a::1, mpid=29179, TLS, session=<Pk7ZPjxKYvggAwD7Ty/eAcABEsCm0Ugk> Feb 7 14:54:33 mail rspamd[7584]: <7f0452>; proxy; finalize_item: slow asynchronous rule: DCC_CHECK(356): 4683.46 ms; no idle timer is needed Feb 7 14:54:33 mail rspamd[7584]: <7f0452>; proxy; rspamd_task_write_log: id: <1770472402086.174481.82ba4ea7042bbcefd4717d27e6cdefe5d1191...@spica.telekom.de>, qid: <4f7XWS4zHyz1XZP>, ip: 194.25.134.83, from: <[email protected]>, (default: F (no action): [2.19/10.00] [RCVD_UNAUTH_PBL(2.00){},FROM_DN_EQ_ADDR(1.00){},DMARC_POLICY_ALLOW(-0.50){t-online.de;none;},R_SPF_ALLOW(-0.20){+ip4:194.25.134.80/28;},MIME_GOOD(-0.10){multipart/alternative;text/plain;},MX_GOOD(-0.01){},ARC_NA(0.00){},ARC_SIGNED(0.00){ellael.org:s=dkim:i=1;},ASN(0.00){asn:3320, ipnet:194.25.0.0/16, country:DE;},FREEMAIL_ENVFROM(0.00){t-online.de;},FREEMAIL_FROM(0.00){t-online.de;},FREEMAIL_REPLYTO(0.00){t-online.de;},FROM_EQ_ENVFROM(0.00){},HAS_REPLYTO(0.00){[email protected];},MIME_TRACE(0.00){0:+;1:+;2:~;},MISSING_XM_UA(0.00){},PREVIOUSLY_DELIVERED(0.00){[email protected];},RCPT_COUNT_ONE(0.00){1;},RCVD_COUNT_THREE(0.00){4;},RCVD_TLS_LAST(0.00){},RECEIVED_SPAMHAUS_PBL(0.00){91.46.90.123:received;},REPLYTO_EQ_FROM(0.00){},RWL_MAILSPIKE_POSSIBLE(0.00){194.25.134.83:from;},R_DKIM_NA(0.00){},TO_DN_EQ_ADDR_ALL(0.00){},TO_MATCH_ENVRCPT_ALL(0.00){}]), len: 1837, time: 4749.868ms, dns req: 62, digest: <1f1c35e42ebe9cd897ae3131d4bc8b70>, rcpts: <[email protected]>, mime_rcpts: <[email protected]> Feb 7 14:54:33 mail rspamd[7584]: <7f0452>; proxy; rspamd_protocol_http_reply: regexp statistics: 17870 pcre regexps scanned, 2 regexps matched, 13621 regexps total, 34 regexps cached, 298.50KiB scanned using pcre, 298.50KiB scanned total Feb 7 14:54:33 mail postfix/qmgr[29095]: 4f7XWS4zHyz1XZP: from=<[email protected]>, size=2275, nrcpt=2 (queue active) Feb 7 14:54:33 mail postfix/smtpd[29172]: disconnect from mailout07.t-online.de[194.25.134.83] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Feb 7 14:54:33 mail dovecot[7350]: lmtp(29182): Connect from local Feb 7 14:54:33 mail dovecot[7350]: lmtp(mike)<29182><ELWUHhlEh2n+cQAAOoNhLw>: save: box=INBOX, uid=43670, msgid=<1770472402086.174481.82ba4ea7042bbcefd4717d27e6cdefe5d1191...@spica.telekom.de>, flags=() Feb 7 14:54:33 mail dovecot[7350]: lmtp(mike)<29182><ELWUHhlEh2n+cQAAOoNhLw>: sieve: msgid=<1770472402086.174481.82ba4ea7042bbcefd4717d27e6cdefe5d1191...@spica.telekom.de>: stored mail into mailbox 'INBOX' Feb 7 14:54:33 mail dovecot[7350]: lmtp(29182): Disconnect from local: Logged out (state=READY) Feb 7 14:54:33 mail postfix/lmtp[29180]: 4f7XWS4zHyz1XZP: to=<[email protected]>, orig_to=<[email protected]>, relay=mx1.enfer-du-nord.net[private/dovecot-lmtp], delay=4.9, delays=4.8/0.01/0.02/0.01, tls=none, dsn=2.0.0, status=sent (250 2.0.0 <[email protected]> ELWUHhlEh2n+cQAAOoNhLw Saved) Feb 7 14:54:33 mail postfix/lmtp[29181]: 4f7XWS4zHyz1XZP: to=<[email protected]>, relay=10.0.1.11[10.0.1.11]:24, delay=4.9, delays=4.8/0.01/0/0.05, tls=none, dsn=5.0.0, status=bounced (host 10.0.1.11[10.0.1.11] said: 550 Recipient <[email protected]> FAIL (in reply to RCPT TO command)) Feb 7 14:54:33 mail postfix/bounce[29184]: 4f7XWS4zHyz1XZP: sender non-delivery notification: 4f7XWY3tkZz1XZQ Feb 7 14:54:33 mail postfix/qmgr[29095]: 4f7XWS4zHyz1XZP: removed Feb 7 14:54:33 mail postfix/cleanup[29177]: 4f7XWY3tkZz1XZQ: message-id=<[email protected]> Feb 7 14:54:33 mail postfix/cleanup[29177]: 4f7XWY3tkZz1XZQ: removed (canceled) ############################# Does that answer your questions? >>>> (2) [email protected] >>> [email protected] > > Which of these two is addresses is an original SMTP RCPT TO, which > one is derived, how is the address derived? see above >> (2) is derived by recipient_bcc_maps: >> /^(.*)@ellael\.org$/ ${1}@dbmail.ellael.org > > Mapping (2) does not produce [email protected]. Yes, that's been my problem. > Unfortunately, recipient_bcc_maps accepts only one address. > > virtual_alias_mapping happens after recipient_bcc_maps, so you could > add the missing mapping there, but that would require one rule per > recipient. > > If you end up with one virtual alias per recipient, then you might > just as well ditch recipient_bcc_maps and use virtual aliases only: > > in: [email protected] > out: [email protected], [email protected] That's the way I went in the meantime. I extended my virtual_alias_maps accordingly and now, mails are diliverd to both LMTP serves. > While devising a solution I mssed that you are aliasing > all recipients to a different domain. Sorry, I should have been more precise on that. Just out of curiosity: How much of an effort would it be to implement that … virtual_transport = lmtp:unix:private/dovecot-lmtp, lmtp:[10.0.2.11]:24 … delivers to both instead of https://www.postfix.org/lmtp.8.html): | The Postfix SMTP client supports multiple destinations separated by comma or whitespace | (Postfix 3.5 and later). Each destination is tried in the specified order. Please, don't get me wrong. This is *not* a feature request, it is just a question out of curiosity of mine. Thanks again for all your help in helping me get my issue settled, Michael _______________________________________________ Postfix-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
