Pantek Library
Hosting Provided By
CybrHost
High Speed Hosting

Re: Occasional spamassassin: Connection refused

From: mouss <mouss(at)netoyen.net>
Date: Wed Aug 29 2007 - 18:11:56 EDT


Simon wrote:

> On 8/29/07, Mark Martinec  wrote:
>   

>> Simon,
>>
>>
>>> connect to transport spamassassin: Connection refused
>>>
>> You do not have a transport named 'spamassassin' in Postfix master.cf file.
>>
>> The name of a transport comes from a content_filter setting, a FILTER
>> action in an access map or header/body checks, or a transport map entry.
>> The name of a transport is then stored with a message when enqueued by
>> Postfix, so even if you previously used a transport 'spamassassin' in
>> your settings but you no longer do so, it is possible that it is still
>> referenced from some messages waiting in your mail queue.
>>
>> Depending on your intention:
>> - create a transport named 'spamassassin' in Postfix master.cf;
>> - or, remove all references to nonexisting transport from config files;
>> - if there are messages still in a queue referencing this nonexistant
>> transport, you may requeue them (postsuper -r ...) or perhaps just
>> delete them (postsuper -d ...).
>>
>
> Thanks for the reply mark... Ive checked thru all the files in
> /etc/postfix and /etc/postfix2 (2nd instance) and there is no
> transport marked 'spamassassin', all our transport config is mysql
> based, but there is nothing in there either. Strange?
>   

mysql is not a mail transport. you have something (maybe in your mysql tables) that returns 'spamassassin' as a transport, but this is not defined as a transport.

anyway, this is off topic here. followups on the postfix list. but there, provide output of 'postconf -n'. Received on Wed Aug 29 18:12:11 2007

This archive was generated by hypermail 2.1.8 : Fri Oct 26 2007 - 03:18:00 EDT


Contact Us  Legal Notices  Order Services Online 
Pantek Home  Privacy Policy  IT news  Site Map  Pantek Library