Re: "Content/Error_report_too_long, _sorry."

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.

--===============4986779617019463256==
Content-Type: multipart/signed;
    boundary="=_ripper.email-scan.com-150510-1729339466-0001";
    micalg=pgp-sha1; protocol="application/pgp-signature"

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-150510-1729339466-0001
Content-Type: text/plain; format=flowed; delsp=yes; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Philip Rhoades via Courier-maildrop writes:

>> If everything is set up correctly you only need a
>>
>> | maildrop
>>
>> This actually runs maildrop in proper delivery mode, reading  
>> $HOME/.mailfilter, and completely ignoring the VERBOSE setting.
>
>
> Ok, now I am only getting this:
>
>   deferral: ezmlm-weed:_fatal:_out_of_memory/
>
> which I think I have asked about before but I don't remember getting a  
> response to . .

I am not familiar with that. I don't see why maildrop's invocation would be  
a factor there.

> Anyway, would it be possible to generate separate delivery messages for each  
> email to a nominated directory? - then each log file could be as long as  
> necessary for debugging purposes and I can just remove them as necessary  
> based on their time-stamps . . possible?

maildrop writes log message to standard error, so it's up to you to handle  
it however you wish. If you want to redirect standard error somewhere else,  
you could even get fancy and find something that will write its input to a  
dated filename, and then use logrotate, or something, to purge old log files.


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

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

iHUEABYKAB0WIQRupkKLJP96aW75pIOKYPgoojZS4gUCZxOgSgAKCRCKYPgoojZS
4spoAPwK6NcZMJLj9VCboJLZSh4PJR6V6NRIfeyEJxRilD2A9wD/UH65kebXN20X
E3TaGUD7LJcRnJLlla8JLcG2DErxBQg=
=/AZh
-----END PGP SIGNATURE-----

--=_ripper.email-scan.com-150510-1729339466-0001--


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


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

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

--===============4986779617019463256==--