Search results

  1. H

    Custom rule - empty sender orig_client

    DNSBL will not work if the sender server (185.41.154.171) is not blacklisted. Again, it is important to setup local resolver/DNS service if you are using DNSBL. I think the main issue is RCVD_IN_DNSWL_HI(-5). If you notice many false positive from this SA score, try modify the default -5 score...
  2. H

    [TUTORIAL] ClamAV create custom signature database file

    PMG use clamav as the default AV engine for virus scanning and the default detection rate is bad. Beside add custom 3rd signature database, let try to create your own custom signature database using clamav's sigtool. 1. Use sigtool to hex dump the first 2KB output of the suspicious file to the...
  3. H

    How to set Spamhaus DNSBL correctly?

    Just set your DNSBL list and threshold under Mail Proxy -> Options.
  4. H

    regular expressions in PMG 7.1-4

    It will match upper and lower case subject (?i)(\W|^)(privated?|pains?|penis|pussy)(\W|$)
  5. H

    Adding IP to Configuration -> Mail Proxy -> Whitelist & Networks

    From the official documentation, it will bypass greylisting, SPF and DNSBL. No mention of rate limiting. https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#_mail_proxy_configuration
  6. H

    Bad Spam recognition (compared to other solutions)

    @poetry, I believe you have already answer your own question. PMG use public DNSBL and spamassassin for spam detection and it provide you the freedom to customize the spam rate based on your own environment and experiences. As the email admin (I assume you are too), study the current spam mail...
  7. H

    Bad Spam recognition (compared to other solutions)

    Study your spam trend and create custom spamassassin uri rules. # Spammy link with email address uri LINK_W_MAIL /(\?|\#).*(@|%40)mydomain\.com\.my/i describe LINK_W_MAIL Spammy link with email address score LINK_W_MAIL 1.0 uri __G_DRV...
  8. H

    PMG not block obvious phising email ?

    IP 139.59.114.99 not listed in your DNSBL list, try using below DNSBL site. dnsbl-1.uceprotect.net rbl.dns-servicios.com sip.invalument.com hostkarma.junkemailfilter.com
  9. H

    Spam filter rule to check subject for part of recipient name

    then this should work. (?i)(\W|^)(foods|you want|fly|fake|fat|freedom)(\W|$)
  10. H

    Spam filter rule to check subject for part of recipient name

    Is your subject, "j.doe@example.com": "j doe You want this" ?
  11. H

    Spam filter rule to check subject for part of recipient name

    Try this what object, subject match field. Adjust the 25 character to the length you want. (?i)(\W|^)([\w.\-]{0,25}?example\.com)(\W|$)
  12. H

    Proxmox Configuration DNSBL SITES

    Below is my DNSBL with threshold of 3. Use/setup internal DNS to prevent DNSBL timeout. zen.spamhaus.org*2,bl.mailspike.net,psbl.surriel.com,all.spamrats.com,dnsbl-1.uceprotect.net
  13. H

    Proxmox Configuration DNSBL SITES

    Adding more DNSBL may cause false positive as not all DNSBL have the same reputation score. https://www.dnsbl.info/dnsbl-list.php
  14. H

    What Object - Rule to match a word in mail content

    Use spamassassin custom rules to filter mail content. https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#_custom_spamassassin_configuration https://cwiki.apache.org/confluence/display/SPAMASSASSIN/writingrules https://github.com/kawaiipantsu/spamassassin-rules/tree/master/rules
  15. H

    What mx records should I configure in my dns for the PMG?

    Set your domain MX IP to your PMG, PMG will accept all the incoming email and filter/delivery the mails to your actual email server. Assume you have setup correctly PMG with your email server.
  16. H

    [SOLVED] Toggle Spam Info missing SA rules description

    Issue fixed with the latest update. proxmox-mailgateway: 7.1-1 pmg-api: 7.1-4 pmg-gui: 3.1-3 pve-kernel-helper: 7.2-6 pve-kernel-5.13: 7.1-9 pve-kernel-5.11: 7.0-10 pve-kernel-5.13.19-6-pve: 5.13.19-15 pve-kernel-5.13.19-5-pve: 5.13.19-13 pve-kernel-5.13.19-4-pve: 5.13.19-9...
  17. H

    Wide character in subroutine entry at /usr/share/perl5/PMG/RuleDB/ModField.pm line 78. (500)

    I believe the current state of PMG do not support utf8 encoded subject. So it may not work. https://forum.proxmox.com/threads/utf-8-base-64-encoded-subject.110873/
  18. H

    Rule names not updating in logs

    It will show as whitelisted under syslog Jul 07 12:13:22 pmg postfix/postscreen[91151]: WHITELISTED [218.208.xxx.xxx]:37062