Re: Temporarily blocked...not

Gib Henry <[email protected]> Thu, 27 Oct 2016 14:58:56 +0200
Newsgroups gmane.mail.cgatepro.general
Message-ID <[email protected]>
I didn’t say it should. However, any SMTP server which checks your DMARC 
record may reject anything you post via a list like CommuniGate Pro, so 
you’re not getting to everyone on the list.  One option is to add the 
list server as an authorized sender for your domain.


On 10/27/16 2:27 PM, Palvelin Postmaster wrote:
> Yes, I use DMARC. Why should *.stalker.com be an authorized sender for my domain?
>
>
>> On 27 Oct 2016, at 15:11, Gib Henry <[email protected]> wrote:
>>
>> And by the way, I’m guessing you use DMARC.  Your email was tagged “reject” because *.stalker.com is not an authorized sender for palvelin.fi:
>>
>> DMARC: reject
>> Return-Path:
>> <[email protected]>
>>
>> Received: from [72.20.112.40] (HELO stalker.com)
>>    by gibhenry.com (CommuniGate Pro SMTP 6.1.11 _community_)
>>    with ESMTP id 2330255 for
>> [email protected]
>> ; Thu, 27 Oct 2016 01:38:08 -0500
>> X-ListServer: CommuniGate Pro LIST 6.1.12
>> List-Unsubscribe:
>> <mailto:[email protected]>
>>
>> List-ID: <CGatePro.mail.stalker.com>
>> List-Archive:
>> <http://mail.stalker.com:8080/Lists/CGatePro/List.html>
>>
>> Precedence: list
>> Reply-To: "CommuniGate Pro Discussions"
>> <[email protected]>
>>
>> Sender: "CommuniGate Pro Discussions"
>> <[email protected]>
>>
>> To: "CommuniGate Pro Discussions"
>> <[email protected]>
>>
>> From: Palvelin Postmaster
>> <[email protected]>
>>
>> MIME-Version: 1.0
>> Content-Type: text/plain; charset=us-ascii
>> Content-Transfer-Encoding: quoted-printable
>> X-Original-Message-Id:
>> <[email protected]>
>>
>> Date: Thu, 27 Oct 2016 09:37:36 +0300
>> X-Mailer: Apple Mail (2.3251)
>> Message-ID:
>> <[email protected]>
>>
>> Subject: Temporarily blocked...not
>>
>>
>> On 10/27/16 8:37 AM, Palvelin Postmaster wrote:
>>> Hi,
>>>
>>> we get occasional brute force login atttempts. The following log clip shows a couple. The second login attempt would suggest the previous attempt doesn't actually block the host from retrying even though the log entry suggests so. Do I misunderstand something?
>>>
>>> 20:43:21.328 1 POP-006892([173.68.176.196]:4079) failed to open ACCOUNT(cs) for [173.68.176.196]:4079->[83.150.109.27]:110. Error Code=unknown user account
>>> 20:43:21.329 1 POP-006892([173.68.176.196]:4079) [173.68.176.196] temporarily blocked on login failure
>>> 20:43:21.343 1 ROUTER SYSTEM: 'angela' rejected. Error Code=unknown user account
>>> 20:43:21.343 1 POP-006893([173.68.176.196]:3535) failed to open ACCOUNT(angela) for [173.68.176.196]:3535->[83.150.109.28]:110. Error Code=unknown user account
>>> 20:43:21.344 1 POP-006893([173.68.176.196]:3535) [173.68.176.196] temporarily blocked on login failure
>>> 20:43:21.596 1 ROUTER SYSTEM: 'company' rejected. Error Code=unknown user account