Hello Fellow Slackers , Just having recently recreated my mail server I find I am having Difficulty with getting any email responses from maillist at slackware.com . Yes I've done google searches for just such occurances of lack of response from majordomo at slackware.com looking for just what might be the issue(s) , I've found some possible problems & have fixed/updated those issues I've found in my searching , But still no response is returned from majordomo . There are at present NO filters except spamassassin & milter-greylist But the ip addresses assoiciated with slackware.com (ie: mail.cwo.com) are whitelisted) But they'd give me an entry in the logfile for blocking ...

Would someone at slackware please respond to this missive ?

I've sent emails from my other address , ie: my gmail.com account , to contact addresses several days ago , And still nothing .

Please see more below ...


# I've sent to majordomo@slackware.com in the body of the message
help
# and later
lists

The maillog , see below , show that mail.cwo.com accepts the email and NOTHING returns .

# a sample log from 05-Mar-2019
Mar 5 18:34:12 ns4 milter-greylist: Mail from=<babydr@baby-dragons.com>, rcpt=<majordomo@slackware.com>, addr=localhost[127.0.0.1] is matched by entry racl 264 whitelist net_list "my network" [maxpeek -1]
Mar 5 18:34:12 ns4 milter-greylist: x263YBb8009999: skipping greylist because address 127.0.0.1 is whitelisted, (from=<babydr@baby-dragons.com>, rcpt=<majordomo@slackware.com>, addr=localhost[127.0.0.1]) ACL 264
Mar 5 18:34:13 ns4 sm-mta[10002]: x263YBb8009999: to=<majordomo@slackware.com>, ctladdr=<babydr@baby-dragons.com> (1002/100), delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=120322, relay=mail.cwo.com. [64.57.96.4], dsn=2.0.0, stat=Sent (ok 1551843253 qp 8374 uuid b5d04fa8-3fc0-11e9-b30a-00259014b742)

OK, I found a problem on our end. Try it again.

Thank you , Patrick . Tho now the response is ...
Mar 27 14:02:54 ns4 sm-mta[25315]: x2RM2qhE025312: to=<majordomo@slackware.com>, ctladdr=<babydr@baby-dragons.com> (1002/100), delay=00:00:02, xdelay=00:00:02, mailer=esmtp, pri=120632, relay=mail.cwo.com. [64.57.96.4], dsn=5.0.0, stat=Service unavailable

That's odd. The issue I'd found was that CWO had enabled spam filtering on majordomo@slackware.com, and I saw your mails caught in the trap. I disabled the filters.

After seeing your "Service unavailable" post, I tested sending "lists" in the message body to majordomo@slackware.com from a test Gmail account. Got the expected mail back.

Hello Patrick (& All) , It must have been due to a non-allowed command to majordomo as all others have completed successfully .
So I am marking this thread as SOLVED , well I at least hope I can ...
Tnx , JimL

1 members found this post helpful.