Thanks to visit codestin.com
Credit goes to GitHub.com

Skip to content

Comments

#208 Update config doc about dot escaping in email#279

Open
shalak wants to merge 3 commits intoacme-dns:masterfrom
shalak:208_fix_config_doc
Open

#208 Update config doc about dot escaping in email#279
shalak wants to merge 3 commits intoacme-dns:masterfrom
shalak:208_fix_config_doc

Conversation

@shalak
Copy link

@shalak shalak commented Sep 18, 2021

Fix for #208

linuxgemini added a commit to linuxgemini/acme-dns that referenced this pull request Feb 9, 2022
Co-authored-by: İlteriş Yağıztegin Eroğlu <[email protected]>
Signed-off-by: İlteriş Yağıztegin Eroğlu <[email protected]>
linuxgemini added a commit to linuxgemini/acme-dns that referenced this pull request Feb 9, 2022
Co-authored-by: İlteriş Yağıztegin Eroğlu <[email protected]>
Signed-off-by: İlteriş Yağıztegin Eroğlu <[email protected]>
config.cfg Outdated
nsname = "auth.example.org"
# admin email address, where @ is substituted with .
# admin email address, where "@" is substituted with dot (".")
# any dots in email username must be escaped with "\", e.g. firstname\.lastname.example.com
Copy link

@candlerb candlerb Mar 2, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That needs to be a double-backslash:

nsname = "firstname\\.lastname.example.com"

This is because of TOML escaping. If you put a single backslash here, then acme-dns fails to start with the following error:

Mar 02 10:51:38 ns-acme acme-dns[34272]: time="2022-03-02T10:51:38Z" level=error msg="Encountered
an error while trying to read configuration file:  Near line 6 (last key parsed 'general.nsadmin'):
invalid escape character '.'; only the following escape characters are allowed:
\\b, \\t, \\n, \\f, \\r, \\\", \\\\, \\uXXXX, and \\UXXXXXXXX"

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

@etfz etfz mentioned this pull request Mar 27, 2023
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

Successfully merging this pull request may close these issues.

3 participants