Parameter since is not working correctly

[dwydler]

Hello Sean,
I updated parsedmarc to version 8.16.0. Then added the parameter since to the parsedmarc.ini configuration file. The DMARC reports are retrieved from an email mailbox via IMAPS.

[general]
save_aggregate = True
save_forensic = True
save_smtp_tls = True
log_file = /var/log/parsedmarc/parsedmarc.log
silent = False
debug = True
delete = False

[mailbox]
reports_folder = INBOX
watch = True
test = True
check_timeout = 3600
#batch_size = 0
since = 1d

The email inbox contains emails/reports that are older than one day.

After starting parsedmarc, no emails are read at first. In the same second, 8 emails are recognized. This corresponds to the number of emails in the screenshot.

2024-12-01 10:21:27,247 - INFO - [cli.py:1205] - Starting parsedmarc
2024-12-01 10:21:27,642 - DEBUG - [__init__.py:1593] - Only days and weeks values in 'since' option are                          considered for IMAP conections. Examples: 2d or 1w
2024-12-01 10:21:27,657 - DEBUG - [__init__.py:1612] - Found 0 messages in INBOX
2024-12-01 10:21:27,657 - DEBUG - [__init__.py:1619] - Processing 0 messages
2024-12-01 10:21:27,670 - INFO - [cli.py:1588] - Watching for email - Quit with ctrl-c
2024-12-01 10:21:27,909 - DEBUG - [__init__.py:1612] - Found 8 messages in INBOX
2024-12-01 10:21:27,909 - DEBUG - [__init__.py:1619] - Processing 8 messages
2024-12-01 10:21:27,909 - DEBUG - [__init__.py:1623] - Processing message 1 of 8: UID 364
2024-12-01 10:21:27,925 - INFO - [__init__.py:1199] - Parsing mail from [email protected] on 2024-11-27 15:59:59-08:00
2024-12-01 10:21:28,081 - DEBUG - [utils.py:347] - Trying to fetch reverse DNS map from https://raw.githubusercontent.com/domainaware/parsedmarc/master/parsedmarc/resources/maps/base_reverse_dns_map.csv...
2024-12-01 10:21:28,122 - DEBUG - [utils.py:439] - IP address 2a01:111:f403:c20c::4 added to cache
2024-12-01 10:21:28,123 - DEBUG - [__init__.py:1623] - Processing message 2 of 8: UID 365
2024-12-01 10:21:28,141 - INFO - [__init__.py:1199] - Parsing mail from "DMARC Aggregate Report" <[email protected]> on 2024-11-28 11:48:43+00:00
2024-12-01 10:21:28,294 - DEBUG - [utils.py:439] - IP address 52.101.171.102 added to cache
2024-12-01 10:21:28,295 - DEBUG - [__init__.py:1623] - Processing message 3 of 8: UID 366
2024-12-01 10:21:28,303 - INFO - [__init__.py:1199] - Parsing mail from [email protected] on 2024-11-28 05:52:29-08:00
2024-12-01 10:21:28,460 - DEBUG - [utils.py:439] - IP address 52.101.171.125 added to cache
2024-12-01 10:21:28,461 - DEBUG - [__init__.py:1623] - Processing message 4 of 8: UID 367
2024-12-01 10:21:28,472 - INFO - [__init__.py:1199] - Parsing mail from "DMARC Aggregate Report" <[email protected]> on 2024-11-28 19:08:02+00:00
2024-12-01 10:21:28,564 - DEBUG - [utils.py:439] - IP address 52.101.169.86 added to cache
2024-12-01 10:21:28,678 - DEBUG - [utils.py:439] - IP address 52.101.171.91 added to cache
2024-12-01 10:21:28,678 - DEBUG - [__init__.py:1623] - Processing message 5 of 8: UID 368
2024-12-01 10:21:28,687 - INFO - [__init__.py:1199] - Parsing mail from "WEB.DE DMARC Reports" <[email protected]> on 2024-11-29 08:39:25+00:00
2024-12-01 10:21:28,838 - DEBUG - [utils.py:439] - IP address 52.101.171.128 added to cache
2024-12-01 10:21:28,959 - DEBUG - [utils.py:439] - IP address 52.101.171.103 added to cache
2024-12-01 10:21:29,053 - DEBUG - [utils.py:439] - IP address 40.107.149.122 added to cache
2024-12-01 10:21:29,130 - DEBUG - [utils.py:439] - IP address 52.101.169.135 added to cache
2024-12-01 10:21:29,130 - DEBUG - [__init__.py:1623] - Processing message 6 of 8: UID 369
2024-12-01 10:21:29,140 - INFO - [__init__.py:1199] - Parsing mail from GMX DMARC Report <[email protected]> on 2024-11-29 08:39:25+00:00
2024-12-01 10:21:29,302 - DEBUG - [utils.py:439] - IP address 52.101.169.117 added to cache
2024-12-01 10:21:29,397 - DEBUG - [utils.py:439] - IP address 52.101.171.92 added to cache
2024-12-01 10:21:29,478 - DEBUG - [utils.py:439] - IP address 52.101.171.98 added to cache
2024-12-01 10:21:29,478 - DEBUG - [__init__.py:1623] - Processing message 7 of 8: UID 370
2024-12-01 10:21:29,487 - INFO - [__init__.py:1199] - Parsing mail from [email protected] on 2024-11-28 15:59:59-08:00
2024-12-01 10:21:29,707 - DEBUG - [utils.py:439] - IP address 2a01:111:f403:c20b::1 added to cache
2024-12-01 10:21:29,707 - DEBUG - [utils.py:406] - IP address 2a01:111:f403:c20c::4 was found in cache
2024-12-01 10:21:29,707 - DEBUG - [__init__.py:1623] - Processing message 8 of 8: UID 371
2024-12-01 10:21:29,724 - INFO - [__init__.py:1199] - Parsing mail from "DMARC Aggregate Report" <[email protected]> on 2024-11-29 11:50:25+00:00
2024-12-01 10:21:29,878 - DEBUG - [utils.py:439] - IP address 52.101.169.85 added to cache
2024-12-01 10:21:29,956 - DEBUG - [utils.py:439] - IP address 52.101.169.102 added to cache
2024-12-01 10:21:30,072 - DEBUG - [utils.py:439] - IP address 52.101.169.141 added to cache
2024-12-01 10:21:30,090 - INFO - [elastic.py:390] - Saving aggregate report to Elasticsearch
2024-12-01 10:21:30,361 - WARNING - [cli.py:131] - An aggregate report ID 18421885466395362117 from google.com about domain.com with a date range of 2024-11-27 00:00:00Z UTC to 2024-11-27 23:59:59Z UTC already exists in Elasticsearch
2024-12-01 10:21:30,362 - INFO - [elastic.py:390] - Saving aggregate report to Elasticsearch
2024-12-01 10:21:30,577 - WARNING - [cli.py:131] - An aggregate report ID 658916cf8ad1400e8c4e0754ca7ec58c from outlook.com about domain.com with a date range of 2024-11-26 00:00:00Z UTC to 2024-11-27 00:00:00Z UTC already exists in Elasticsearch
2024-12-01 10:21:30,577 - INFO - [elastic.py:390] - Saving aggregate report to Elasticsearch
2024-12-01 10:21:30,707 - WARNING - [cli.py:131] - An aggregate report ID 1732760607.797066 from Yahoo about domain.com with a date range of 2024-11-27 00:00:00Z UTC to 2024-11-27 23:59:59Z UTC already exists in Elasticsearch
2024-12-01 10:21:30,707 - INFO - [elastic.py:390] - Saving aggregate report to Elasticsearch
2024-12-01 10:21:30,871 - WARNING - [cli.py:131] - An aggregate report ID 3ed23bcc77f54051ba2807291fb21c07 from Enterprise Outlook about domain.com with a date range of 2024-11-26 00:00:00Z UTC to 2024-11-27 00:00:00Z UTC already exists in Elasticsearch
2024-12-01 10:21:30,872 - INFO - [elastic.py:390] - Saving aggregate report to Elasticsearch
2024-12-01 10:21:31,007 - WARNING - [cli.py:131] - An aggregate report ID ac7aec204d1d4654acbb9bb43201c343 from web.de about domain.com with a date range of 2024-11-28 00:00:00Z UTC to 2024-11-28 23:59:59Z UTC already exists in Elasticsearch
2024-12-01 10:21:31,008 - INFO - [elastic.py:390] - Saving aggregate report to Elasticsearch
2024-12-01 10:21:31,144 - WARNING - [cli.py:131] - An aggregate report ID 8eaf27ee175c445aac56d1b065e716ab from GMX about domain.com with a date range of 2024-11-28 00:00:00Z UTC to 2024-11-28 23:59:59Z UTC already exists in Elasticsearch
2024-12-01 10:21:31,145 - INFO - [elastic.py:390] - Saving aggregate report to Elasticsearch
2024-12-01 10:21:31,271 - WARNING - [cli.py:131] - An aggregate report ID 9370460849411531310 from google.com about domain.com with a date range of 2024-11-28 00:00:00Z UTC to 2024-11-28 23:59:59Z UTC already exists in Elasticsearch
2024-12-01 10:21:31,271 - INFO - [elastic.py:390] - Saving aggregate report to Elasticsearch
2024-12-01 10:21:31,430 - WARNING - [cli.py:131] - An aggregate report ID d61eeb7038384004b14b1679dd02c760 from outlook.com about domain.com with a date range of 2024-11-27 00:00:00Z UTC to 2024-11-28 00:00:00Z UTC already exists in Elasticsearch
2024-12-01 10:28:07,463 - WARNING - [imap.py:88] - IMAP connection error. IMAPClient.idle() takes 1 positional argument but 2 were given. Reconnecting...

Am I doing something wrong with the configuration or is this a bug?