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

email forwarding does not work when it is to a recipient with encryption turned on #102

Closed
eleith opened this issue Jan 22, 2022 · 1 comment

Comments

@eleith
Copy link
Contributor

eleith commented Jan 22, 2022

Behaviour

Steps to reproduce this issue

  1. create a recipient
  2. turn on encryption for that recipient
  3. assign an alias to that recipient
  4. send email to the alias

Expected behaviour

an encrypted email should be forwarded to the recipient

Actual behaviour

the email is never forwarded, laravel logs shows the following error

Connection to 127.0.0.1:25 Timed Out (code: 0) {"exception":"[object] (Swift_TransportException(code: 0): Connection to 127.0.0.1:25 Timed Out

Configuration

running 0.8.10 and emails to non-encrypted aliases do forward properly. i followed gpg instructions

i would have guessed the errors would be related to pgp and signing but nothing stands out yet. the timeout indicates there is an smtp error though postfix logs just say the email was deferred with no exact error.

is there a set of debug steps i can take to ensure gpg works locally? any other logs i can look at?

@eleith eleith changed the title email forwardingdoes not work when it is to a recipient with encryption turned on email forwarding does not work when it is to a recipient with encryption turned on Jan 22, 2022
@eleith
Copy link
Contributor Author

eleith commented Jan 22, 2022

docs have more information on how to set up gpg (https://anonaddy.com/self-hosting/) in particular, do not set a passphrase on the key and copy the fingerprint to ANONADDY_SIGNING_KEY_FINGERPRINT= and then running php artisan config:cache afterwards

@eleith eleith closed this as completed Jan 22, 2022
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

1 participant