Traceability of message delivery

Dear Paul/Aaron,

Hope this has not been already queried and answered.

Is there a way to trace the delivery of a message in logs,
once it is
transfered from an MTA to DBMail (MDA) and to the point
where it is
extracted (by pop) or viewed (by imap).

I know that now in version 2.2.x, DBMail is adding a header
(X-DBMail-PhysMessage-ID) to the e-mail with an ID number.
Can this be
extended to support what I am asking.

Or Is this going to be a new feature altogether ?

Thanks in advance.

Lasantha.
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

Lasantha Marian wrote:
> Dear Paul/Aaron,
> 
> Hope this has not been already queried and answered.
> 
> Is there a way to trace the delivery of a message in
logs, once it is
> transfered from an MTA to DBMail (MDA) and to the point
where it is
> extracted (by pop) or viewed (by imap).

insertion is logged at trace level 3 and above.
retrieval by pop will update the status field of a message
(0->1)
viewing in imap will update the seen_flag field of a message
(0->1) unless the
mailbox is read-only, or opened read-only.

> 
> I know that now in version 2.2.x, DBMail is adding a
header
> (X-DBMail-PhysMessage-ID) to the e-mail with an ID
number. Can this be
> extended to support what I am asking.

That header is no longer added since it messes with the
message size *after*
insertion, and it didn't really add value.

> Or Is this going to be a new feature altogether ?

There are some plans to make the logging more compact and
amenable to parsing.
(thing apache's access logs). But nothing has been done
about that yet. Feel
free to sponsor us or buy commercial support if you need
this.

-- 
 
____________________________________________________________
____
  Paul Stevens                                      paul at
nfg.nl
  NET FACILITIES GROUP                     GPG/PGP:
1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

Lasantha Marian wrote:
>>
>> insertion is logged at trace level 3 and above.
>> retrieval by pop will update the status field of a
message (0->1)
>> viewing in imap will update the seen_flag field of
a message (0->1) unless the
>> mailbox is read-only, or opened read-only.
>>   
> But how can one maintain the continuous traceability
between all these
> activities. I am thinking of a scenario where a unique
ID (eg:
> AAAAAA-AA-NNNNNN) being given to every message instance
inserted and
> then same is referred during retrieval and/or viewing.
During the
> insertion, special care should be given to log the link
between MTA's
> message ID to DBMail's (MDA) ID's.

Would you really want to keep track of all messages being
viewed? That's
currently not possible using just the logs. But making that
an optional logging
feature is not very complex.

Maintaining tracebility between the MTA and dbmail-lmtpd's
insertion can most
likely be done by making the message_idnr part of the LMTP
response, much like
the queue-id of a receiving MTA is part of the reponse when
mail is relayed.

> If commercial support is opted what are the details ?
What/where are the
> sponsorship options available for us to consider ?

For more details concerning commercial support, please visit
http://dbmail.eu


-- 
 
____________________________________________________________
____
  Paul Stevens                                      paul at
nfg.nl
  NET FACILITIES GROUP                     GPG/PGP:
1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail