DKIM 套接字问题
我对 dkim-milter 有疑问。
我的邮件日志文件充满了日志，
Dec 5 23:59:59 NS1 dkim-filter[31424]: Sendmail DKIM Filter: Unable to bind to port inet:20209@localhost: Address already in use
Dec 5 23:59:59 NS1 dkim-filter[31424]: Sendmail DKIM Filter: Unable to create listening socket on conn inet:20209@localhost
Dec 5 23:59:59 NS1 dkim-filter[31424]: smfi_opensocket() failed
我怀疑问题与 Dkim-filter.conf 和行有关：
Socket inet:20209@localhost
看起来有些东西已经在该端口上运行，所以我无法再次绑定它。
如何更改此设置并使 DKIM 正常运行？
I have a problem with dkim-milter.
My maillog file is filled with logs
Dec 5 23:59:59 NS1 dkim-filter[31424]: Sendmail DKIM Filter: Unable to bind to port inet:20209@localhost: Address already in use
Dec 5 23:59:59 NS1 dkim-filter[31424]: Sendmail DKIM Filter: Unable to create listening socket on conn inet:20209@localhost
Dec 5 23:59:59 NS1 dkim-filter[31424]: smfi_opensocket() failed
I suspect that the problem is related to Dkim-filter.conf and line:
Socket inet:20209@localhost
It looks like something is allready runing on that port so I can't bind it again.
How can I change this and make DKIM running without errors?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
请注意，我发现当我手动停止并重新启动 dkim-milter 服务时，我的日志中充满了该消息。这是由于配置选项“AutoRestart”默认为“Yes”。
启用该选项后，当使用“service dkim-milter stop”停止服务时，它会自动重新启动，并且当我的 shell 脚本运行“service dkim-milter”时，它会自动重新启动。几秒钟后，它正在重复该过程，并且无法连接到端口，因为它已经在运行。
我的经验不足，不知道最好的方法是修复它，但上述问题已经过测试并且可重复。
As a note, I found that when I manually stopped and restarted the dkim-milter service, my logs filled up with that message. This was due to the config option "AutoRestart" which defaults to Yes"
With that option on, when the service is stopped using "service dkim-milter stop", it automatically restarts, and when my shell script then ran "service dkim-milter start" a few seconds later, it was duplicating the process and was unable to connect to the port as it was already running.
I am not really experienced enough to know the best was to fix it, but the problem above was tested and repeatable.
就我而言，我运行了错误的命令。 我不是在跑步，而是
在跑步：
不确定这种情况有多常见，但我确实花了一段时间才发现。
In my case, I was running the wrong command. Instead of running
I was running:
Not sure how common this is, but it sure took me a while to track down.
端口 20209 已被使用，也许是旧的僵尸 dkim-milter？
netstat -nlp | netstat -nlp | netstat -nlp | netstat -nlp | netstat -nlp | netstat -nlp grep 20209 将帮助您找出阻塞端口的原因
port 20209 is already in use, maybe an old zombie dkim-milter?
netstat -nlp | grep 20209will help you find out whats blocking the port我遇到了同样的问题，因此在朋友的帮助下，我按照以下步骤操作：
tail -n 25 /var/log/maillognetstat -nlp | grep 20209service dkim-milter status作为 dkim-filter 运行： ps ax | grep filter
kill 32731现在产生错误的进程没有运行。
这是重新启动 dkim-milter 和 postfix 的方法：
现在一切似乎都正常
I had the same problem so with the help of a friend I followed the steps below:
tail -n 25 /var/log/maillognetstat -nlp | grep 20209service dkim-milter statusrunning as dkim-filter:
ps ax | grep filterkill 32731Now the process which produced the errors isn't running.
This is how to restart to dkim-milter and postfix:
And everything seemed to work ok now