Posts by joximu

    Aber es läuft ein Prozess von spamassassin?

    1. # ps ax | grep spam
    2. ... /usr/sbin/spamass-milter -P /var/run/spamass/ -f -p /var/spool/postfix/spamass/spamass.sock -e -f -I -u spamass-milter
    3. ... /usr/bin/perl -T -w /usr/sbin/spamd --max-children=5 --sql-config --nouser-config --username=debian-spamd --port=783 --helper-home-dir=/var/lib/spamassassin -d --pidfile=/var/run/
    4. ... spamd child
    5. ... spamd child

    Gruss J

    Hi Nuxwin

    I started with 1.5.3-20181208 and copied debian-stretch.xml in autoinstaller/packages to devuan-ascii.xml and had a good start.

    Somewhere during installing/configuring the ftp server it hang...

    Ah - a second try went to the end... I got the "last steps" to run manually... lets see if it works.




    I tried the three 1.5.* branches to install on Devuan ascii... but no success... (either "not supported yet" or the setup died...)

    Is the recommended way "install devuan jessie" and the "upgrade to ascii"?



    I'd comment out the database migration - as you stated this may be very complicated and should not keep the feature unfinished.

    Moving the alias with all web-data and mail accounts is not to difficult in i-MSCP but manually a big deal - moving the database can be done manually...

    The first (Dom-Alias to new account) is more important - but also the second one can be interesting...

    Otherwise there is the manual way...

    Maybe it's too hard to move also the databases... they are not connected to a certain subdomain/alias or whatever. And the db prefix changes when moving to another (a news) client account.... this is to complex to have it done automatically.


    postgrey prevents postfix from accepting a mail "on the first try" (reject with "temporary error"). If the mail is sent a second time, it's accepted. There are only problems if the sending server is always a different one.

    spamassassin on the other hand has a look at the mail which was accepted and is being delivered to the mailbox - it writes the spam points in the mail header (and maybe adds the original mail to a spam report) but the mail is delivered to the inbox. If the user has some filter rules which moves the "***SPAM***" Mails to another folder... then it should be there.

    So - theese two components do not definitively reject mails. It's possible that the mail cannot be accepted because every time the mail arrives, it comes from a different server -> should be go back to sender after 4 or 5 days.

    If the mail has been accepted then it's somewhere in the maildir of the customer.

    More infos might be available when having a look in the mail.log - but one should know when/from where etc theese "certain mails" are....

    Hope this helps