On Tue, 7 Nov 2006, Sam Varshavchik wrote:
> Sunet Sysadmin writes:
>
>> Hi,
>> We have courier mail server with courier-filter. Modules running on
>> courier-filter are SA, Clamd(using unix socket), SPF. Every thing seems to
>> be working good. But all of a sudden i get these errors
>>
>> "Nov 8 08:59:51 jupiter submit: Transport endpoint is not connected
>> Nov 8 08:59:51 jupiter courieresmtpd:
>> error,relay=::ffff:130.94.123.232,from=<[EMAIL PROTECTED]>: 432
>> Mail filters temporarily unavailable.
>> Nov 8 08:59:54 jupiter courieresmtpd: started,ip=[::ffff:82.244.132.94]
>> Nov 8 08:59:55 jupiter submit: Transport endpoint is not connected
>> Nov 8 08:59:55 jupiter courieresmtpd:
>> error,relay=::ffff:195.98.170.130,from=<[EMAIL PROTECTED]>: 432
>> Mail filters temporarily unavailable.
>> Nov 8 08:59:55 jupiter courieresmtpd: started,ip=[::ffff:202.60.69.27]
>> "
>>
>> After i restart all the service courier, clamd ,spamassassin again starts
>> working. Can you help me with this or point me to right direction. Any
>> help is much appreciated.
>
> Whatever you're running for a mail filter, clamd or spamassassin, is
> crashing.
>
> Try asking for help on the clamd/spamassassin mailing lists. Courier can't do
> anything about this, except to refuse incoming mail when it happens, until
> it's fixed.
Ok, I've taken over this job from the guy who wrote the original
message. Anyway, the filter isn't crashing, but it is processing very slowly.
When the number of Unix domain sockets that are connected to it gets to 128,
the errors above appear. If there's some way to fix this, I'd love to hear
about it.
The filter in question is pureperlfilter, which is written by Julian
Mehnle, who has requested that support messages for that module also be
directed to this list.
Anyway, I have a question for Julian and others close to
Courier::Filter -- is there any chance that the multithreading support will be
entering alpha/beta testing sometime soon? Because it seems to me that the
CPU is not very heavily loaded (load average of 0.46), so it's presumably
blocking on IO or something. I'm hoping that by processing multiple threads
in parallel, we'll be able to get through things quicker.
If it helps, the SpamAssassin module is the one thats slowing
everything down. I tested this by removing it from the pureperlfilter config.
I'm still using Courier::Filter version 0.17, but after reading the
Changelog, I'm guessing this won't make a lot of difference.
Thanks all,
---------------------------------------------------------------------
| Name: Tim Nelson | Because the Creator is, |
| E-mail: [EMAIL PROTECTED] | I am |
---------------------------------------------------------------------
----BEGIN GEEK CODE BLOCK----
Version 3.12
GCS d+++ s+: a- C++$ U+++$ P+++$ L+++ E- W+ N+ w--- V-
PE(+) Y+>++ PGP->+++ R(+) !tv b++ DI++++ D G+ e++>++++ h! y-
-----END GEEK CODE BLOCK-----
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
