W dniu 16.05.2022 o 15:51, Matus UHLAR - fantomas pisze:
W dniu 16.05.2022 o 15:14, Matus UHLAR - fantomas pisze:
Any idea to whitlist ?
On 16 May 2022, at 9:35 pm, Matus UHLAR - fantomas
<uh...@fantomas.sk> wrote:
perhaps the null address at outgoing server, so you don't reject
your own bounces
W dniu 16.05.2022 o 14:46, Viktor Dukhovni pisze:
No. Better to apply the reject rule only on the inbound side, where
it should only lead to bounces on remote systems.
The OP's own systems should be sending outbound mail via the
outbound MTA.
On 16.05.22 14:52, natan wrote:
Maybe smart loop if then ? But I do not know if it is not
overcomplicated and what it would look like
please explain more deeply what do your inbound and outbound
mailservers exactly do.
perhaps explain, how did e-mail 4L1w1y6WBVz1DDmK enter your mailserver
- if you could block it the way in, you wouldn't have to generate
bounce.
I guessed your incoming server is used as MX, and outgoing server
for outbound e-mail from your clients.
On 16.05.22 15:33, natan wrote:
1)I send email from my outgoing server smtp xxx.xxx.xxx.220
Log from serwer smtp xxx.xxx.xxx.220:
May 16 12:08:38 smtp1 postfix/submission/smtpd[18768]:
4L1w1y5FpXz6c1M: client=unknown[xxx.xxx.xxx.60], sasl_method=LOGIN,
sasl_username=na...@domain.ltd
May 16 12:08:38 smtp1 postfix/cleanup[4182]: 4L1w1y5FpXz6c1M:
warning: header Subject: alakot from unknown[xxx.xxx.xxx.60];
from=<na...@domain.ltd> to=<na...@domain.ltd> proto=ESMTP helo=<poczta>
May 16 12:08:38 smtp1 postfix/cleanup[4182]: 4L1w1y5FpXz6c1M:
message-id=<6eb63dcd4d1732c33ca530cbae194...@domain.ltd>
May 16 12:08:38 smtp1 postfix/qmgr[33961]: 4L1w1y5FpXz6c1M:
from=<na...@domain.ltd>, size=1270, nrcpt=1 (queue active)
May 16 12:08:38 smtp1 postfix/smtp/smtp[36552]: 4L1w1y5FpXz6c1M:
to=<na...@domain.ltd>, relay=<mx.domain.ltd[xxx.xxx.xxx.4]:25,
delay=0.18, delays=0.11/0/0.04/0.03, dsn=5.7.1, status=bounced (host
mx.domain.ltd[xxx.xxx.xxx.4] said: 550 5.7.1 spam2bok bla bla (in
reply to end of DATA command))
May 16 12:08:38 smtp1 postfix/bounce[3725]: 4L1w1y5FpXz6c1M: sender
non-delivery notification: 4L1w1y6Yk6z6c0l
May 16 12:08:38 smtp1 postfix/qmgr[33961]: 4L1w1y5FpXz6c1M: removed
so, it's as Victor said - your outgoing server accepted mail from you
to you, and your incoming server first refused to accept mail from
your incoming server, then it refused to accept the bounce, both
because of the same reason.
You can filter such mail on your outgoing server, so you don't accept
something you can't deliver.
Or, you can whitelist mail from your outgoing server with null
envelope on your incoming server, so you know what was refused.
... this should be safe if you don't accept or forward such mail to
outside hosts.
Are you aware that body_checks is very lightway compared to e.g. spam
and virus filtering?
Yes I know I understand it but it is more complicated.
example:
1)I get "targeted spam" where in body is "fake link"
2)I block this in body_checks - works perfect (fastest)
3)Before I blocked some emails passed
4)My user send me "a spam sample" and I dont get this
maybe realy good idea is block thats in outgoing serwer with REJECT bla bla
--
