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
Forwarding to many destinations emails #34
Comments
|
From the Sieve RFC :
|
Sorry, I don't have many knowledge about Sieve language, can you explain me why is better using Sieve vs virtual_alias_maps with a hash table map file how I describe above? I tested the latter and I checked that it can be used to email forwarding (with local copy) and aliases to multiple destinations. Maybe, as I tell you in #19, is not possible using sql db easily with admin web interface for multiple destinations, but it is easiest with plain text + postmap. Ok, I wait for your opinion. |
The idea when designing this was that forwarding an email is a user choice while aliases are MTA operations. As such, a user choice belongs in the MDA, therefore Dovecot and Pigeonhole. Maybe the design choice is too constraining, and maybe having an SQL-based map in Postfix would simplify things. Still, some important differences:
|
I just pushed to branch feat-forward-multiple to work on this issue. For now it only stores multiple destinations in the same format as aliases, forwarding is thus broken because Dovecot does not interpret the comma separated string properly. |
Sieve does not support loops and I do not believe that extdata is able to provide a list of any kind. I am not sure how to address this issue. |
OK, I understand it and I believe too it should remain so. Loops in Sieve seem dangerous, it is the cause because this feature is unavailable. With loops and vnd.dovecot.filter plugin we could implement it, but it don´t seem possible. I think that we can use vnd.dovecot.execute or vnd.dovecot.pipe plugins in For another hand, Horde team fixed this issue:
They regenerate the sieve config with they own framework. We could modify Neither of the two ideas I really like, but do you think about it? |
Of course, another workaround could be forwarding to an alias, that alias redirects to multiple destinations. We simply have explain the multiple forward configuration in the readme file. This way the desired behaviour would respected, right? In this case, this workaround could fix the problem for now. |
(I renamed the issue to remove the part about aliases) Thank you for the ideas. Documenting a proper configuration using aliases seems like a simple enough workaround solution if we do not find anything better soon. Regarding your proposals, one of the core design concepts in Freeposte.io was to put as much as possible in the database. I would love to find a way to store DKIM keys in the database, so writing custom sieve scripts to disk does not thrill me. I would like to keep it as a last resort option. Instead, I see three solutions that do not require to write dynamic files to disk:
|
After some thinking, I believe external scripts are the only decent way to go. The behaviour could be accomplished with a very simple script, provided that sendmail is available locally and that the original mail is provided on stdin. The behaviour of such a script would be:
|
Also, extprogram is not currently packaged in Alpine, we would have to provide a package. After dicussing the matter with ncopa, the plan is to write a single Dovecot |
Hi, I would like to forward to many destinations, but I don't see that option in the administration interface, when I fill the box with various email addresses (separated by spaces or commas), not working for me.
For another hand, I think that there are a bug in
edit alias
page, because when I try to add many email addresses and I save the configuration withCreate
button, when I check the aliases again, only one appear.This can be solved (workaround) with the new config override feature (#29, #31), changing
virtual_alias_maps
parameter ofmain.cf
with a table map file:/freeposte/overrides/postfix.cf
/freeposte/overrides/virtual_alias.map
The text was updated successfully, but these errors were encountered: