Re: Maildrop delivery issue

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--===============3755670560127623156==
Content-Type: multipart/signed;
    boundary="=_ripper.email-scan.com-397952-1783596867-0001";
    micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 8bit

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--=_ripper.email-scan.com-397952-1783596867-0001
Content-Type: text/plain; format=flowed; delsp=yes; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Bernd Wurst writes:

> Hallo.
>
> We experience errors when maildrop delivers mail to our mailboxes since a  
> few days ago.
>
> It's affecting multiple users, all using maildrop for delivery. All users  
> not using maildrop are not affected. We upgraded to courier-2.0.2 last week,  
> so it's most likely correlating with this.
>
> The result is that message files inside Maildir++ have the wrong size in  
> their filename and so the whole maildir gets blocked by Dovecot IMAP Server.
>
> # ls -l /home/user/maildir/cur/1783557589.[...]\,S\=217586\:2\,
> -rw------- 1 user users 217633  9. Jul 02:39 '/home/user/maildir/cur/ 
> 1783557589.[...]\,S\=217586\:2\,'
>
> Did you do any change on maildrop that could lead to this behaviour?
>
> It's not happening with every message but about once or twice a day per user.

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.

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'll confirm my theory, and fix this.


--=_ripper.email-scan.com-397952-1783596867-0001
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQRupkKLJP96aW75pIOKYPgoojZS4gUCak+HQwAKCRCKYPgoojZS
4jq8AQDGmbo4XIHthlAupYzyj9PnsMbb0nQNQcgidAk3xRPXMgEA82Vmq92XvvSg
PkF/NJn2Ey1BFgRaGG4FTZUsBmy2Lwo=
=iQP6
-----END PGP SIGNATURE-----

--=_ripper.email-scan.com-397952-1783596867-0001--


--===============3755670560127623156==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============3755670560127623156==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============3755670560127623156==--