Il 31/01/2025 10:53, Jeremy Harris via Exim-users ha scritto:
Well, you've not said what version Exim you are running so I
can only guess it's something modern. You could split out
to separate named-queues during reception, and have separate
queue-runners. Or you could run two totally separate
Hello everyone,
I have a remote_smtp transport configured to send messages using the
same interface that originally received such message.
All is working well a part from one specific case: defers.
When messages are deferred due to termporary errors from the remote
hosts, it happens that aft
On 30.01.2025 18:33, Andreas Metzler via Exim-users wrote:
libspf2 also comes with a command-line program (spfquery) - Perhaps Patrik
can reproduce the issue with spfquery.
$ echo "1.1.1.1"a...@many-spf.hp-mail-infra-test-01.ch helohost.com | spfquery
-f -
StartError
Context: Failed to query M
On 31/01/2025 10:08, Matteo Bonora via Exim-users wrote:
Splitting the messages in different queues is interesting though. Could you
point me to some documentation on how to implement that?
https://exim.org/exim-html-4.93/doc/html/spec_html/index.html
Concept index. Named queues, and the "qu
Unfortunately I cannot do that...
That would be detrimental for hosts which rate limits the connection number.
We currently have "connection_max_messages = 20"
Setting it to an higher value would get us blocked due to "too many
messages in one connection". Setting it to a lower value we would
On 30/01/2025 18:34, Matteo Bonora via Exim-users wrote:
Is there a way to disable or control this behavior?
Try setting "connection_max_messages = 1" on the transport.
--
Cheers,
Jeremy
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/list
On 31/01/2025 09:30, Matteo Bonora via Exim-users wrote:
I'm open to alternatives ;)
Well, you've not said what version Exim you are running so I
can only guess it's something modern. You could split out
to separate named-queues during reception, and have separate
queue-runners. Or you could
Is anyone using Exim with OpenSSL v1.1.1 or earlier ?
Context: https://bugs.exim.org/show_bug.cgi?id=3131
and the mailop list message below.
(I still have a VM that can build Exim 4.98 with OpenSSL 1.O.2u
but would not dare run it in listening mode.)
Thanks,
--
Andrew C. Aitchison
On Thu, Jan 30, 2025 at 07:34:31PM +0100, Matteo Bonora via Exim-users wrote:
> I have a remote_smtp transport configured to send messages using the same
> interface that originally received such message.
Please, post here configuration of this transport, and explain
how outgoing interface is bo
Il 31/01/2025 15:05, Evgeniy Berdnikov via Exim-users ha scritto:
Attenzione: Questa email arriva da un mittente insolito.
Attenzione: Assicurati che sia qualcuno di cui ti fidi.
On Thu, Jan 30, 2025 at 07:34:31PM +0100, Matteo Bonora via Exim-users wrote:
I have a remote_smtp transport configu
On 31/01/2025 14:38, Jeremy Harris via Exim-users wrote:
On 31/01/2025 11:35, Andrew C Aitchison via Exim-users wrote:
Is anyone using Exim with OpenSSL v1.1.1 or earlier ?
There's a buildfarm system running 1.0.2g (Solaris 10)
and another running 1.0.2t (Solaris 11).
Any informant notes tha
On 31/01/2025 11:35, Andrew C Aitchison via Exim-users wrote:
Is anyone using Exim with OpenSSL v1.1.1 or earlier ?
There's a buildfarm system running 1.0.2g (Solaris 10)
and another running 1.0.2t (Solaris 11).
--
Cheers,
Jeremy
--
## subscription configuration (requires account):
## htt
On 31/01/2025 17:08, Matteo Bonora via Exim-users wrote:
This transport is really very simple and the bonding is done by the "interface =
$interface_address" line. It works perfectly in every case but the one I described.
Commit 237b2df13410 looks relevant.
--
Cheers,
Jeremy
--
## subscript
Why you have altered the original message?
It is not fair and offensive.
On Fri, 31 Jan 2025, Matteo Bonora via Exim-users wrote:
Il 31/01/2025 15:05, Evgeniy Berdnikov via Exim-users ha scritto:
Attenzione: Questa email arriva da un mittente insolito.
Attenzione: Assicurati che sia qualcuno d
Ehm... Sorry?
If you are referring to the following 2 lines:
Attenzione: Questa email arriva da un mittente insolito.
Attenzione: Assicurati che sia qualcuno di cui ti fidi.
They are simply a warning from our Email Security Gateway, added on top of
messages, to alert the recipient about message
15 matches
Mail list logo
