Solved '550 No such recipient here'. => spamd: unauthorized connection from xx to port 783

tarta

Verified User
Joined
Jan 31, 2018
Messages
81
Hi,

I'm having a problem with outgoing mails to certain mailboxes
- it works when sending mail from @global-soft.pl to [email protected]
- it works when sending mail from [email protected] to @global-soft.pl
- it doesn't work when sending mail from @global-soft.pl to [email protected] with error:

'550 No such recipient here'.

Exim Rejectlog shows:
2021-11-28 19:31:14 H=xx] X=TLS1.2:ECDHE-ECDSA-AES128-GCM-SHA256:128 CV=no F=<[email protected]> A=login:[email protected] rejected RCPT <[email protected]>:

and /var/log/mail.warn shows:

ds spamd[20493]: spamd: unauthorized connection from [Server IP] to port 783, fd 5 at /usr/bin/spamd line 1627.



Questions:
1) how to resolve rejected RCPT
2) how to resolve spamd and 783 access issues?
 
Last edited:
As for the "no such recipient here", have you seen this thread? It contains a couple of suggestions and solutions:

As for the spamd, check this one:
 
MX records are set (per my understanding) correct (CloudFlare)



As for the spamd ==>> I failed at the 1st step already
file does not exist: ==> /etc/init.d/exim
 
ok, my situation is similar to https://forum.directadmin.com/threads/stop-receiving-email-with-forwarding-enabled.64885/

[email protected] is on the same server as mail from @global-soft.pl
yet, MX is set to use Zoho servers

now, when I've created [email protected] on the server I can send mails to it from @global-soft.pl as it's now a

R=virtual_user T=dovecot_lmtp_udp S=4330 C="250 2.0.0 <[email protected]


That makes is more complex :)
1) mail hosted on zoho works fine
2) mails sent from @global-soft.pl to [email protected] do not reach zoho server, but stay internally on server (as a virtual user)


what config is missing on @global-soft.pl server side to ensure outgoing mails go to the correct server (looks like a routing issue?)
 
1) spamd


Yes it's a bit older manual. Check this file:
/etc/systemd/system/exim.service

[Service]
ExecStart=/usr/sbin/exim -bd -q${QUEUE}


I assume I should update is to
ExecStart=/usr/sbin/exim -bd -A xx, 127.0.0.1 -q${QUEUE}


that ends in
Nov 29 15:38:19 dxx.com exim[138970]: exim abandoned: unknown, malformed, or incomplete option -A
Nov 29 15:38:19 dxx.com systemd[1]: exim.service: Main process exited, code=exited, status=1/FAILURE
Nov 29 15:38:19 dxx.com systemd[1]: exim.service: Failed with result 'exit-code'.



2) mail

I presume that [email protected] email address exists. What happens if you send a mail from Gmail to that e-mail address?

sending emails from ie. Gmail to [email protected] ends in mail arraiving on Zoho server (and that's what I need).
whereas sending mail from @global-soft.pl to [email protected] ends in mail arraiving on VPS server (and that's what dont want).
 
1) spamd issue remains unsolved

2) Ive just uncheck the 'Local Mail Server' for dreier.pl and all started working


Zrzut ekranu 2021-11-29 162909.png
 
2.) That was the next thing I wanted to suggest so glad you found it already.

1.) As for spamd, I think that manual is too old. Best is to put the exim.service file back as it was before.
As far as I read, it seems that it might be caused be a loopback address missing.

Try changing it in the /etc/systemd/system/spamassassin.service instead.
change:
ExecStart=/usr/bin/spamd --pidfile /var/run/spamd.pid -d -c -m 15 --ipv4
to
ExecStart=/usr/bin/spamd -A 11.22.33.44 --pidfile /var/run/spamd.pid -d -c -m 15 --ipv4
where 11.22.33.44 is your public ip and restart exim.

If this does not help then change back to the default, and then we have to wait for somebody else or you have to send in a ticket.

You can also try 11.22.33.44,127.0.0.1 but do -not- use a space behind the comma.
 
You can also try 11.22.33.44,127.0.0.1 but do -not- use a space behind the comma.

ok, corrected to

ExecStart=/usr/bin/spamd -A 11.22.33.44,127.0.0.1 --pidfile /var/run/spamd.pid -d -c -m 15 --ipv4

and resulting in

root@ds:/usr/local/directadmin/custombuild# service exim status
● exim.service - Exim Mail Transport Agent
Loaded: loaded (/etc/systemd/system/exim.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2021-11-29 18:28:19 CET; 4s ago
Main PID: 201436 (exim)
Tasks: 1 (limit: 9509)
Memory: 6.0M
CPU: 89ms
CGroup: /system.slice/exim.service
└─201436 /usr/sbin/exim -bd -q1h

Nov 29 18:28:19 dxxm systemd[1]: Started Exim Mail Transport Agent.

root@ds:/usr/local/directadmin/custombuild# service spamd status
● spamassassin.service - Spamassassin daemon
Loaded: loaded (/etc/systemd/system/spamassassin.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2021-11-29 18:28:06 CET; 22s ago
Process: 201407 ExecStart=/usr/bin/spamd -A xx8,127.0.0.1 --pidfile /var/run/spamd.pid -d -c -m 15 --ipv4 (code=exited, status=0/SUCCESS)
Main PID: 201415 (spamd)
Tasks: 3 (limit: 9509)
Memory: 98.5M
CPU: 3.086s
CGroup: /system.slice/spamassassin.service
├─201415 /usr/bin/perl -T -w /usr/bin/spamd -A Xx8,127.0.0.1 --pidfile /var/run/spamd.pid -d -c -m 15 --ipv4
├─201417 spamd child
└─201418 spamd child

Nov 29 18:28:03 xx systemd[1]: Starting Spamassassin daemon...
Nov 29 18:28:03 xx spamd[201407]: logger: removing stderr method
Nov 29 18:28:06 xxm spamd[201415]: spamd: server started on IO::Socket::IP [127.0.0.1]:783 (running version 3.4.6)
Nov 29 18:28:06 xx spamd[201415]: spamd: server pid: 201415
Nov 29 18:28:06 dxxm spamd[201415]: spamd: server successfully spawned child process, pid 201417
Nov 29 18:28:06 dxxm systemd[1]: Started Spamassassin daemon.
Nov 29 18:28:06 dsxxm spamd[201415]: spamd: server successfully spawned child process, pid 201418
Nov 29 18:28:06 ds.promo-codes4u.com spamd[201415]: prefork: child states: IS
Nov 29 18:28:06 ds.promo-codes4u.com spamd[201415]: prefork: child states: II



case closed.

Thanks a lof for your help @Richard
 
You're welcome.
Thanks for reporting back, then we can use this adjusted solution in case anyone else encounters this issue. (y)

If possible, please edit your first post and change the prefix to solved/fixed (whatever is present).
 
Back
Top