On Wed, 29 Nov 2017 20:21:47 + Jeremy Harris wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> I have built, signed and uploaded RC3 of Exim 4.90 to the ftp site:
Hi,
I've still problems to compile on an actual Fedora 26 system:
gcc tls.c
In file included from tls.c:122:0:
On 29/11/17 22:44 Jeremy Harris wrote:
> On 29/11/17 22:18, Sebastian Arcus via Exim-users wrote:
> > Is there a way to build a router only for verification of local
> > addresses for inbound messages? As far as I can tell, verify =
recipient
> > doesn't work when Exim delivers to Dovecot
On 29/11/17 23:25, Phil Pennock wrote:
On 2017-11-29 at 22:18 +, Sebastian Arcus via Exim-users wrote:
Is there a way to build a router only for verification of local addresses
for inbound messages? As far as I can tell, verify = recipient doesn't work
when Exim delivers to Dovecot through
On 2017-11-29 at 22:18 +, Sebastian Arcus via Exim-users wrote:
> Is there a way to build a router only for verification of local addresses
> for inbound messages? As far as I can tell, verify = recipient doesn't work
> when Exim delivers to Dovecot through dovecot-lda - as this always
On 28/11/17 22:52, Jeremy Harris wrote:
> On 26/11/17 09:46, Torsten Tributh via Exim-users wrote:
>> I also recognized that in these cases the AUTH-acl will also be called
>> after ACL-DATA.
>
> That's probably a (minor) bug. Thanks for pointing it out.
Bug 2203 raised for that.
--
Cheers,
Exim maintainers, developers, users,
We have released a security release today.
The latest Exim release is now 4.89.1
This release contains all fixes we did on the exim-4_89+fixes branch
since the exim-4_89 release. This includes the fixes for
CVE-2017-16943 and CVE-2017-16944.
Tarballs are in
On 29/11/17 22:18, Sebastian Arcus via Exim-users wrote:
> Is there a way to build a router only for verification of local
> addresses for inbound messages? As far as I can tell, verify = recipient
> doesn't work when Exim delivers to Dovecot through dovecot-lda - as this
> always verifies the
Is there a way to build a router only for verification of local
addresses for inbound messages? As far as I can tell, verify = recipient
doesn't work when Exim delivers to Dovecot through dovecot-lda - as this
always verifies the recipient (as long as the domain is in
+local_domains) no matter
>>> What i'm missing?!
>> quote_ldap_dn ?
> No, seems no. Same result.
Boh. I've done some more tests, but insted of using:
exim -be
i've used:
exim -d+deliver -v -bt test@domain
and my LDAP query, as expected, work. The query finally is:
${lookup ldapm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I have built, signed and uploaded RC3 of Exim 4.90 to the ftp site:
ftp://ftp.exim.org/pub/exim/exim4/test/
Sha256 sums:
bf4ff09ba8d045e01dc559bddc50fb21888ef861d4fa59ff6c858236f3877092
exim-4.90_RC3.tar.bz2
> From: Emanuel Gonzalez
> I have an idea to avoid sending spam from my server. Is it possible
> to create a rule so that when it is sent to a recipient, the mail
> is discarded and an alert arrives by email?
This code sends an alert by email:
https://github.com/Exim/exim/wiki/BlockCracking
--
IP addresses change constantly so adding them to a file is not useful.
Regards,
De: Olaf Hopp
Enviado: miércoles, 29 de noviembre de 2017 12:39:06
Para: exim-users@exim.org
Cc: emanuel_gonza...@live.com.ar
Asunto: Re: [exim] ACL block
On 11/29/2017 02:43 PM, Emanuel Gonzalez wrote:
Hello.!!
my idea is to block the IP that makes the unsuccessful login attempts to the
smtp service.
On the web I found the following rule, but not if it is what I need.
acl_smtp_auth:
dropmessage = authentication is
Hi,
See this.
https://github.com/Exim/exim/wiki/BlockCracking
Best Regards.
> Оригинално писмо
>От: Emanuel Gonzalez emanuel_gonza...@live.com.ar
>Относно: [exim] ACL block incorrect authentication data
>До: "exim-users@exim.org"
>Изпратено на:
On 29/11/17 13:23, Emanuel Gonzalez wrote:
> 2017-11-29 09:40:56 fixed_login authenticator failed for (shkhHHO7Wf)
> [220.164.38.211]: 535 Incorrect authentication data (set_id=zu)
> 2017-11-29 09:41:11 fixed_login authenticator failed for (7ouBtZ1fzi)
> [220.164.38.211]: 535 Incorrect
Hello!
On Wed, 29 Nov 2017 at 13:23:55 (+), Emanuel Gonzalez wrote:
> I use fail2ban with iptables to block the brute-force attack, but on some
> virtual servers I do not use iptables.
> 2017-11-29 09:40:56 fixed_login authenticator failed for (shkhHHO7Wf)
> [220.164.38.211]: 535
Hello.!!
my idea is to block the IP that makes the unsuccessful login attempts to the
smtp service.
On the web I found the following rule, but not if it is what I need.
acl_smtp_auth:
dropmessage = authentication is allowed only once per
message
Hello.!!
I use fail2ban with iptables to block the brute-force attack, but on some
virtual servers I do not use iptables.
2017-11-29 09:40:56 fixed_login authenticator failed for (shkhHHO7Wf)
[220.164.38.211]: 535 Incorrect authentication data (set_id=zu)
2017-11-29 09:41:11 fixed_login
some help??
Regards.!
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
19 matches
Mail list logo