Posts by sport80

    Sure, i've used exactly your template


    The roundcube plugin with your implementation add this in /var/mail/virtual/somedomain/someuser


    dovecot.sieve -> sieve/managesieve.sieve
    sieve/


    But have you try if you don't use roundcube but only IMAP or POP3?


    This file/folder are not created and sieve does not have any rule to delivery the spam to INBOX.Junk folder, so, the email are delivered in INBOX with the spam definition directly

    Hi,


    yes, i confirm, the sieverules are already implemented in i-MSCP through Roundcube managesieve plugins, but the spam to junk function is not enabled by default if the user does not make a login in RoundCube. The result is that the spam email are delivered in INBOX folder and not in INBOX.Junk. With my mod all the users have the spam to junk by default. See a description in 90-sieve.conf file


    Hi,


    there are some useful functions that can be implemented in i-MSCP directly


    Spam To Junk


    The i-MSCP panel already have a spam to junk implementation, but it works only if the user at the first time make a login through webmail and save the custom settings in RoundCube. To make working a default spam-to-junk filter to the users that does not make a login in webmail, here is the solution.


    1) edit the /etc/dovecot/dovecot.conf file and add the following lines:



    exit and save



    2) Create the default sieve dir, create a default sieve rule in and own it to the mail user


    mkdir /var/lib/dovecot/sieve
    nano /var/lib/dovecot/sieve/default.sieve



    chown -R vmail:mail /var/lib/dovecot/sieve



    3) reload/restart dovecot service


    service dovecot restart



    Source: https://rtcamp.com/tutorials/mail/server/sieve-filtering/



    Imap IDLE


    The Imap IDLE function is very useful to increase the battery life of mobile device. Many Imap clients, like K9 mail, implement a push-to-mail function in Imap that use the Idle function of Imap server. The default idle time in dovecot is set to 2 minutes, increasing this time to 29 minutes, as the rfc2177 say, many mobile device can improve the battery life


    edit the /etc/dovecot/dovecot.conf file and add the following line:



    reload/restart dovecot service


    service dovecot restart



    Source: https://peterkieser.com/2011/0…e-and-dovecots-push-imap/



    Expunge Junk Folder


    This function can delete the oldest spam email received and optimize the space assigned to the mail account (edit 12/11/2014: modified cronjob and search query in DB)


    1) edit the file /etc/dovecot/dovecot-sql.conf and add this line at the end


    Quote

    iterate_query = SELECT mail_addr AS user FROM mail_users


    now restart/reload dovecot service


    2) Create a new cronjob like this:


    crontab -e


    Quote

    40 3 12 * * /usr/bin/doveadm expunge -A mailbox INBOX.Junk savedbefore 30d >/dev/null 2>&1




    Source: http://wiki2.dovecot.org/Plugins/Expire



    Hope this can help many users :)



    Bye bye

    Hi,


    the mail quota warning is misconfigured.


    When a user reach the max quota, the mail received is like this


    Quote


    From: postmaster@{HOST_NAME}
    Subject: i-MSCP Quota Warning


    You are using 95% of the space assigned to your mailbox.


    I think that the script imscp-dovecot-quota.sh does not find the HOST_NAME variable


    Shell-Script
    1. #!/bin/sh
    2. PERCENT=$1
    3. USER=$2
    4. cat << EOF | /usr/lib/dovecot/deliver -d $USER -o "plugin/quota=maildir:User quota:noenforcing"
    5. From: postmaster@{HOST_NAME}
    6. Subject: i-MSCP Quota Warning
    7. You are using $PERCENT% of the space assigned to your mailbox.
    8. EOF


    For now, the solution is to modify the postmaster@{HOST_NAME} with other mail address desired
    My i-MSCP configuration:


    System: Ubuntu 14.04 (trusty tahr)
    i-MSCP Git 1.1.x
    Build: 20140915
    Server implementation: Apache/2.4.7 with php5-fpm 5.5.9 , dovecot 2.2.9


    Thank you very much

    Hi,


    the external mail server feature means to me that is possible to use i-MSCP as a complete mail relay and also as a spam filter for another mail server, but i have misunderstanding this function.


    It would be very useful to use i-MSCP as full mail relay as described before


    Thank you very much

    Hi Nuxwin,


    thank you very much for clarification.


    So, with this setting, i-MSCP work only when a valid MX record are alredy defined


    Code
    1. Domain: Setup a DNS MX record to relay mail of your entire domain, including subdomains.
    2. Spam Filter: Setup a DNS MX record to relay mail of your entire domain, including subdomains, but retains our server as final mailhost.
    3. Wildcard: Setup a DNS MX record to relay mail for inexistent subdomains.


    This means that this feature work exactly in a inverse mode that i need, correctly? :P



    Ok, i create a ticket for this request


    Thank you very much

    Hi Nuxwin,


    thank you very much for your reply. Sorry, but I don't understand very well...


    How it work it's clear, but if i want to use i-MSCP as spam filter to relay to another mail server, i must to have the mx record that point to the i-MSCP server and not to the real mail server.


    This function, without the name server installed and configured as default DNS on the ethernet, work only with the domains that are hosted by i-MSCP self, but does not work with the others mail servers because they read as MX record the real mail server and not the i-MSCP server


    So, it's this the real function desired to work?


    Thank you very much

    Hi,


    I've found a problem with the external mail server function.


    I've configured i-MSCP to use a external name server and when i set the external mail server this function does not work, because it supposed to use the internal DNS.


    In /etc/postfix/imscp/relay_domains i found correctly the domain desired to redirect, but postfix is not able to relay.


    The /etc/postfix/imscp/transport file is empty and to correctly relay the domain i must to edit this file with, eg:


    Code
    1. example.com smtp:bar.example:2025


    and run


    Code
    1. postmap /etc/postfix/imscp/transport



    It's possible to fix this problem?



    My i-MSCP configuration:


    System: Ubuntu 14.04 (trusty tahr)
    i-MSCP Git 1.1.x Build: 20140915
    Server implementation: Apache/2.4.7 with php5-fpm 5.5.9 , dovecot 2.2.9



    Thank you very much