Greetings, All!
Can't seems to grasp the origin of the issue.
If I send the mail to the same addresses myself, it is coming through, so is
much of the other mail traffic.
info@ is virtual, bulk of the mail coming its way, no problem.
vera@ is real local address.
If I grep similar entries in the
following earlier advice here, I've finally tried to set DKIM
I think I'm getting there, but I've noticed it's doubling up[1], with amavis
which one should be bypassed, and, how to do so ?
thanks, V
from main.cf
..
content_filter = smtp-amavis:[127.0.0.1]:10024
smtp-amavis_destination_recipient
On 24.05.19 21:19, li...@sbt.net.au wrote:
following earlier advice here, I've finally tried to set DKIM
I think I'm getting there, but I've noticed it's doubling up[1], with amavis
which one should be bypassed, and, how to do so ?
very hard to say withoutmore info.
What do milters on ports 8
On Fri, May 24, 2019 9:31 pm, Matus UHLAR - fantomas wrote:
>> which one should be bypassed, and, how to do so ?
>
> very hard to say withoutmore info. What do milters on ports 8891 and 8893
> do?
OpenDKIM and OpenDMARC
I was just installing DKIM followed by DMARC using Steve Jenkins howto
htt
Andrey Repin:
> Greetings, All!
>
> Can't seems to grasp the origin of the issue.
> If I send the mail to the same addresses myself, it is coming through, so is
> much of the other mail traffic.
Perhaps the origin is that *you* are not sending email from
84.204.28.35.
Wietse
> info@ is
Hi All , Need some guidance on how we can configure transport rules which has
to route email based on both Sender and recipient domains .
Our transport_maps ( in my org ) have been simple and configured in
traditional fashion:
like receive email from
Domain1 >> smtp:Gateway1
Domain2 >> smtp:Gate
VB:
> Hi All , Need some guidance on how we can configure transport rules which has
> to route email based on both Sender and recipient domains .
>
> Our transport_maps ( in my org ) have been simple and configured in
> traditional fashion:
>
> like receive email from
>
> Domain1 >> smtp:Gateway
Thank you Wietse ,
( Absolutely delighted to hear from the man himself ) _/\_
Ty.
--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
I have an active email address that only receives spam (it is an address that
wasn't used for years but I've recently reactive to see just how much spam an
unprotected decades old account that hasn't accepted mail since 2006 would get).
Anyway, what I would like to do is somehow blacklist any IP
On Fri, May 24, 2019 at 10:38:29AM +0300, Andrey Repin wrote:
> May 24 08:07:39 mxs postfix/smtp/smtpd[1938]: NOQUEUE: reject: RCPT from
> mail.regionspb.net[84.204.28.35]: 450 4.7.0 : Recipient
> address rejected: defer_if_reject requested; from=
> to= proto=ESMTP helo=
> May 24 10:13:22 mxs p
On 5/24/2019 11:33 AM, @lbutlr wrote:
I have an active email address that only receives spam (it is an address that
wasn't used for years but I've recently reactive to see just how much spam an
unprotected decades old account that hasn't accepted mail since 2006 would get).
Anyway, what I woul
On 24 May 2019, at 11:23, Noel Jones wrote:
> On 5/24/2019 11:33 AM, @lbutlr wrote:
>> I have an active email address that only receives spam (it is an address
>> that wasn't used for years but I've recently reactive to see just how much
>> spam an unprotected decades old account that hasn't acc
Hi there,
I've done that by building a policy filter that bans those IPs using
iptables whenever those trap accounts get reached.
It wasn't that easy, but its beautiful how it's working.
Chain SPAMBLOCK (X references)
pkts bytes target prot opt in out source
destination
0 0
On 24 May 2019, at 12:52, Rafael Azevedo wrote:
>
> Hi there,
>
> I've done that by building a policy filter that bans those IPs using
> iptables whenever those trap accounts get reached.
Oh, well, that sounds lovely. Is it sharable?
(shouldn't be much iss ti adapt it to pf)
> It wasn't that
Greetings, Viktor Dukhovni!
> On Fri, May 24, 2019 at 10:38:29AM +0300, Andrey Repin wrote:
>> May 24 08:07:39 mxs postfix/smtp/smtpd[1938]: NOQUEUE: reject: RCPT from
>> mail.regionspb.net[84.204.28.35]: 450 4.7.0 : Recipient
>> address rejected: defer_if_reject requested;
>> from= to= proto=
15 matches
Mail list logo