New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E-mails are forwarded twice when e-mail account exists #448

Closed
utrenkner opened this Issue Jun 9, 2017 · 10 comments

Comments

Projects
None yet
4 participants
@utrenkner

utrenkner commented Jun 9, 2017

Summary

On e-mails, which have a real account and a forwarding address, each e-mail is forwarded twice. E-mail addresses with only a forwarding address and no account do not show this behaviour.

System information

  • Froxlor version: We use your Froxlor packages for Debian Wheezy (currently 0.9.38.7-1+wheezy1)
  • Web server: Apache 2.2
  • OS/Version: GNU/Linux Debian Wheezy

Steps to reproduce

  1. Create a client's e-mail account in Froxlor
  2. Add a forwarding address
  3. Send test e-mail to the newly created account in step 1
  4. Check the account from step 2, to which e-mails are forwarded

Expected behavior

  1. Each e-mail to the newly created account in step 1 appears once in the account in step 2, to which e-mails are forwarded

Actual behavior

  1. Each e-mail to the newly created account in step 1 appears twice in the account in step 2, to which e-mails are forwarded

We have noticed this problem already a long time ago (one or two years), but found only now the trigger (having forwarding + a real account for the original e-mail address). Back then it was not such a big issue, because we only used it temporarily during vacation times. Now we need a permanent solution with e-mail account + forwarding.

@d00p

This comment has been minimized.

Show comment
Hide comment
@d00p

d00p Jun 9, 2017

Member

Are you using amavisd-new additionally?

Member

d00p commented Jun 9, 2017

Are you using amavisd-new additionally?

@utrenkner

This comment has been minimized.

Show comment
Hide comment
@utrenkner

utrenkner commented Jun 9, 2017

No.

@d00p

This comment has been minimized.

Show comment
Hide comment
@d00p

d00p Jun 9, 2017

Member

any other tool/filter?

Member

d00p commented Jun 9, 2017

any other tool/filter?

@bjoern-tantau

This comment has been minimized.

Show comment
Hide comment
@bjoern-tantau

bjoern-tantau Nov 16, 2017

I have the same problem with Debian Jessie, Postfix and Dovecot. I have Sieve enabled but it also happens with Sieve disabled.

bjoern-tantau commented Nov 16, 2017

I have the same problem with Debian Jessie, Postfix and Dovecot. I have Sieve enabled but it also happens with Sieve disabled.

@bjoern-tantau

This comment has been minimized.

Show comment
Hide comment
@bjoern-tantau

bjoern-tantau Nov 16, 2017

And Spamassassin. If I disable Spamassin in /etc/postfix/master.cf the problem disappears.

bjoern-tantau commented Nov 16, 2017

And Spamassassin. If I disable Spamassin in /etc/postfix/master.cf the problem disappears.

@bjoern-tantau

This comment has been minimized.

Show comment
Hide comment
@bjoern-tantau

bjoern-tantau Nov 16, 2017

And adding -o receive_override_options=no_address_mappings to /etc/postfix/master.cf fixed it (with Spamassassin enabled).

So, I went from

# service type  private unpriv  chroot  wakeup  maxproc command + args
#               (yes)   (yes)   (yes)   (never) (100)
# ==========================================================================
smtp      inet  n       -       -       -       -       smtpd
        -o content_filter=spamassassin

To

# service type  private unpriv  chroot  wakeup  maxproc command + args
#               (yes)   (yes)   (yes)   (never) (100)
# ==========================================================================
smtp      inet  n       -       -       -       -       smtpd
        -o content_filter=spamassassin
        -o receive_override_options=no_address_mappings

bjoern-tantau commented Nov 16, 2017

And adding -o receive_override_options=no_address_mappings to /etc/postfix/master.cf fixed it (with Spamassassin enabled).

So, I went from

# service type  private unpriv  chroot  wakeup  maxproc command + args
#               (yes)   (yes)   (yes)   (never) (100)
# ==========================================================================
smtp      inet  n       -       -       -       -       smtpd
        -o content_filter=spamassassin

To

# service type  private unpriv  chroot  wakeup  maxproc command + args
#               (yes)   (yes)   (yes)   (never) (100)
# ==========================================================================
smtp      inet  n       -       -       -       -       smtpd
        -o content_filter=spamassassin
        -o receive_override_options=no_address_mappings
@bjoern-tantau

This comment has been minimized.

Show comment
Hide comment
@bjoern-tantau

bjoern-tantau Nov 17, 2017

But now sieve stopped working. I'll continue my investigation.

bjoern-tantau commented Nov 17, 2017

But now sieve stopped working. I'll continue my investigation.

@bjoern-tantau

This comment has been minimized.

Show comment
Hide comment
@bjoern-tantau

bjoern-tantau Nov 23, 2017

Sieve didn't work because I still had it deactivated as part of my tests. :-/

bjoern-tantau commented Nov 23, 2017

Sieve didn't work because I still had it deactivated as part of my tests. :-/

@d00p

This comment has been minimized.

Show comment
Hide comment
@d00p

d00p Nov 27, 2017

Member

The entry -o receive_override_options=no_address_mappings is exactly for this kind of problem and worked for me for ages

Member

d00p commented Nov 27, 2017

The entry -o receive_override_options=no_address_mappings is exactly for this kind of problem and worked for me for ages

@HolySephi

This comment has been minimized.

Show comment
Hide comment
@HolySephi

HolySephi Apr 6, 2018

Contributor

Duplicate mails are almost every time just an incorrect configuration of additional mail processors like amavis or spamd. As d00p already wrote just add the no_address_mappings to the service that receives the mail from the processor.

This could be closed because this can't be fixed within Froxlor - only in the master.cf of your postfix setup

Contributor

HolySephi commented Apr 6, 2018

Duplicate mails are almost every time just an incorrect configuration of additional mail processors like amavis or spamd. As d00p already wrote just add the no_address_mappings to the service that receives the mail from the processor.

This could be closed because this can't be fixed within Froxlor - only in the master.cf of your postfix setup

@d00p d00p closed this Apr 6, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment