Replies: 1 comment
-
Try escaping the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What happened?
Subaddressing is not working as described in the manual at https://stalw.art/docs/smtp/inbound/rcpt#subaddressing
I have set-up an example server that is able to successfully receive emails at the address
[email protected]
:How can we reproduce the problem?
I unsuccessfully tried two approaches to make sub-addressing work based on the description in the manual at https://stalw.art/docs/smtp/inbound/rcpt#subaddressing, leading me to think that the feature might be broken. I am trying to get [email protected] delivered to [email protected]
The current version of config.toml seems to follow a different logic than described in the manual forcing me to slightly modify the example from the manual: I added the following line to config.toml
session.rcpt.sub-addressing = [ { if = "matches('^([^.]+)\.([^.]+)@(.+)$', rcpt)", then = "$2 + '@' + $3" }, { else = false } ]
As a second try, i did the modifications directly in the web interface (see attached screenshot):
matches('^([^.]+)\.([^.]+)@(.+)$', rcpt)
in "if" field$2 + '@' + $3
in "then" fieldfalse
in "else" fieldBoth different trials lead to the same result: the mailbox for user
[email protected]
does not exist (see log below).Version
v0.10.5
What database are you using?
RocksDB
What blob storage are you using?
RocksDB
Where is your directory located?
Internal
What operating system are you using?
Docker
Relevant log output
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions