emailrelay: disabled config is started anyway
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Package Name
emailrelay
Maintainer
fededim@gmail.com
OpenWrt Version
25.12.2
OpenWrt Target/Subtarget
x86/64
Steps to Reproduce
Have more than one instance in /etc/config/emailrelay
Have at least one instance disabled (option enabled '0')
(Re)start service
Check status
Result: the disabled instance is started with the only one option "/usr/bin/emailrelay --no-daemon"
If more than one instance is using the same default port 25 -> conflict, only one instance is started.
Actual Behaviour
Result: the disabled instance is started with the only one option "/usr/bin/emailrelay --no-daemon"
If more than one instance is using the same default port 25 -> conflict, only one instance is started.
Confirmation Checklist
- The package is maintained in this repository.
- I understand that issues related to the base OpenWrt repository or LuCI repository will be closed.
- I am reporting an issue for OpenWrt, not an unsupported fork.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report identifies /etc/config/emailrelay and the restart/status flow but no source file or test. Start by locating the emailrelay package's service and configuration handling, then reproduce with one disabled instance; done means disabled instances are not started while enabled instances still start without port conflicts.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100