1 Topic by Zwiebelhacker (edited by Zwiebelhacker 2022-04-26 21:25:16)

  • Zwiebelhacker
  • Member
  • Offline
  • Registered: 2019-04-02
  • Posts: 6

Topic: Mail Forwarding doesnt work

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.5.2
- Deployed with iRedMail Easy or the downloadable installer? Downloadable Installer
- Linux/BSD distribution name and version: Debian 11 Bullseye
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP 
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? Yes and No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Hello,

after a fresh Installation of our IredMail Server, the mail-forwarding feature doesnt work anymore.
The forwarding address is set via IredAdmin-Pro. https: //mailserver/iredadmin/profile/user/forwarding/user@domain.com.

- Enable mail forwarding (is checked)
- Save a copy in mailbox (not checked)
- Forward mails to address (forwarding-address)

From /var/log/mail.log

Apr 26 15:09:26 mx01 postfix/smtpd[3363]: proxy-accept: END-OF-MESSAGE: 250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 4Knhzp2D2Pz1ynl; from=<XXX@web.de> to=<XXX@mailserver.com> proto=ESMTP helo=<mout.web.de>
Apr 26 15:09:26 mx01 postfix/pipe[3392]: 4Knhzp2D2Pz1ynl: to=<XXX@mailserver.com>, relay=dovecot, delay=0.05, delays=0.01/0.01/0/0.04, dsn=2.0.0, status=sent (delivered via dovecot service)

The E-Mails are stored in the Mailbox but are not forwarded.

Can you give me any hints?

Best Regards
Zwiebelhacker

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,082

Re: Mail Forwarding doesnt work

Zwiebelhacker wrote:

Apr 26 15:09:26 mx01 postfix/smtpd[3363]: proxy-accept: END-OF-MESSAGE: 250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 4Knhzp2D2Pz1ynl; from=<XXX@web.de> to=<XXX@mailserver.com> proto=ESMTP helo=<mout.web.de>

What does "proxy-accept:" mean here? iRedMail doesn't have program which produces this message.

You can do a quick testing with commands below (Replace <email> by the real email address which has forwarding address):

cd /etc/postfix/ldap/
for i in $(ls *cf); do echo $i; postmap -q "<email>" ldap:./$i; done

3 Reply by Zwiebelhacker

  • Zwiebelhacker
  • Member
  • Offline
  • Registered: 2019-04-02
  • Posts: 6

Re: Mail Forwarding doesnt work

ZhangHuangbin wrote:
Zwiebelhacker wrote:

Apr 26 15:09:26 mx01 postfix/smtpd[3363]: proxy-accept: END-OF-MESSAGE: 250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 4Knhzp2D2Pz1ynl; from=<XXX@web.de> to=<XXX@mailserver.com> proto=ESMTP helo=<mout.web.de>

What does "proxy-accept:" mean here? iRedMail doesn't have program which produces this message.


You can do a quick testing with commands below (Replace <email> by the real email address which has forwarding address):

cd /etc/postfix/ldap/
for i in $(ls *cf); do echo $i; postmap -q "<email>" ldap:./$i; done

I guess thats because we use a "Postfix Before-Queue Content Filter".

Thats the result of the code:

catchall_maps.cf
forwarding@mail.address
recipient_bcc_maps_domain.cf
recipient_bcc_maps_user.cf
relay_domains.cf
sender_bcc_maps_domain.cf
sender_bcc_maps_user.cf
sender_dependent_relayhost_maps_domain.cf
sender_dependent_relayhost_maps_user.cf
sender_login_maps.cf
forwarding@mail.address
transport_maps_domain.cf
transport_maps_user.cf
virtual_alias_maps.cf
forwarding@mail.address
virtual_group_maps.cf
virtual_group_members_maps.cf
adresswhichshouldbeforwarded@xxx.com
virtual_mailbox_domains.cf
virtual_mailbox_maps.cf

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,082

Re: Mail Forwarding doesnt work

Mail forwarding, aliases, etc are not work in before-queue state because the addresses haven't been expanded to final destination addresses yet.