yes

On 9/1/2020 1:39 AM, David Bray wrote:
Hey cool thanks for the dir listing
is the permissions critical here, noting that https://raw.githubusercontent.com/qmtoaster/dspam/master/dspamdb.sh
leaves the ownership as root.root and perms 644

David Bray
0418 745334
2 ∞ & <


On Mon, 31 Aug 2020 at 23:29, Eric Broch <ebr...@whitehorsetc.com <mailto:ebr...@whitehorsetc.com>> wrote:

    Here's my domain level directory. There are no .qmail-user files
    only .qmail-default :

    # ls -la /home/vpopmail/domains/mydomain.tld/
    total 24
    drwx------ 11 vpopmail vchkpw 4096 Oct 31  2019 .
    drwx------  8 vpopmail vchkpw 4096 Apr  6  2019 ..
    drwx------  3 vpopmail vchkpw  143 Dec 28  2016 user1
    drwx------  3 vpopmail vchkpw  143 Dec 28  2016 user2
    drwx------  4 vpopmail vchkpw 4096 Aug 16 13:39 user2
    drwx------  3 vpopmail vchkpw  143 Dec 28  2016 user4
    drwx------  3 vpopmail vchkpw  143 Dec 28  2016 user5
    drwx------  3 vpopmail vchkpw 4096 Apr  8  2019 postmaster
    -rw-------  1 vpopmail vchkpw   56 Sep 14  2017 .qmail-default

    Eric


    On 8/31/2020 7:23 AM, Eric Broch wrote:

    In the PER USER configuration the
    '/home/vpopmail/domains/mydomain.tld/.qmail-default' file doesn't
    change and remains:

    | /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox



    On 8/31/2020 7:20 AM, Eric Broch wrote:

    So, here's what the directory directory looks like:

    # ls -la /home/vpopmail/domains/mydomain.tld/user
    total 52
    drwx------   4 vpopmail vchkpw  4096 Aug 16 13:39 .
    drwx------  11 vpopmail vchkpw  4096 Oct 31  2019 ..
    drwx------ 357 vpopmail vchkpw 12288 Aug 31 07:10 Maildir
    -rw-------   1 vpopmail vchkpw    21 Dec 28  2016 .mailfilter.dspam
    -rw-------   1 vpopmail vchkpw    42 Aug 16 13:38 .qmail


    .qmail file (one line no quotes):  "| preline /usr/bin/maildrop
    ./.mailfilter.dspam"


    .mailfilter.dspam (here)  
<https://github.com/qmtoaster/dspam/blob/master/.mailfilter.dspam>.


    Eric



    On 8/31/2020 7:09 AM, Eric Broch wrote:

    When I do per user the file .qmail file resides in that
    person's home email directory
    '/home/vpopmail/domains/mydomain.tld/user' (in the same
    directory as Maildir).

    This .qmail file contains the following:

    | preline /usr/bin/maildrop ./.mailfilter.dspam

    .mailfilter.dspamhere  
<https://github.com/qmtoaster/dspam/blob/master/.mailfilter.dspam>.


    It does NOT duplicate email.


    On 8/30/2020 10:33 PM, Remo Mattei wrote:
    I have a little diff variant from Eric,
    If I do the top level like Eric I do have the same config, if
    I do per user I have the following in the .qmail-user

    |/usr/bin/dspam  --deliver=innocent --user $EXT@$USER --debug
    --mode=teft --feature=noise,whitelist --stdout -p -m |
    /home/vpopmail/bin/vdelivermail ''
    /home/vpopmail/domains/domain.ht/user <http://domain.ht/user>

    Keep in mind if you do use RC, this becomes tricky since the
    .qmail-user will become .qmail inside of the user home dir and
    this will make duplicates (emails).

    Just my 2 cents. Overall, it’s pretty similar to what Eric has.

    Remo

    On Aug 30, 2020, at 6:40 PM, David Bray
    <da...@brayworth.com.au <mailto:da...@brayworth.com.au>> wrote:

    Thanks
    My understanding of the beast just increased

    Cheers

    David Bray
    0418 745334
    2 ∞ & <


    On Mon, 31 Aug 2020 at 11:29, Eric Broch
    <ebr...@whitehorsetc.com <mailto:ebr...@whitehorsetc.com>> wrote:

        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/  
<http://brayworth.com/%5Buser%5D/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
        <ebr...@whitehorsetc.com
        <mailto:ebr...@whitehorsetc.com>> 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, <r...@mattei.org
            <mailto:r...@mattei.org>> 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 <an...@pobox.com
                <mailto:an...@pobox.com>> 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:
                qmailtoaster-list-unsubscr...@qmailtoaster.com
                <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com>
                > For additional commands, e-mail:
                qmailtoaster-list-h...@qmailtoaster.com
                <mailto:qmailtoaster-list-h...@qmailtoaster.com>
                >
                
---------------------------------------------------------------------
                To unsubscribe, e-mail:
                qmailtoaster-list-unsubscr...@qmailtoaster.com
                <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com>
                For additional commands, e-mail:
                qmailtoaster-list-h...@qmailtoaster.com
                <mailto:qmailtoaster-list-h...@qmailtoaster.com>


Reply via email to