Explanation

View: New views
3 Messages — Rating Filter:   Alert me  

Explanation

by Jorge Bastos :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi Paul,

Allow me to ask an explanation:

When running dbmail-util for message cleanup, why do I have :

 

Repairing DBMAIL physmessage integrity...

Ok. Found [256] unconnected physmessages.

Ok. Orphaned physmessages deleted.

 

Repairing DBMAIL partlists integrity...

Ok. Found [0] unconnected partlists.

 

Repairing DBMAIL mimeparts integrity...

Ok. Found [778] unconnected mimeparts.

Ok. Orphaned mimeparts deleted.

 

256 unit’s on one side, and 778 on the other?

Shouldn’t the values match? I mean:

 

Mimeparts = physmessages X 3

 

Or the reason is, ‘cause messages can have one mimepart, or some of them, never a fixed number, correct right?

 

Jorge,


_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev

Re: Explanation

by Paul J Stevens :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Jorge Bastos wrote:

> Ok. Found *_[256]_* unconnected physmessages.
> Ok. Found *_[778]_* unconnected mimeparts.
>
> 256 unit’s on one side, and 778 on the other?
> Shouldn’t the values match? I mean:
>
> Mimeparts = physmessages X 3
>
> Or the reason is, ‘cause messages can have one mimepart, or some of
> them, never a fixed number, correct right?

a plain/text rfc822 message will consist of two mimeparts, like the good
old messageblks storage.
1: rfc822 headers
2: rfc822 body

a message/rfc822 would result in:

1: rfc822 headers
2: mimepart headers
3: mimepart body

a multipart message with only one mimepart will result in at least 5
mimeparts:
1: rfc822 headers
2: multipart preface
3: mimepart headers
4: mimepart body
5: multipart postface


But then a message/rfc822 mimepart can contain a multipart message which
may contain anything. Full recursion.


So there number of mimeparts (M) related to the number of physmessages
(P) is something like:

M = A . P
2 <= A < inf


--
   ________________________________________________________________
   Paul Stevens                                      paul at nfg.nl
   NET FACILITIES GROUP                     GPG/PGP: 1024D/11F8CD31
   The Netherlands________________________________http://www.nfg.nl
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev

Re: Explanation

by Jorge Bastos :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Perfect!

Thanks for the clarification!

> -----Original Message-----
> From: dbmail-dev-bounces@... [mailto:dbmail-dev-
> bounces@...] On Behalf Of Paul Stevens
> Sent: sábado, 10 de Outubro de 2009 21:59
> To: DBMAIL Developers Mailinglist
> Subject: Re: [Dbmail-dev] Explanation
>
> Jorge Bastos wrote:
> > Ok. Found *_[256]_* unconnected physmessages.
> > Ok. Found *_[778]_* unconnected mimeparts.
> >
> > 256 unit’s on one side, and 778 on the other?
> > Shouldn’t the values match? I mean:
> >
> > Mimeparts = physmessages X 3
> >
> > Or the reason is, ‘cause messages can have one mimepart, or some of
> > them, never a fixed number, correct right?
>
> a plain/text rfc822 message will consist of two mimeparts, like the
> good
> old messageblks storage.
> 1: rfc822 headers
> 2: rfc822 body
>
> a message/rfc822 would result in:
>
> 1: rfc822 headers
> 2: mimepart headers
> 3: mimepart body
>
> a multipart message with only one mimepart will result in at least 5
> mimeparts:
> 1: rfc822 headers
> 2: multipart preface
> 3: mimepart headers
> 4: mimepart body
> 5: multipart postface
>
>
> But then a message/rfc822 mimepart can contain a multipart message
> which
> may contain anything. Full recursion.
>
>
> So there number of mimeparts (M) related to the number of physmessages
> (P) is something like:
>
> M = A . P
> 2 <= A < inf
>
>
> --
>    ________________________________________________________________
>    Paul Stevens                                      paul at nfg.nl
>    NET FACILITIES GROUP                     GPG/PGP: 1024D/11F8CD31
>    The Netherlands________________________________http://www.nfg.nl
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev@...
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev