Looks like you were right about this one.
I would if possible, prefer to set this up as a TCP/IP socket for reasons
of testability.
However, I tried this last night and found that it wasn't returning any
email.
This is on a localhost proxy server, so technically there is no such
thing as a LMTP since there is no local MDA/MTA available (other than
postfix).
If I read the docs right I have to set this up as:
postfix --> dspam [LMTP]
ServerPort 10027
ServerMode standard
ServerQueueSize 32 (what is this?)
ServerParameters "--deliver=innocent"
ServerDomain localhost.localdomain (or other)
and master.cf with
-o content_fitler=dspam:127.0.0.1:10027
dspam ...... ..... lmtp
-o something there but I can't remember right now...
dspam --> postfix [SMTP]
DeliveryHost 127.0.0.1
DeliveryPort 10028
DeliveryIdent localhost
DeliveryProto SMTP
and master.cf with
127.0.0.1:10028 .... ..... smtp
-o and something here too but I can't rembember right now...
I think this is almost right but I have yet to test it.
I'm also missing some of the details on the email messages for firstrun,
quarantine full and the like. Where do they live and are there examples
in the docs that I should just go find and stop bothering everyone?
And lastly, I forgot to write down the following:
I found there was some kind of conflict between the database storing user
configuration settings (Whitelisting, TOE/TEFT...) and the user
configurations on local files. I don't want them to have access to
anything locally. Is there something obvious to do?
And there was a problem previously with user accounts being created for
every alias (answer is probably postfix setting to defer rewrite which
is common in their configurating examples for content_filters) but also
for non-deliverable addresses. I think again this might be a postfix
configuration issue that i'll look into.
Thaks for your help!
On 1/16/2007, "Michael Alger" <[EMAIL PROTECTED]> wrote:
>On Mon, Jan 15, 2007 at 11:45:07AM -0500, Tom Allison wrote:
>
>> Let me start with the error:
>>
>> status=deferred (connect to mydomainnamehere.com[/tmp/dspam.sock]: No
>> such file or directory)
>>
>> And then go to my configuration for postfix:
>>
>> 127.0.0.1:10021 inet n - n - 5 smtpd
>> -o content_filter=lmtp:unix:/tmp/dspam.sock
>>
>> And lastly the configuration for dspam.
>>
>> ServerDomainSocketPath "/tmp/dspam.sock"
>
>Many distributions set up postfix's smtpd listeners in a chroot
>environment, in which case the root ("/") directory for the smtpd is
>probably something like /var/spool/postfix.
>
>Solution is either to move the dspam socket to a location under the
>smtpd's chroot path, or to make smtpd not run chrooted (which has
>security implications, of course).
>
>Your master.cf should have comments telling you which column
>indicates that the process should run chrooted; I think it's the 4th
>(the first - in yours, which means to use the default, which is
>usually chrooted).
