Hi List.

I am facing #5.7.1 Sorry, that domain isn't in my list of allowed
rcpsthosts (CHKUSER)
whenever i am trying to send using SMTPS - port 465.

I have created a new Minimal Centos7 server, installed qmail as per
the qmailtoaster.org receipe all the way to Qmail-1.03-3.1 (Dev repo)

rsync'ed with -u not to overwrite newer controlfiles, from my production
(Qmail-1.03-2.1), dumped database and checked all /var/qmail files and
made sure (I hope) that content in rcpthosts, virtualdomains etc was
like production server.

It works very well until I try to use port 465 to submit an e-mail then
#5.7.1 Sorry, that domain isn't in my list of allowed rcpsthosts
(CHKUSER) is showing up on my Thunderbird

This is the line in the SMTPS log

2019-01-11 16:38:47.075740500 CHKUSER accepted sender: from
<[email protected]::> remote <[192.168.1.100]:unknown:xxx.xxx.xxx.xx> rcpt
<> : sender accepted
2019-01-11 16:38:47.129749500 CHKUSER rejected relaying: from
<[email protected]::> remote <[192.168.1.100]:unknown:xxx.xxx.xxx.xx> rcpt
<[email protected]> : client not allowed to relay

and this is the lines from my submission log

2019-01-11 15:31:07.454431500 CHKUSER accepted sender: from
<[email protected]:[email protected]:> remote
<[192.168.1.100]:unknown:xxx.xxx.xxx.xx> rcpt <> : sender accepted
2019-01-11 15:31:07.505012500 CHKUSER relaying rcpt: from
<[email protected]:[email protected]:> remote
<[192.168.1.100]:unknown:xxx.xxx.xxx.xx> rcpt <[email protected]> : client
allowed to relay


So why is the senders address <[email protected]::> in the SMTPS log
and <[email protected]:[email protected]:> in the Submission log

I'm almost certain this is my issue because :: is not in the rcpthosts
file (I have tried a lot of different settings - and properly running in
cirkles now so please -HELP)  - I have not tried, yet, to change
tcp.smtp to include ip-address:allow

Cheers Finn von B





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to