Re: [courier-users] courier-analog and pop3

Mon, 29 Nov 2004 19:29:44 -0800 

On Wednesday 24 November 2004 19:54, Sam Varshavchik wrote:
> Mark Bucciarelli writes:
> > I have log files that track a number of pop3 logins and retrievals,
> > but courier-analog reports no pop3 activity.

> POP3 reporting works for me.

Yeah, it works here too.  But I have to change line 1214 of the script 
from:

if (/^(...............)[^:]*(imapd|pop3d)(-ssl)?[\[\]\d]*:\s*(.*)/)

to:

if (/^(...............)[^:]*(imapd|pop3login)(-ssl)?[\[\]\d]*:\s*(.*)/)


I'm running courier-pop version 0.45.6.20040712-0 (www.backports.org) and 
courier-analog-0.12.20041107 (Sourceforge CVS).

Do you have any interest in an option for SpamAssassin stats?  I want one 
and plan to write one.

Also, I ran the index.html produced by courier-analog through the w3 
validator.  The result is attached (invalid HTML 4.01 transitional, 10 
errors).

Regards,

Mark
Title: Validation Results
Jump To:
File: index.html
Encoding: utf-8
Doctype: HTML 4.01 Transitional
Errors: 10

No Character Encoding Found! Falling back to UTF-8.

I was not able to extract a character encoding labeling from any of the valid sources for such information. Without encoding information it is impossible to reliably validate the document. I'm falling back to the "UTF-8" encoding and will attempt to perform the validation, but this is likely to fail for all non-trivial documents.

So what should I do? Tell me more...

No DOCTYPE Found! Falling Back to HTML 4.01 Transitional

A DOCTYPE Declaration is mandatory for most current markup languages and without one it is impossible to reliably validate this document. I am falling back to "HTML 4.01 Transitional" and will attempt to validate the document anyway, but this is very likely to produce spurious error messages for most non-trivial documents.

So what should I do? Tell me more...

DOCTYPE Fallback in effect!

The DOCTYPE Declaration in your document was not recognized. This probably means that the Formal Public Identifier contains a spelling error, or that the Declaration is not using correct syntax. Validation has been performed using a default "fallback" Document Type Definition that closely resembles HTML 4.01 Transitional, but the document will not be Valid until you have corrected the problem with the DOCTYPE Declaration.

This page is not Valid HTML 4.01 Transitional!

Below are the results of attempting to parse this document with an SGML parser.

  1. Line 1, column 0: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"

    <html><head><title>Courier Usage Report</title></head><frameset rows='24,*' bord

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with the HTML 4.01 Transitional DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

    ✉

  2. Line 1, column 69: there is no attribute "ROWS"

    ... Report</title></head><frameset rows='24,*' border='0'><frame src=''24,*' border='0'><frame src='' name='main'

    ✉

  3. Line 1, column 86: element "FRAMESET" undefined

    ...head><frameset rows='24,*' border='0'><frame src='' name='main' sc

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).

    ✉

  4. Line 1, column 98: there is no attribute "SRC"

    ...et rows='24,*' border='0'><frame src="" title="Position where error was detected.">'header.html' name='main' scrollin='no'>

    ✉

  5. Line 1, column 117: there is no attribute "NAME"

    ...er='0'><frame src='' name='main' scrollin='no'><frame name='body'

    ✉

  6. Line 1, column 133: there is no attribute "SCROLLIN"

    ...c='header.html' name='main' scrollin='no'><frame name='body' scrollin='no'><n

    ✉

  7. Line 1, column 137: element "FRAME" undefined

    ...eader.html' name='main' scrollin='no'><frame name='body' scrollin='no'><nofra

    ✉

  8. Line 1, column 170: element "FRAME" undefined

    ...'no'><frame name='body' scrollin='no'><noframes><a href=''>Enter w

    ✉

  9. Line 1, column 262: end tag for "HTML" which is not finished

    ...pport</a></noframes></frameset></html>

    Most likely, You nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element (e.g. 'ul') which requires a child element (e.g. 'li') that you did not include. Hence the parent element is "not finished", not complete.

    ✉

Valid XHTML 1.0! Feedback: The W3C Validator Team
Date: 2004/07/21 10:24:06

Copyright © 1994-2004 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.

Reply via email to