Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: exim: dev

[Bug 1031] Implement database logging of completed remote delivery

 

 

exim dev RSS feed   Index | Next | Previous | View Threaded


axel.rau at chaos1

Jun 5, 2012, 6:02 AM

Post #1 of 10 (859 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




--- Comment #11 from Axel Rau <axel.rau [at] chaos1> 2012-06-05 14:02:12 ---
Am 02.04.2012 um 21:50 schrieb Kris Oye:

> I would really like to see this patch included in HEAD. I need the ability to
> report delivery times and elapsed time and this is so much better than combing
> logs for a successful remote transport!
We seem to be on the no-win trip here )-:

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


--
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/ ##


nigel at exim

Jun 5, 2012, 10:14 AM

Post #2 of 10 (820 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

Nigel Metheringham <nigel [at] exim> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |nigel [at] exim




--- Comment #12 from Nigel Metheringham <nigel [at] exim> 2012-06-05 18:14:16 ---
See additional exim-dev discussion
https://lists.exim.org/lurker/message/20120605.160403.7124fe4e.en.html
https://lists.exim.org/lurker/message/20120605.171055.966806d1.en.html


--
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/ ##


brent at servuhome

Jun 5, 2012, 7:40 PM

Post #3 of 10 (817 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

Brent Jones <brent [at] servuhome> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |brent [at] servuhome




--- Comment #13 from Brent Jones <brent [at] servuhome> 2012-06-06 03:40:15 ---
I could see many handy uses of this in my workload as well.
One such case would be a simple "Last message received date" per-user mailbox,
which would be easier to use this patch rather than shoehorn UPDATES as part of
a router or transport (if that is even possible).
Reputation would be nice as well, to query reputation to a recipient domain,
and avoid using servers on an outbound relay rotation that have a bad/poor
reputation to a recipient (ie. stop sending mail out of a server that is
already rate limited by Yahoo)


--
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/ ##


tlyons at ivenue

Jun 6, 2012, 7:11 AM

Post #4 of 10 (814 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 #14 from Todd Lyons <tlyons [at] ivenue> 2012-06-06 15:11:19 ---
(In reply to comment #12)
> See additional exim-dev discussion
> https://lists.exim.org/lurker/message/20120605.160403.7124fe4e.en.html
> https://lists.exim.org/lurker/message/20120605.171055.966806d1.en.html

I don't want to derail Axel's work, but I want to explore Nigel's different
approach a bit.

On Tue, Jun 5, 2012 at 10:10 AM, Nigel Metheringham <nigel [at] dotdot> wrote:
> On top of Todd's comments...
>
> This feels a bit like making a specific special case function where
> there could be something more generic... would we do better running
> something ACL like at the end of a delivery attempt which could do
> logging or maybe something else...

I like the idea of a post-router ACL, but I agree (with your "something ACL
like") that the typical application of an ACL doesn't really apply because the
verbs accept, defer, deny, discard, and drop really have no meaning after the
router has run. Just silently skip the function of the verb and still process
the conditions. The warn verb would serve the most useful purpose. The
require verb has potential, but I can't think of any way of using it that would
be useful post transport, unless you can use it to signal to a subsequent
transport call (i.e. prior lookup failed because database is unreachable, etc)
but *that* approach seems laden with opportunities for failure. Off the cuff,
I think only processing warn statements and conditions only for the rest would
be the preferred approach.

> And I can see why you might have a purpose for just *remote* deliveries,

Hmmm, I didn't catch that it was remote deliveries only. In my personal
situtation, I would need to log everything. I also log spam rules matched, SPF
results, etc, which is not going to be available at this juncture unless I
stuff it into a connection or message variable. And I need to log it when it
rejects an email, which does not get to a transport, which means I personally
would need to add the logging there too.

> but its another specialisation which might be better generalised out -
> maybe its just a transport attribute, with a condition (or is the
> condition on the transport overall).

I kind of like the concept of a "secondary_logger" attribute generic transport
option. It's sole purpose would be to expand whatever is configured for it.
Such as the ${lookup DBTYPE{...}} , but it could just as easily call some
external script (doesn't scale well, but may be useful for someone). But as
above, will require manual work to log defer or reject verb matches in ACL's
prior to the routers being run.

> We will obviously need some spec file documentation.

If it's accepted as an Experimental Feature, we should omit it from the spec
and from the optionslist (right?). If it gets accepted or adjusted to be a
mainline feature, then we'll slam out that additional documentation.


--
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 6, 2012, 7:36 AM

Post #5 of 10 (816 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 #15 from Jeremy Harris <jgh146exb [at] wizmail> 2012-06-06 15:36:58 ---
So far it smells like we're considering a generic option that can be used on
either a router or a transport, which calls an ACL.
- Do we need both; would just the router-option do (given enough richness of
information fed to the ACL)?
- How should information be fed to the ACL?
- What information?
- Assuming the option causes a post-router (or transport) ACL call, the final
result of the ACL can be ignored. Do we need a separate pre-router (transport)
method? Would the result be useful in that scenario (eg. as a router
precondition)? Could a more general data return be useful?
- Is the same technique applicable to authenticators?


--
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/ ##


nigel at exim

Jun 6, 2012, 8:00 AM

Post #6 of 10 (820 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 #16 from Nigel Metheringham <nigel [at] exim> 2012-06-06 16:00:56 ---
If we are looking at audit logging then it needs to run post transport, so we
know that the transport succeeded (or not - if not its possibly more
important!).


--
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

Jun 6, 2012, 9:54 AM

Post #7 of 10 (815 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 #17 from Axel Rau <axel.rau [at] chaos1> 2012-06-06 17:54:43 ---
Am 06.06.2012 um 16:11 schrieb Todd Lyons:

>>
>> And I can see why you might have a purpose for just *remote* deliveries,
>
> Hmmm, I didn't catch that it was remote deliveries only. In my personal
> situtation, I would need to log everything. I also log spam rules matched, SPF
> results, etc, which is not going to be available at this juncture unless I
> stuff it into a connection or message variable. And I need to log it when it
> rejects an email, which does not get to a transport, which means I personally
> would need to add the logging there too.
Yes, I do that already with standard exim lookups during acl processing.
But there may be a cleaner way to do it.

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


--
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 6, 2012, 11:44 AM

Post #8 of 10 (820 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 #18 from Jeremy Harris <jgh146exb [at] wizmail> 2012-06-06 19:44:31 ---
After the transport runs, certainly (for audit). I'm trying to point out that
if you regard the running of a router to encapsulate the running of the
transport, a post-router audit call can have all of the information that a
post-transport one can, plus other stuff too.


--
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

Jun 6, 2012, 1:24 PM

Post #9 of 10 (822 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
----------------------------------------------------------------------------
Attachment #521 is|0 |1
obsolete| |




--- Comment #19 from Axel Rau <axel.rau [at] chaos1> 2012-06-06 21:24:32 ---
Created an attachment (id=575)
--> (http://bugs.exim.org/attachment.cgi?id=575)
git commit patch file for exim-4_80

Ported from 4.77 to 4.80. Not yet tested with 4.80.


--
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

Jun 11, 2012, 4:22 PM

Post #10 of 10 (754 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 #20 from Axel Rau <axel.rau [at] chaos1> 2012-06-12 00:22:15 ---
Patch tested on 4.80, running on FreeBSD 8.2.
No difference to 4.77 seen.


--
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/ ##

exim dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.