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

maddy 0.8 something broke email_localpart_optional #751

Open
petrm opened this issue Jan 25, 2025 · 4 comments
Open

maddy 0.8 something broke email_localpart_optional #751

petrm opened this issue Jan 25, 2025 · 4 comments
Assignees
Labels
bug Something isn't working. release-blocker Critical problem that should not go as a "known issue" into any release

Comments

@petrm
Copy link

petrm commented Jan 25, 2025

Describe the bug

I have maddy set up as described here: https://maddy.email/multiple-domains/.

    check {                   
        authorize_sender {
            user_to_email chain {  
            step email_localpart_optional           # remove domain from username if present
            step email_with_domain $(local_domains) # expand username with all allowed domains
            }                                        
        }                                                         
    } 

Something has changed in 0.8, because when I authenticate with [email protected], I get the error below.

maddy  | 2025-01-25T19:31:05.563762356Z submission/sasl: authentication failed  {"reason":"no auth. provider accepted creds, last err: unknown credentials","src_ip":"192.168.1.2:59842","username":"[email protected]"}

Authenticating with just user allows the client to log in, but then I end up with:

maddy  | 2025-01-25T19:38:41.643632364Z submission/sasl: authentication failed  {"reason":"no auth. provider accepted creds, last err: unknown credentials","src_ip":"192.168.1.2:39680","username":"[email protected]"}

For now I rolled back to 0.7.1.

Configuration file

Nothing was changed in the config.

  • maddy version: 0.8
@petrm petrm added the bug Something isn't working. label Jan 25, 2025
@foxcpp foxcpp added the release-blocker Critical problem that should not go as a "known issue" into any release label Jan 26, 2025
@foxcpp foxcpp self-assigned this Jan 26, 2025
@foxcpp
Copy link
Owner

foxcpp commented Jan 28, 2025

c48332a should fix the issue

@foxcpp foxcpp added the ready-for-release Feature is implemented and available for testing in dev branch. It will be included in the next rele label Jan 28, 2025
@petrm
Copy link
Author

petrm commented Jan 31, 2025

I built master c852199 and the problem is still there. Any debugging I can do?

@foxcpp foxcpp removed the ready-for-release Feature is implemented and available for testing in dev branch. It will be included in the next rele label Feb 1, 2025
@foxcpp
Copy link
Owner

foxcpp commented Feb 2, 2025

Try again with 01c65cf

@petrm
Copy link
Author

petrm commented Feb 2, 2025

Tested, 01c65cf works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working. release-blocker Critical problem that should not go as a "known issue" into any release
Projects
None yet
Development

No branches or pull requests

2 participants