Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Stop rejection due to bad dates (Jeffery Small)
2. ovsqlite (Bo Lindbergh)
----------------------------------------------------------------------
Message: 1
Date: Wed, 16 Dec 2020 10:23:55 -0800
From: Jeffery Small <[email protected]>
To: Mailing Lists <[email protected]>
Subject: Stop rejection due to bad dates
Message-ID:
<caolermw5p65hqkbl0pflk0j5b5p1bnmntmjvswt+njt_eji...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I use the news system to post email received from various mailing lists.
I also post spam to a special group using a rule in my mailagent(1)
processing file. I am getting a lot of spam, apparently with badly
formed date headers which the news system sees as being in the
future. In my mailagent logs I typically see these entries:
MATCH on rule #13 in mode INITIAL
WARNING Date field is 5h18m23s in the future
ERROR could not post to local.delete
NOTICE not saved, leaving in mailbox
Now, I'm assuming that it is the bad date causing the rejection.
Before I go to the trouble of writing yet another filter to check
and repair the date line of every potential post, Is there a simple
rule I can use for inn2 to instruct it to simply ignore these types of
errors and go ahead and post anyway?
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/inn-workers/attachments/20201216/4442434b/attachment-0001.htm>
------------------------------
Message: 2
Date: Thu, 17 Dec 2020 02:02:56 +0100
From: Bo Lindbergh <[email protected]>
To: [email protected]
Subject: ovsqlite
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
At long last, ovsqlite! In two patches to be applied in sequence
on top of svn revision 10453.
1. https://www.stacken.kth.se/~blgl/inn-xbuildconfig.diff.gz
The first patch is split out because it has general utility,
not specific to ovsqlite.
I use some generated files, so I wanted to enhance storage/buildconfig
to add lists of files to be removed at various cleanup levels.
METHOD_SOURCES, EXTRA_SOURCES, and PROGRAMS were handled by separate
code paths that were identical except for the names. This cried out
to be replaced by a table-driven approach, so that's what I did.
The Makefile-related data could end up in either %storage or %overview,
and so had to be merged and re-sorted before Make.methods could be written.
I changed this to use a new %makefile variable containing
the Makefile-related data for both storage and overview methods.
2. https://www.stacken.kth.se/~blgl/inn-ovsqlite.diff.gz
I use a single compile-link-and-run test to probe for a sufficient
version of SQLite. Feel free to refine this if you have more patience
with autoconf than I.
scripts/rc.news is rewritten to use 'case "$OVMETHOD" in ...' for startup
and shutdown handling. In an ideal world, this too should be generated
by storage/buildconfig (ovmethod.rc or something).
In addition to the man pages, hacking/internals info can be found here:
* storage/ovsqlite/ovsqlite-private.h
* storage/ovsqlite/sql-init.sql
* storage/ovsqlite/sqlite-helper-gen.in
More testing is needed; I've only used the hardware I've got at home,
which is all x86_64 (macOS 10.15 and Fedora 33).
Don't hesitate to complain if any part of the documentation is too terse.
/Bo Lindbergh
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 126, Issue 8
*******************************************
