Mailing List Archive: exim: dev

[Bug 1031] Implement database logging of completed remote delivery

Index | Next | Previous | View Threaded

jgh146exb at wizmail

Jun 30, 2013, 9:40 AM

Post #1 of 6 (116 views)
Permalink

[Bug 1031] Implement database logging of completed remote delivery

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1031

Jeremy Harris <jgh146exb [at] wizmail> changed:

What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|pdp [at] exim |jgh146exb [at] wizmail

--- Comment #25 from Jeremy Harris <jgh146exb [at] wizmail> 2013-06-30 17:40:36 ---
http://git.exim.org/users/jgh/exim.git/tree/transp_logging_1031

Starts with Axel's patch on 4.80 then merged up to HEAD as of today.
Compiles, and the testsuite runs without complaint. There are no
specific tests for the feature yet, and I'd expect it to be not fully
functional
for cutthrough deliveries.

--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email

--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##

jgh146exb at wizmail

Jun 30, 2013, 9:42 AM

Post #2 of 6 (112 views)
Permalink

[Bug 1031] Implement database logging of completed remote delivery [In reply to]

jgh at wizmail

Jun 30, 2013, 10:52 AM

Post #3 of 6 (106 views)
Permalink

Re: [Bug 1031] Implement database logging of completed remote delivery [In reply to]

On 30/06/13 17:42, Jeremy Harris wrote:
> http://bugs.exim.org/show_bug.cgi?id=1031

The current coding logs on connection problems
in the transport. Verify-callouts also make connections;
how should these be dealt with?

Bear in mind that if cutthrough deliveries are configured
the verify code is making the connection used for delivery.
On the other hand, should such a connection fail in such
a way that does no affect the verification aspect of the
callout, a traditional transport delivery will be attempted.
--
Cheers,
Jeremy

--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##

axel.rau at chaos1

Jul 1, 2013, 10:21 AM

Post #4 of 6 (103 views)
Permalink

[Bug 1031] Implement database logging of completed remote delivery [In reply to]

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1031

Axel Rau <axel.rau [at] chaos1> changed:

What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|Exim 4.77 |4.82

--- Comment #26 from Axel Rau <axel.rau [at] chaos1> 2013-07-01 18:21:46 ---
That is really good news, Jeremy.
I cloned your repository and did a 1st test with my production DB on a test
server.
After applying the attached patch, logging of successful remote delivery seems
to work flawlessly.

Axel

--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email

--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##

axel.rau at chaos1

Jul 1, 2013, 10:26 AM

Post #5 of 6 (103 views)
Permalink

[Bug 1031] Implement database logging of completed remote delivery [In reply to]

------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1031

--- Comment #27 from Axel Rau <axel.rau [at] chaos1> 2013-07-01 18:26:26 ---
Created an attachment (id=641)
--> (http://bugs.exim.org/attachment.cgi?id=641)
git commit based on branch transp_logging_1031

Subject: [PATCH] Set variables for transp_logging if remote delivery

--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email

--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##

Axel.Rau at chaos1

Jul 1, 2013, 12:52 PM

Post #6 of 6 (103 views)
Permalink

Re: [Bug 1031] Implement database logging of completed remote delivery [In reply to]

Jeremy,

Am 30.06.2013 um 19:52 schrieb Jeremy Harris <jgh [at] wizmail>:

> On 30/06/13 17:42, Jeremy Harris wrote:
>> http://bugs.exim.org/show_bug.cgi?id=1031
>
> The current coding logs on connection problems
> in the transport. Verify-callouts also make connections;
> how should these be dealt with?
This should be answered by gedalya [at] gedalya, who requested that feature.
> Bear in mind that if cutthrough deliveries are configured
> the verify code is making the connection used for delivery.
> On the other hand, should such a connection fail in such
> a way that does no affect the verification aspect of the
> callout, a traditional transport delivery will be attempted.
I think, if we log such failures, we should also log the context. How can we feed the context into smtp.c?

Questions:

To create a test for the feature, a database schema is needed. To make this all scriptable, sqlite comes
into mind. I did not find an example where a schema is being created in the test suite.

While testing, I noticed that PostgreSQL-execution-errors are no longer logged in the main log, as used to be with 4.80. Has this changed recently?

Axel
---
PGP-Key:29E99DD6 ☀ +49 151 2300 9283 ☀ computing @ chaos claudius

--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads