On 2018-05-31 at 21:41 -0500, Martin McCormick via Exim-users wrote:
> The last part of this long message is the log of the
> delivery attempt. As you see, I do now log in to the smarthost
> and the only reason for the failure is that the sender name gets
> changed.
>
> The ISP knows
I am replying to 2 postings.
Jeremy Harris via Exim-users writes:
> This will be the magic bit, and the syntax looks right, so
> best guess is that you placed it in the wrong place.
Thank you!
I certainly did but I am not quite good yet.
> Compare that file with:
>
>
Hi All,
I have relay server, need to limit number of relayed messages to
2000/hour/Client , need to drop additional mail after that until rate
period ends.
I tried settings below with no luck.
Any ideas
Thanks
acl_check_rcpt:
defer ratelimit = 2000 /1h / strict / $sender_host_address
Hello Heiko,
thanks for your fast analysis.
On 31.05.2018 17:38, Heiko Schlittermann via Exim-users wrote:
> I'm not sure how the sa_exim processing works, I do not use it for long
> time now. Does it see the original spooled message and modifies it?
> After this step, Exim does its own
> On May 31, 2018, at 2:05 PM, Emanuel Gonzalez via Exim-users
> wrote:
>
> The problem occurs when my clients send through a mail client (example
> thunderbird)
>
Which is when Exim verifies the *client's* certificate.
> tls_certificate = /opt/exim/ssl/exim2.crt
> tls_privatekey =
The problem occurs when my clients send through a mail client (example
thunderbird)
I use this setting on exim:
daemon_smtp_ports = 25 : 465 : 587
tls_on_connect_ports = 465
openssl_options = +no_sslv2 +no_sslv3
MAIN_TLS_ENABLE = yes
tls_certificate = /opt/exim/ssl/exim2.crt
tls_privatekey
On 31 May 2018, at 18:01, Emanuel Gonzalez via Exim-users
wrote:
> any ideas?
You appear to have obfuscated the original error (the MX for blabla.com doesn’t
offer STARTTLS, for example), and you’ve not given details of the server you’re
connecting to or your configuration, so I’d guess that
On 05/31/2018 05:02 AM, Martin McCormick via Exim-users wrote:
> set passwd.client as follows:
> *.suddenlink.net:marti...@suddenlink.net:somePaSsword
have you checked
man 5 exim4-config_files
and that the hostname in passwd.client is the rDNS of your smarthost, so
in your case could be
any ideas?
--
## 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/
Martin McCormick via Exim-users (Do 31 Mai 2018 05:02:35
CEST):
> In the first place one can not add protocol=smtps to
> /etc/exim4/conf.d/transport/30_exim4-config_remote_smtp_smarthost
> as this throws an error now that protocol=smtps is not understood.
Try
$ exim -bP config
and
Hi,
it looks as if the last SA-Exim header eliminated the blank line that
separates header and body.
I'm not sure how the sa_exim processing works, I do not use it for long
time now. Does it see the original spooled message and modifies it?
After this step, Exim does its own processessing,
On 05/31/2018 04:02 AM, Martin McCormick via Exim-users wrote:
> It was also necessary to add a line to
>
> /etc/exim4/conf.d/transport/30_exim4-config_remote_smtp_smarthost
>
> in a certain place that indicated protocol=smtps
This will be the magic bit, and the syntax looks right, so
Hello,
as this gets quite long a short overiew in advance: After upgrading to
exim 4.90_1 (Ubuntu 18.04), I observe message corruption in the queue in
rare cases. All corrupted messages are from linux kernel mailing list. I
can eliminate file system as reason for corruption.
Whole story:
Since
Debian wheezy had a version of exim4 whose number was
4.7x, maybe even as high as 4.79. With a little help, I got exim
to establish a smtps session with the internet service provider
in our area. The recipe was to:
dpkg-reconfigure exim4-config and be sure to select
mail
14 matches
Mail list logo
