The GUI whitelist/blacklist is part of mailwatch.
It's located In the database mailwatch
Greylisting can be duplicated by just replicating the database sqlgrey
Search found 108 matches
- 07 May 2020 14:15
- Forum: How-to
- Topic: database components backup/export/import to new EFA?
- Replies: 12
- Views: 7994
- 06 May 2020 10:24
- Forum: How-to
- Topic: Blacklist TLD
- Replies: 10
- Views: 5874
Re: Blacklist TLD
Will delete every email from *@*.qq.com but will allow every email from *@qq.com.*.qq.com
- 06 May 2020 02:20
- Forum: How-to
- Topic: Blacklist TLD
- Replies: 10
- Views: 5874
Re: Blacklist TLD
Hi, I actually do see mails getting through that are on the blacklist in the webconsole. How do they get in effect? I added icu without dot, like this: https://localhost/mailscanner/lists.php Blacklist: From: To: Action: icu default Delete qq.com default Delete space default Delete top default Dele...
- 05 May 2020 23:37
- Forum: How-to
- Topic: Blacklist TLD
- Replies: 10
- Views: 5874
Re: Blacklist TLD
EDIT: Deleted, though I thought I had a fix but looking further at source it appears TLD's should be supported. So it might jsut be a small syntax issue. I am working on it, doing some tests
- 05 May 2020 23:01
- Forum: How-to
- Topic: Blacklist TLD
- Replies: 10
- Views: 5874
Re: Blacklist TLD
Seems we need to make a feature request for this. Also seems someone already fixed this for themselves, I have not tried this to see if it works so use at your own risk.
https://www.pokorra.de/2019/03/mailwatc ... blacklist/
https://www.pokorra.de/2019/03/mailwatc ... blacklist/
- 05 May 2020 22:54
- Forum: How-to
- Topic: Blacklist TLD
- Replies: 10
- Views: 5874
Re: Blacklist TLD
yes you are correct the blacklist isn't blocking TLD's.
- 05 May 2020 18:08
- Forum: 4.x Bugs
- Topic: SPF Not working
- Replies: 4
- Views: 14421
Re: SPF Not working
I completely understand the need to sanitize, but it's hard for me to follow along with it that way. I don't expect you to trust me, but maybe talk to one of the moderators, and have them look at the unsanitized version so they can help further. From what I can tell though is spf=none, which is same...
- 05 May 2020 09:00
- Forum: 4.x Bugs
- Topic: SPF Not working
- Replies: 4
- Views: 14421
Re: SPF Not working
Detail's are your friend. I would recommend posting your dns txt record that you have for spf. And posting a example of where you think spf is not working correctly.
- 04 May 2020 15:42
- Forum: 4.x Bugs
- Topic: Cron job are not running
- Replies: 18
- Views: 46855
Re: Cron job are not running
Seems you tried setting up sophosavi at some point as well.ajmind wrote: ↑04 May 2020 15:16Code: Select all
1MAILGW1 site-packages]# cat /etc/ld.so.conf /opt/sophos-av/lib64 include ld.so.conf.d/*.conf
you need to delete
Code: Select all
/opt/sophos-av/lib64
then run
Code: Select all
sudo ldconfig
- 04 May 2020 15:11
- Forum: 4.x Bugs
- Topic: Cron job are not running
- Replies: 18
- Views: 46855
Re: Cron job are not running
what's output of
Code: Select all
cat /etc/ld.so.conf
- 04 May 2020 14:58
- Forum: 4.x Bugs
- Topic: Cron job are not running
- Replies: 18
- Views: 46855
Re: Cron job are not running
I use sophos av without problems. Whats the link to the directions you followed? I'll look and see if maybe I can reverse engineer where it went wrong.
- 04 May 2020 12:57
- Forum: 4.x Bugs
- Topic: Cron job are not running
- Replies: 18
- Views: 46855
Re: Cron job are not running
What did you do to cause this? IT didn't just happen on it's own. Your probably better off reinstalling eFa. post output of ldd /usr/lib64/python2.7/site-packages/pycurl.so This is what it should look like: [uder@host ~]$ ldd /usr/lib64/python2.7/site-packages/pycurl.so linux-vdso.so.1 => (0x00007ff...
- 03 May 2020 18:34
- Forum: 4.x Bugs
- Topic: Postfix all mails Reject - GreyList Off !
- Replies: 8
- Views: 17155
Re: Postfix all mails Reject - GreyList Off !
so there is something wrong with your unbound service.
if thats running then check
and post contents
Code: Select all
sudo systemctl status unbound
Code: Select all
cat /etc/resolv.conf
- 03 May 2020 18:19
- Forum: 4.x Bugs
- Topic: Postfix all mails Reject - GreyList Off !
- Replies: 8
- Views: 17155
Re: Postfix all mails Reject - GreyList Off !
Anonymous TLS connection established from unknown[209.85.221.45]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) May 3 20:38:29 antispam postfix/smtpd[26620]: warning: 45.221.85.209.zen.spamhaus.org: RBL lookup error: Host or domain name not found. Name service error for name=45.221...
- 03 May 2020 18:05
- Forum: 4.x Bugs
- Topic: Postfix all mails Reject - GreyList Off !
- Replies: 8
- Views: 17155
Re: Postfix all mails Reject - GreyList Off !
your going to need to add some CONTEXT and a whole lot more details for help.
- 03 May 2020 14:26
- Forum: How-to
- Topic: GeoIP not always tagging email
- Replies: 25
- Views: 23575
Re: GeoIP not always tagging email
^^^^This catches every ip from 208.84.40.0 to 208.84.47.255smyers119 wrote: ↑03 May 2020 13:10 I am not a expert, and I didn't test this. but you can try adding this in local.cfCode: Select all
header CLASSMATE_NET Received =~ /208\.84\.4[0-7]\.\d{1,3}/ describe CLASSMATE_NET Spam Mail from 208.84.40.0/21 score CLASSMATE_NET 9.0
- 03 May 2020 14:14
- Forum: How-to
- Topic: GeoIP not always tagging email
- Replies: 25
- Views: 23575
Re: GeoIP not always tagging email
I think I found the problem thanks to the link you posted above.... THIS: =~ /(208\.84\.40\.)/ Should actually be THIS: =~ (208\.84\.40\.) Does that look right? This first one when entered into that link highlighted both "/" in red and said "pattern error"... Just use mine so yo...
- 03 May 2020 13:53
- Forum: How-to
- Topic: GeoIP not always tagging email
- Replies: 25
- Views: 23575
Re: GeoIP not always tagging email
Permissions match minebikertrash wrote: ↑03 May 2020 13:49 The file is this in /etc/mail/spamassassin/blockip.cf
The permissions on the file are this:
-rw-r--r--. 1 root root 8271 Apr 29 04:45 blockip.cf
Is this correct?
- 03 May 2020 13:32
- Forum: How-to
- Topic: GeoIP not always tagging email
- Replies: 25
- Views: 23575
Re: GeoIP not always tagging email
Hold up, I found the problem. the ip is encompassed in brackets which is why it's not matching will edit this post with the fix. found a cool regex validator as well (https://regex101.com/) EDIT: Never mind it appears what I posted above is working fine according to the validator. It's showing your ...
- 03 May 2020 13:10
- Forum: How-to
- Topic: GeoIP not always tagging email
- Replies: 25
- Views: 23575
Re: GeoIP not always tagging email
I am not a expert, and I didn't test this. but you can try adding this in local.cf
Code: Select all
header CLASSMATE_NET Received =~ /208\.84\.4[0-7]\.\d{1,3}/
describe CLASSMATE_NET Spam Mail from 208.84.40.0/21
score CLASSMATE_NET 9.0
- 03 May 2020 12:43
- Forum: How-to
- Topic: GeoIP not always tagging email
- Replies: 25
- Views: 23575
Re: GeoIP not always tagging email
I don't think your regex syntax is correct.bikertrash wrote: ↑03 May 2020 12:01 And... another one came right through yesterday... same sub-net...
Oh well...
- 01 May 2020 19:41
- Forum: How-to
- Topic: LDAP Auth and Validation with Active Directory / Exchange for EFA 3.0.2.6
- Replies: 20
- Views: 13532
- 30 Apr 2020 21:23
- Forum: 4.x Bugs
- Topic: MSMilter not started after installation
- Replies: 26
- Views: 11603
Re: MSMilter not started after installation
see how far back journalctl goes, it may still have the logs from when you first installed eFaCitabria79 wrote: ↑30 Apr 2020 21:20 The problem is that it all was to be done after a fresh install, the system is used now. And impossible to reinstall...
- 30 Apr 2020 21:14
- Forum: 4.x Bugs
- Topic: MSMilter not started after installation
- Replies: 26
- Views: 11603
Re: MSMilter not started after installation
Also a copy of dmesg after a fresh install might catch some pertinent info as well.
Code: Select all
dmesg > dmesg.txt
- 30 Apr 2020 21:09
- Forum: 4.x Bugs
- Topic: MSMilter not started after installation
- Replies: 26
- Views: 11603
Re: MSMilter not started after installation
The journalctl logs might give us some insight, but only after a fresh install.
Code: Select all
journalctl --no-pager > logs.txt