Skip to content
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

--with-base64compat harmful #1

Open
arekm opened this issue Dec 20, 2016 · 2 comments
Open

--with-base64compat harmful #1

arekm opened this issue Dec 20, 2016 · 2 comments

Comments

@arekm
Copy link

arekm commented Dec 20, 2016

Issue for sake of others googling around and looking for libsrs-alt.

--with-base64compat is unfortunately recommented in README but it breaks RFC5321 compatibility.
It can generate addresses like "SRS0=GW..5e=YD=test.pl=test@example.com" where there are two
dots without any separator between and that is invalid according to above RFC.

(and for example google enforces strict RFC5321 checking and is catching that incompatibility)

@LynxChaus
Copy link
Owner

make patch? But libsrs_alt is obsolete and exim already have native support of SRS internally (see https://bugs.exim.org/show_bug.cgi?id=1649).

@arekm
Copy link
Author

arekm commented Dec 20, 2016

About a patch ... not sure which character would be good to be used as replacement for 'dot'. So for now disabling base64compat option works (with its drawbacks though).

exim doesn't have "native srs support". Exim is flexible enough that you can implement SRS with its internal functions but that's nasty and error prone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants