On 04.10.23 19:22, Viktor Dukhovni via Exim-users wrote:
On Wed, Oct 04, 2023 at 12:49:29PM -0400, Chris Siebenmann via Exim-users wrote:
Sure, one can expose every internal host as a reachable email subdomain,
optionally equivalent to the main domain, but this is not a good idea.
Email address
On 04.10.23 16:34, Chris Siebenmann wrote:
Now I would like to configure this server as a smarthost, so it will
forward emails from my desktop computers (without static IP or DNS).
Also, I'd like to have unique mailnames for each desktop, like
.mydomain.org, to better identify where the mail orig
On 04.10.23 15:05, Evgeniy Berdnikov via Exim-users wrote:
On Wed, Oct 04, 2023 at 02:11:27PM +0200, Mario Emmenlauer via Exim-users wrote:
I wanted sender verification only for non-authenticated users. The
spam protection is (for me) not relevant for authenticated users.
They are assumed to be
On 04/10/2023 01:03, Paul Vinkenoog via Exim-users wrote:
And I see the patched version has been pushed to Epel 9 updates-testing
yesterday, so I expect it will appear soon on Epel.
It may take up to 7 days, depending on how many people test it and add
feedback [1] (plus when, and of what nat
On 04.10.23 15:59, Mario Emmenlauer wrote:
On 04.10.23 15:05, Evgeniy Berdnikov via Exim-users wrote:
On Wed, Oct 04, 2023 at 02:11:27PM +0200, Mario Emmenlauer via Exim-users wrote:
I wanted sender verification only for non-authenticated users. The
spam protection is (for me) not relevant for
On 04/10/2023 10:01, Heiko Schlittermann via Exim-users wrote:
[about libspf2]
while the recent CVEs addressed some issues that existed in Exim, there
seems to be at least one issue that is related to a library we
potentially use.
ZDI-23-1472 | ZDI-CAN-17578 | CVE-2023-42118 | Exim Bug 3032
F
On Wed, Oct 04, 2023 at 07:59:21PM -0400, Chris Siebenmann via Exim-users wrote:
> Another, much more brute force way (if you don't have a common
> /etc/passwd file that's somehow distributed around) is to change the
> /etc/passwd GECOS field for relevant accounts to have the machine's name
> in i
On Wed, Oct 04, 2023 at 09:36:12PM +0200, Mario Emmenlauer via Exim-users wrote:
> Since this is auto-generated system mail, there is absolutely no chance that I
> would want to reply to such email, now or in the future.
Right way is to make ALL sender's addresses routable, even for
automaticall
On 05.10.23 11:14, Evgeniy Berdnikov via Exim-users wrote:
On Wed, Oct 04, 2023 at 09:36:12PM +0200, Mario Emmenlauer via Exim-users wrote:
Since this is auto-generated system mail, there is absolutely no chance that I
would want to reply to such email, now or in the future.
Right way is to
On 05.10.23 01:59, Chris Siebenmann via Exim-users wrote:
So for me, the exim email system on the desktop computers is
exclusively used by the Linux operating system. I do not enable
incoming email, so all mails are generated by the various services
that come with Linux. Some of these services ar
On 05.10.23 01:37, Viktor Dukhovni via Exim-users wrote:
On Wed, Oct 04, 2023 at 09:36:12PM +0200, Mario Emmenlauer wrote:
Rather than leak user@.domain forms out to the public
Internet, explain and solve the real problem that not masquerading
all users behind the primary domain is supposed to
Dňa 5. októbra 2023 13:29:46 UTC používateľ Mario Emmenlauer via Exim-users
napísal:
>Yes, this is something I did not really consider :( But after the
>suggestions here on the list I can value this. I'll go for an approach
>that keeps the addresses routable. Thanks for pointing that out!
I use
On 8.09.2023 12:16, Mike Clarke via Exim-users wrote:
I've just upgraded from 4.95 to 4.96 and have started to have problems with
exim_tidydb
Exim version 4.96 #1 (FreeBSD 13.2) built 29-Aug-2023 15:38:40
I had similar problem on FreeBSD but on 12.4 (and visible after upgrade
from 4.95 to 4.9
13 matches
Mail list logo
