π Securely share sensitive information with automatic expiration & deletion after a set number of views or duration. Track who, what and when with full audit logs.
If I set the subnet to 2001:db8::/64 (the prefix reserved for documentation), it works. I would also like to point out that networking works, I just have reason to believe that the application prioritizes IPv4, which doesn't work on that host+container.
I tried to define the SMTP server by IP address only, but that doesn't work.
Hi @olegbliaher - that's an interesting report. Admittedly I've never tried ipv6 only (yet). Thanks for the compose config. I'll try to test this locally soon. Thanks for reporting!
π Bug Report
π¬ How To Reproduce
Steps to reproduce the behavior:
Code sample
--> Configured FROM: address: 'pwpush@oderland.se' --> Default port is 25 but will only be used if smtp_address is set.
The settings.yml mail configuration is:
raise_delivery_errors: true smtp_port: 25 smtp_enable_starttls_auto: true smtp_open_timeout: 10 smtp_read_timeout: 10 mailer_sender: pwpush@domain.com smtp_starttls: true smtp_password: [HIDDEN] smtp_openssl_verify_mode: none smtp_user_name: username smtp_address: smtp.server.com
The Mail subsystem SMTP configuration is:
address: smtp.server.com port: 25 open_timeout: 10 read_timeout: 10 user_name: user password: [HIDDEN] openssl_verify_mode: none enable_starttls_auto: true
Environment
Where are you running/using Password Pusher?
If applicable, what version of Password Pusher?
1.47.3
Screenshots
The error:
π Expected behavior
I expect an email to be sent :)
π Additional context
Since IPv6 is always a bit tricky, I had to define a subnet explicitly in my docker-compose.yml file:
If I set the subnet to
2001:db8::/64
(the prefix reserved for documentation), it works. I would also like to point out that networking works, I just have reason to believe that the application prioritizes IPv4, which doesn't work on that host+container.I tried to define the SMTP server by IP address only, but that doesn't work.