This is the contents of the .qmail-default (domain level) file that's
existed since the beginning and never changed (directory:
/home/vpopmail/domains/mydomain) :
| /usr/bin/dspam --user "$EXT@$HOST" --deliver=stdout |
/home/vpopmail/bin/vdelivermail '' bounce-no-mailbox
The .qmail file if one decides to run dspam by user (not domain) is as follows
(/home/vpopmail/domains/mydomain/myuser) :
| preline /usr/bin/maildrop ./.mailfilter.dspam
.mailfilter.dspamhere
<https://github.com/qmtoaster/dspam/blob/master/.mailfilter.dspam>.
The lines provided in the previous email do not call dspam at all (below):
<quote>
it creates the .qmail as a result
|/var/qmail/bin/preline /usr/bin/maildrop -A 'Content-Filter: maildrop-toaster'
/etc/mail/mailfilter
if you then edit the account via the admin panel that file becomes:
|/var/qmail/bin/preline /usr/bin/maildrop -A 'Content-Filter: maildrop-toaster'
/etc/mail/mailfilter
/home/vpopmail/domains/brayworth.com/[user]/Maildir/
</quote>
Eric
On 8/30/2020 7:06 PM, David Bray wrote:
Ok - working backwards from memory here
and when I read the install script I can see that the .qmail file is
not created
so (and this is getting off topic now)
* there should only be a .qmail-default and not a .qmail
* and
it's likely that these came from an older install
o so they should be removed ..
David Bray
0418 745334
2 ∞ & <
On Mon, 31 Aug 2020 at 09:53, Eric Broch <[email protected]
<mailto:[email protected]>> wrote:
Hmmm...
I never had double delivery and mine's been installed for 5 years
or more.
The install script installs only one dot qmail file
(.qmail-default), and only after a query to implement at domain level.
You have the option to run dspam at domain or user level.
Please show me where in the install procedure a .qmail file is
created with the following line:
|/var/qmail/bin/preline /usr/bin/maildrop -A 'Content-Filter:
maildrop-toaster' /etc/mail/mailfilter
?
The install script is for CentOS 5/6/7. I've yet to upgrade it for 8.
I would recommend Dspam; however, it needs some attention.
Eric
On 8/30/2020 4:31 PM, David Bray wrote:
I wondered this exact question and was going to ask this question
I've wondered how it actually works
I've disabled it
if it works as documented at:
* https://raw.githubusercontent.com/qmtoaster/dspam/
it creates the .qmail as a result
|/var/qmail/bin/preline /usr/bin/maildrop -A 'Content-Filter:
maildrop-toaster' /etc/mail/mailfilter
if you then edit the account via the admin panel that file becomes:
|/var/qmail/bin/preline /usr/bin/maildrop -A 'Content-Filter:
maildrop-toaster' /etc/mail/mailfilter
/home/vpopmail/domains/brayworth.com/[user]/Maildir/
<http://brayworth.com/%5Buser%5D/Maildir/>
which results in a double up of delivery ...
if you remove the file, the problem goes away
so at best it needs to be carefully monitored, but it is still
effective
but the newer scripted install does a pretty good job with
spamassassin anyway ... so I've disabled it..
David Bray
0418 745334
2 ∞ & <
On Mon, 31 Aug 2020 at 07:10, <[email protected]
<mailto:[email protected]>> wrote:
I have used dspam from the early days so you could put this
as an option on your playbook.
Just my 2cents
> Il giorno 30 ago 2020, alle ore 13:43, Angus McIntyre
<[email protected] <mailto:[email protected]>> ha scritto:
>
> I'm (still!) working on my Ansible role for installing
qmailtoaster, but I've switched to CentOS 8, based on Eric's
new script, and it seems much more straightforward and robust.
>
> One question I have is whether I should try to support
dspam or not. It looks as if the project was abandoned in
2014, amid reports that dspam never performed as well as the
developer claimed.
>
> Anyone have any thoughts or feelings (or, better, solid
data) on whether it's worth including dspam in a qmailtoaster
install?
>
> Angus
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
[email protected]
<mailto:[email protected]>
> For additional commands, e-mail:
[email protected]
<mailto:[email protected]>
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
[email protected]
<mailto:[email protected]>
For additional commands, e-mail:
[email protected]
<mailto:[email protected]>
