Re: Maildrop delivery issue

Hi Sam.

Am 09.07.26 um 13:34 schrieb Sam Varshavchik:
> Looking over the code I think I have a pretty good guess what's going 
> on. Those particular messages must have broken MIME formatting, spam 
> probably. They must be multipart MIME entities with junk after the 
> closing MIME boundry delimiter, and maildrop ignores the extra junk when 
> it figures out the filename.

Thank you for investigating!
Yes, the ones I looked up manually were all spam.


> What surprises me is that anything other than Courier code is reading 
> it, especially an IMAP server. It makes no sense, an IMAP server cannot 
> use this, even if it was correct.

I don't expect dovecot to dig that deep. Most likely it does just 
compare S= value to stat value before even opening the file...

I don't want to argue about Maildir++ format with the inventor but I'm a 
bit irritated. The specs say "append ,S=nnnnn to the name of the file, 
where nnnnn is the size of the file."
If there is garbage (in terms of MIME) at the end, then you can count 
(and write) it or not but it doesn't really make sense to write and not 
count it.

I just found out that dovecot has a compatibility setting to ignore the 
size from the file name. In the help text of the option 
maildir_broken_filename_sizes one can read that dovecot compares the 
*physical* size to the S= value. I'd understand that as byte length of 
the whole file.




_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users