I think that's totally the issue- I can see some really old messages
(1996) which very malformed date fields. Am checking on my versions of
software now- I'm a little limited on this end since I'm using a virtual
box on bluehost.com, and while I have root access, there are some aspects
On 12/29/2017 09:51 AM, Mark Sapiro wrote:
>
> It looks like we have a bug somewhere. There may be a defective message
> in the .mbox, but even so, it should result in a more graceful error report.
>
> Did you get a traceback with the "unexpected keyword argument"
> exception. I would like to
On 12/28/2017 11:14 AM, Andrew White, PhD wrote:
>I checked for that- it looks like my problem solving was incomplete. I
>found an error message when running arch where it was sticking on a bad
>record - I kept getting "got an unexpected keyword argument 'flags' "
>(even after
I checked for that- it looks like my problem solving was incomplete. I
found an error message when running arch where it was sticking on a bad
record - I kept getting "got an unexpected keyword argument 'flags' "
(even after using cleanarch on the mbox file), and I think that was the
Jordan Brown writes:
> per se. I don't want to turn on any domain-global rejection of
> "failing" mail, because I wouldn't want to reject messages sent to the
> non-mailing-list addresses.
You should think twice about that. The reason why AOL and Yahoo! have
turned on the reject policy is
