unsubscribe
unsubscribe
Re: How to write the rule to avoid spam
Hello,
I have the following filters in smtpd.conf to cut the hosts sending SPAM:
filter no_dyndns \
phase connect \
match rdns regex { \
'.*\.dyn\..*', '.*\.dsl\..*', \
'([0-9]{1,3}\.){3}.*', \
'([0-9]{1,3}-){3}.*' \
} \
disconnect "550 We do not accept mail from dynamic IPs"
filter no_rdns \
phase rcpt-to \
match !rdns \
disconnect "451 Sending server has no reverse DNS (PTR record)"
filter no_fcrdns \
phase rcpt-to \
match ! fcrdns \
disconnect "451 No Forward Confirmed Reverse DNS. Please contact your
e-mail administrator"
and then
listen on 0.0.0.0 port 25 tls pki mail.svyrydiuk.eu \
ca cafile \
hostname "mail.svyrydiuk.eu" \
filter { no_dyndns, no_rdns, no_fcrdns }
On Wed, Apr 05, 2023 at 02:37:25AM +, Mik J wrote:
> Hello,
> Sometimes I'm getting spam because I have a weakness in my configuration
> At the moment I have
> action TO-CLAM_SMTPD_IN relay host smtp://127.0.0.1:10027
> match from src for domain action TO-CLAM_SMTPD_IN
> match from any for domain action TO-CLAM_SMTPD_IN
> The table clients is a file that contains IPs including 127.0.0.1, the table
> domaines is a list of domains that I host on my mail server
>
> My problem is that a spammer is able to send mails to me when it uses a
> domain that I host.For example, the file domaines contains mydomain1.org and
> mydomain2.orgThe spammer doesehlo emtpmail from:
> rcpt to: data
> subject: This is a spam
> Spamspamspam
> .
>
> So I would tend to write a rule such asmatch ! from domain for
> domain action TO-CLAM_SMTPD_INConsidering that users that write
> from mydomain2.org to mydomain1.org match the first rule since they are local
> or authenticated or coming from one of the known IPs.But this rule is not
> correct
>
> Thank you
--
with best regards,
Slavik Svyrydiuk
Re: How to write the rule to avoid spam
On Wed, Apr 05, 2023 at 02:37:25AM +, Mik J wrote: > Hello, > Sometimes I'm getting spam because I have a weakness in my configuration > At the moment I have > action TO-CLAM_SMTPD_IN relay host smtp://127.0.0.1:10027 > match from src for domain action TO-CLAM_SMTPD_IN > match from any for domain action TO-CLAM_SMTPD_IN > The table clients is a file that contains IPs including 127.0.0.1, the table > domaines is a list of domains that I host on my mail server > > My problem is that a spammer is able to send mails to me when it uses a > domain that I host.For example, the file domaines contains mydomain1.org and > mydomain2.orgThe spammer doesehlo emtpmail from: > rcpt to: data > subject: This is a spam > Spamspamspam > . > > So I would tend to write a rule such asmatch ! from domain for > domain action TO-CLAM_SMTPD_INConsidering that users that write > from mydomain2.org to mydomain1.org match the first rule since they are local > or authenticated or coming from one of the known IPs.But this rule is not > correct > > Thank you -- with best regards, Slavik Svyrydiuk web: www.svyrydiuk.eu
Re: opensmtpd appears to be IPv4-only
I do not have any issues with IPv6. It works for me. Ubuntu == opensmtpd 6.0.3p1-1ubuntu0.2 smtpd.conf lines: listen on 0.0.0.0 port 25 listen on ::0 port 25 $ netstat -lnt | grep ':25' tcp0 0 0.0.0.0:25 0.0.0.0:* LISTEN tcp6 0 0 :::25 :::*LISTEN OpenBSD === version: OpenSMTPD 6.7.0 smtpd.conf lines: listen on all tls pki example.pki On Wed, 22 Jul 2020 16:34:25 +0200 Harald Dunkel wrote: > Hi folks, > > I've got a problem with IPv6 support for opensmtpd 6.7.1p1 on > Debian: Apparently opensmtpd seems to ignore IPv6 after a reboot. > > My smtpd.conf says > > : > xname = "mailhost.example.com" > pki $xname cert "/etc/mail/ssl/mailhost.example.com.cert" > pki $xname key"/etc/mail/ssl/mailhost.example.com.key" > > listen on lo tls pki $xname > listen on eth0tls pki $xname > : > > lsof -p shows that smtpd is listening only on the IPv4 address on > eth0. The IPv6 addresses bound to eth0 (link-local and global) are > ignored. > > If I *restart* smtpd, then it is listening on IPv6 as well, up to > the next prefix change propagated via router advertisement. The > IPv6 address with the new prefix is ignored. When the old prefix > expires, then opensmtpd is back to IPv4-only. I have to restart > it again. > > Can anybody reproduce this? > > > Every helpful comment is highly appreciated. > > Regards > Harri > -- with best regards, Slavik Svyrydiuk
Re: 553 ORCPT address syntax error
> In /etc/mail/aliases I used to say > root: sys...@example.com <mailto:sys...@example.com> Your /etc/aliases must look like: root: sys...@example.com >From man page: user-part@domain-part An email address in RFC 5322 format. If an address extension is appended to the user-part, it is first compared for an exact match. It is then stripped so that an address such as user+...@example.com will only use the part that precedes `+' as a key. On Mon, 15 Jun 2020 13:43:11 +0200 Tony Boston wrote: > Hi, > > I have an issue with forwarding mails which belong to the local root user. > I never had that and it seems something changed in opensmtpd? > > In /etc/mail/aliases I used to say > root: sys...@example.com <mailto:sys...@example.com> > > This always worked but stopped working and the following error pops up in the > logs: > smtp failed-command command="RCPT TO: ORCPT=rfc822;root" > result="553 ORCPT address syntax error” > > It actually does work when I try something like ‘echo Test | mail > sys...@example.com’ BUT 'echo Test | mail root’ does not > > Am I missing something? > > — > Tony > -- with best regards, Slavik Svyrydiuk
