New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dbmail-imapd fetch'ing header fields returns empty results #265
Comments
Thanks for finding this bug, it's an off by one error. |
I can't replicate that on my installation.
|
Could you try it with a uid |
Refactor _fetch_headers to fix #265
Hopefully this fixes your issue |
Sorry, it doesn't seem to work. I cloned your repo, stopped the service, then This first fetch also didn´t work before your update
|
Do you have those headers in the dbmail_headername table? Can you show a detailed log My successful log follows, it show the IDs from the dbmail_headername table Mar 19 13:24:01 test.p-o.co.uk dbmail-imapd[42577]: [0x7416250] Debug:[imap] _fetch_headers(+731): [0x7417fa0] init bodyfetch->headers ) |
The
I assume no need for a log then. |
Ah, if you set header_cache_readonly = no then deliver a few emails they will populate that table, then set it to yes to stop the table filling up. I've got a task for tomorrow to automatically pre-populate that table. |
I have populated the populate_dbmail_headername.tar.gz Unfortunately nothing changed, I still can't fetch fields. |
They need to be lower case :( |
Thank you. Lowercase certainly solved that part of the problem. The problem that remains is this:
On the first fetch, I would have expected reply |
There are no comma separators |
Thank you once again. It works. I noticed response order does not match fetch request order. I don´t know what the RFC says, perhaps it's OK.
|
I can't find anything about order of returned items |
Hi
It seems I can't fetch any existing individual header fields e.g.
This also doesn't work
Whereas these all returns the expected results
DBMail 3.4.1 as systemd service on ubuntu 22.04.1 with PostgreSQL 14.11. Connecting via telnet on port 143
The text was updated successfully, but these errors were encountered: