Re: [exim] Solved: Routing based on sender and recipient

2023-01-04 Thread tt-admin via Exim-users
s+tt-admin=intranett...@exim.org] Im Auftrag von tt-admin via Exim-users Gesendet: Mittwoch, 4. Januar 2023 06:32 An: exim-users@exim.org Betreff: [exim] Routing based on sender and recipient Good Morning, we need to route some mail traffic based on sender AND recipient if that's possible. Con

[exim] Routing based on sender and recipient

2023-01-03 Thread tt-admin via Exim-users
Good Morning, we need to route some mail traffic based on sender AND recipient if that's possible. Configuration as of now: Everything from * to @example.com goes to 10.10.10.10 myrouter: driver = manualroute domains = example.com transport = remote_smtp route_list = * 10.10.10.10 What we

Re: [exim] Eximm Bounce Subject add original Subject of failing e-mail

2022-06-15 Thread tt-admin via Exim-users
@exim.org Betreff: Re: [exim] Eximm Bounce Subject add original Subject of failing e-mail On 15/06/2022 11:10, tt-admin via Exim-users wrote: > is there a way to add the original subject to a bounce e-mail instead of > just "Mail delivery.."? There's a docs chapter on customizing

[exim] Eximm Bounce Subject add original Subject of failing e-mail

2022-06-15 Thread tt-admin via Exim-users
Hi, is there a way to add the original subject to a bounce e-mail instead of just "Mail delivery.."? We already use an exim filter for bounces: if ("$return_path" is "" and ... then headers add "New-Subject: #BOUNCE# $h_subject:" headers remove subject headers add "Subject: $h_new-subject:"

Re: [exim] 2 hours delay (gnutls_handshake): timed out: delivering unencrypted to

2022-04-27 Thread tt-admin via Exim-users
C Aitchison via Exim-users Gesendet: Sonntag, 24. April 2022 11:37 An: tt-admin Cc: exim-users@exim.org Betreff: Re: [exim] 2 hours delay (gnutls_handshake): timed out: delivering unencrypted to On Tue, 19 Apr 2022, tt-admin via Exim-users wrote: > Just finished testing - the problem still occ

Re: [exim] 2 hours delay (gnutls_handshake): timed out: delivering unencrypted to

2022-04-19 Thread tt-admin via Exim-users
-admin=intranett...@exim.org] Im Auftrag von Andrew C Aitchison via Exim-users Gesendet: Donnerstag, 31. März 2022 12:35 An: tt-admin Cc: exim-users@exim.org Betreff: Re: [exim] 2 hours delay (gnutls_handshake): timed out: delivering unencrypted to On Thu, 31 Mar 2022, tt-admin via Exim-users wrote

Re: [exim] 2 hours delay (gnutls_handshake): timed out: delivering unencrypted to

2022-04-07 Thread tt-admin via Exim-users
o:exim-users-bounces+tt-admin=intranett...@exim.org] Im Auftrag von Andrew C Aitchison via Exim-users Gesendet: Donnerstag, 31. März 2022 12:35 An: tt-admin Cc: exim-users@exim.org Betreff: Re: [exim] 2 hours delay (gnutls_handshake): timed out: delivering unencrypted to On Thu, 31 Mar 2022, tt-admin vi

Re: [exim] 2 hours delay (gnutls_handshake): timed out: delivering unencrypted to

2022-03-31 Thread tt-admin via Exim-users
unencrypted to On Wed, Mar 30, 2022 at 02:53:45PM +0200, tt-admin via Exim-users wrote: > Continuation of the strace; > > 6649 select(8, [7], NULL, NULL, {tv_sec=60, tv_usec=0} > 6671 <... recvfrom resumed> 0x56352d0bd71b, 324, 0, NULL, NULL) = -1 > ECONNRESET (Connection

Re: [exim] 2 hours delay (gnutls_handshake): timed out: delivering unencrypted to

2022-03-30 Thread tt-admin via Exim-users
+tt-admin=intranett...@exim.org] Im Auftrag von Andrew C Aitchison via Exim-users Gesendet: Mittwoch, 30. März 2022 09:19 An: tt-admin Cc: exim-users@exim.org Betreff: Re: [exim] 2 hours delay (gnutls_handshake): timed out: delivering unencrypted to On Wed, 30 Mar 2022, tt-admin via Exim-users w

Re: [exim] 2 hours delay (gnutls_handshake): timed out: delivering unencrypted to

2022-03-30 Thread tt-admin via Exim-users
>I wonder what 1758 and 1762 were doing all that time - >I presume there is no other mention of 1762 in the log ? No, they are not mentioned besides the exigrep output. >If you see any more of these stuck in the queue, can you get an lsof >and a truss/strace/ltrace of the processes ? Appreciate

Re: [exim] 2 hours delay (gnutls_handshake): timed out: delivering unencrypted to

2022-03-30 Thread tt-admin via Exim-users
>Does > exigrep 1nWC1t-0001kn-G2 /var/log/exim4/mainlog-202203* >(or where ever your exim logs are) show anything for the "other process" ? I'm afraid not, here you see two logs from yesterday (complete exigrep output without sensitive information): 2022-03-29 10:02:40.626 [1758]

Re: [exim] 2 hours delay (gnutls_handshake): timed out: delivering unencrypted to

2022-03-29 Thread tt-admin via Exim-users
>So, it might not be that one then. Were there any other >operations that might have stepped the system's notion >of time? No - and the uptime of the server is 325 days, but the problem occurs daily since 2020-03-04. I just restarted the exim daemon, for what it's worth. -- Cheers, Marc --

Re: [exim] 2 hours delay (gnutls_handshake): timed out: delivering unencrypted to

2022-03-25 Thread tt-admin via Exim-users
] Im Auftrag von Jeremy Harris via Exim-users Gesendet: Donnerstag, 24. März 2022 01:40 An: exim-users@exim.org Betreff: Re: [exim] 2 hours delay (gnutls_handshake): timed out: delivering unencrypted to On 22/03/2022 11:00, tt-admin via Exim-users wrote: > Exim version 4.90_1 #4 built 30-Apr-2021

[exim] 2 hours delay (gnutls_handshake): timed out: delivering unencrypted to

2022-03-23 Thread tt-admin via Exim-users
Hi all, got a sending e-mail relay here, Ubuntu 18.04 LTS. About 22k e-mails sending volume per day. There are two receiving e-mail servers that are experiencing delays (~2 hours) when receiving e-mails from us. This does not happen for every e-mail we're sending tot them, but for some. Log if