On 12/10/16 21:34, Frank Elsner wrote:
>> the RC2 release candidate build of Exim 4.88
>> Built and signed by myself.
>
> I've installed this version with the same Local/* files as Exim 4.88 RC1
> which works perfect and I encountered this error with RC2.
>
> [frank@siffux src]$ echo test
Hi,
See this config, you'll find a lot useful things:
http://lena.kiev.ua/Lena-eximconf-run.txt
> Оригинално писмо
>От: Dennis Isaías Cervantes dennis.cervan...@tboxplanet.com
>Относно: Re: [exim] block a domain *.top
>До: "'Jeremy Harris'" ,
On Sun, 9 Oct 2016 13:36:32 +0100 Jeremy Harris wrote:
Hi,
> I have built and uploaded to
>
> ftp://ftp.exim.org/pub/exim/exim4/test/
>
> the RC2 release candidate build of Exim 4.88
> Built and signed by myself.
I've installed this version with the same Local/* files as Exim 4.88 RC1
which
Hi,
In acl_check_rcpt put something like this:
deny
senders = /etc/exim/deny_senders
Create file deny_senders and block what you want , like:
*.top
*.br
*.in
> Оригинално писмо
>От: Dennis Isaías Cervantes dennis.cervan...@tboxplanet.com
>Относно: Re: [exim]
Any idea which ACL can I use?
-Mensaje original-
De: Exim-users
[mailto:exim-users-bounces+dennis.cervantes=tboxplanet@exim.org] En nombre
de Jeremy Harris
Enviado el: miércoles, 12 de octubre de 2016 7:45 a. m.
Para: exim-users@exim.org
Asunto: Re: [exim] block a domain *.top
On
On 12/10/16 14:39, Dennis Isaías Cervantes wrote:
> how it could do to prevent a particular domain to write me, but in total for
> example * .TOP
At some suitable point in your ACLs, probably the recipient ACL,
deny domains = *.top
Docs at: http://exim.org/exim-html-current/doc/html/spec_html/
Hello everyone
how it could do to prevent a particular domain to write me, but in total for
example * .TOP
excuse my English, I use a translator
I would appreciate help
regards
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at
Hi.
Docs say that $tls_sni has raw data from client:
"Great care should be taken to deal with matters of case, various injection
attacks in the string (../ or SQL), and ensuring that a valid filename can
always be referenced; it is important to remember that $tls_sni is arbitrary
unverified
W dniu 11.10.2016 o 17:18, Hardy pisze:
> Thanks for all your input. But some of you missed my point. I admit, the
> subject is OT, and I was too lengthy in explanation.
>
> Shorter
> We DO accept mail from a trusted host, not under our control. THAT hosts
> was tricked to accept spam. To
Hi,
the sender verification does not use TLS encrypted connections to verify
senders:
550-Verification failed for
550-Called: 83.246.80.130
550-Sent: RCPT TO:
550-Response: 550 Receiver does not accept unencrypted connections
550 Sender verify
Hi all,
as i switched form an old comodo cert to a new one, also comodo, we
encountered problems with iOS 10 devices.
They can use exim, but fail to use dovecot, with the same cert and they
worked all before the cert exchange.
As Lets Encrypt was used temporarily as a substitution, the use of
11 matches
Mail list logo