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
[Fix] Adresse de rebond différente du domaine principal. #374
Conversation
Thanks for your work! |
Indeed. It's better with comments because in fact there are many IGNORE header for anonymisation too. |
Thanks. Can you also edit your PR to give us more information on what the problem is, and how to test your patch? |
Fait, sauf pour les vérifications... je ne sais pas combien il faut de reviews pour merger, ni quand. |
From my understanding, this template shouldn't be applied as-is, because you should replace the What about the e-mails you send with that conf? Don't they have a |
indeed. Sorry... I will make a commit later in the day to fix it. |
From what I've tested, when you send a mail from user@domain2.com (where domain1.com is the main domain), the headers contains a You should really edit the PR with real examples of mail headers sent before and after your change, so that we can have a real understanding. EDIT: Your problem seems the same as the one addressed in this pending PR #331 |
postsrsd doesn't work... or at least there is a problem in this PR with the syntax of the domain . And for my conf, I didn't use postsrsd. But ok... if my PR is useless from your point of view... fine. I close it. I've fixed it in my conf... for me it's ok. |
ok, let's open it even if my server is in a bad state. :-) I will add two example of header (anonyme) before and after the fix in the PR summary. |
That's it. |
So, the logical part is that it replaces the
with
But:
by
which I understand as fixing your issue... So the |
Perhaps anonymisation... I don't know too but this change solved my issue. |
c'est bon. J'avais en partie oublié que j'avais changé le main.cf. |
I keep the header conf I made because there is some anonymisation which are very nice. |
Can someone have a look at it ? |
I just changed the main.cf as mentioned and worked fine for me. |
Thanks for the feedback ! 👍 |
I understand this might work for your use cases guys, but that's not the right solution in the general case :/. The SRS thing is here for a reason, in particular for when your forward mails (e.g. Alice sends an email to Bob@bob.nohost.me, which is forwarded to Bob@gmail.com). This isn't easy to explain in just 2 sentences so if you really are interested, you can read the wikipedia page as a starter I guess :s. Our current implementation of SRS is pretty buggy at the moment (my understanding is that this $1 thing refers to the main domain, which is not what we want), though I believe it at least allows forwarded email to not be completely rejected (e.g. by gmail.com in my example). So the fix proposed here is an acceptable workaround if you don't care about email forwards (or similar stuff like mailing lists I guess), but it's not in the general case... In the general case, we have to implement a method to correctly handle SRS in a multi-domain context, which is not trivial but is what postsrsd does as suggested here. |
The header_checks / IGNORE stuff is pretty independent from the SRS thing though, I think ;). It might be relevant though I don't have enough knowledge about these to know which implications that can have. |
yes, but I think that for instance it's better than nothing or the Yunohost previous conf. |
For instance the PR for the postsrsd (I have tested too) doesn't work for me and is pretty useless for this case. |
@alexAubin, perhaps it can be good to add/enable SRS conf only if we need it, and use the 'classic' conf I suggest when we just want an email server ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I re-checked #331 and to me it seems to be working fine (I didnt recheck the forwarding case though).
So regarding this PR, the header_checks
thing is ok (and is the same as mailinabox, which I guess we can trust on this...).
But to me we definitely can't just remove sender_canonical_maps
without breaking the foward feature of YunoHost. This was attempted in another old PR and we closed it for the same reason as far as I remember.
@@ -131,10 +131,6 @@ smtpd_recipient_restrictions = | |||
reject_unauth_destination, | |||
permit | |||
|
|||
# SRS | |||
sender_canonical_maps = regexp:/etc/postfix/sender_canonical |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can't remove this without breaking the forward feature of YunoHost (among other things). The proper fix is to use postsrsd to handle the Sender Rewriting Scheme properly...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok. I agree... I can't test postsrsd right now (I tested but surely not enough). I trust you. Can we keep the header. I think we will need to test the first one... many doubts about it.
ok. Postsrs PR merged. This is not needed. Thanks for your review anyway ;) |
I will open perhaps a PR for the header ? :/ |
Yes please 👍 |
Problem
issue: https://forum.yunohost.org/t/probleme-mail-dns-2d-domaine/3460
Solution
https://github.com/mail-in-a-box/mailinabox/blob/master/conf/postfix_outgoing_mail_header_filters
PR Status
REOPENED
TEST/ REVIEW Highly Needed (RHN)
EXAMPLE (for JimBoJoe and Reviewers)
before with postsrsd :
After :
Remerciement
Donc, un grand merci à eux (sans le vouloir).