ffxsam's questions

I have an email server running (Postfix and Dovecot). I also have an archive of a bunch of raw email files that look like this:

1492038516.M77184P7110.mail2.mysite.com,S=39609,W=40258:2,Sab

I would've used imapsync to get these onto the mail server, but they're already archived on my Mac. So I copied about 1500 of these files directly into /var/vmail/domain/user/.Sent/cur on my mail server, however, things look a bit odd in RoundCube:

Just dozens of pages of a single (no subject) message.

Is there some way to force Dovecot to properly reindex everything? Because something is definitely wrong here, but I have no idea how to fix it. Or if there's a better way to import raw email files, I'd love to hear it.

I'm making a script that installs MariaDB, and I'd like to set a root password. I've got the following in said script:

DEBIAN_FRONTEND=noninteractive

echo mariadb-server-10.0 mariadb-server-10.0/root_password password tmpsetup | debconf-set-selections
echo mariadb-server-10.0 mariadb-server-10.0/root_password_again password tmpsetup | debconf-set-selections
apt-get install -y mariadb-server

This doesn't seem to work, as I can't log into the root account with the "tmpsetup" password. What am I doing wrong?

I for the life of me cannot figure out how to make aliases for locations.

Basically, I have /var/www on my server, which could contain any number of folders (for different applications). One of those is ViMbAdmin, located in /var/www/vimbadmin, and the actual web files that should be served to the client are in /var/www/vimbadmin/public. Here's what I have so far, which is failing:

server {
    listen      80;
    server_name myserver.com;
    root        /var/www;

    index index.php;

    # Logs
    access_log  /var/log/nginx/vimbadmin.access.log;
    error_log   /var/log/nginx/vimbadmin.error.log;

    location /vimbadmin/public {
        try_files $uri $uri/ /index.php?$args;
    }

    location /mail2admin {
      alias /vimbadmin/public;
    }

    # Pass the PHP scripts to FastCGI server
    location ~ \.php$ {
        # Prevent Zero-day exploit
        try_files $uri =404;

        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        #NOTE: You should have "cgi.fix_pathinfo = 0;" in php.ini

        fastcgi_pass    unix:/var/run/php5-fpm.sock;
        fastcgi_index   index.php;
        fastcgi_param   SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include         fastcgi_params;
    }
}

My goal is to set it up so that hackers can't just try to go to http://myserver.com/vimbadmin, so the actual URL will be http://myserver.com/mail2admin. What am I doing wrong? I'm really confused about the relationships between root, location, and alias.

Spam scores are above 5 (my threshold)!

X-Spam-Status: Yes, score=5.924 tagged_above=-9999 required=5
    tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_IMAGE_RATIO_02=0.805,
    HTML_MESSAGE=0.001, NO_RECEIVED=-0.001, NO_RELAYS=-0.001,
    RCVD_REMOVED=3.75, T_REMOTE_IMAGE=0.01, URIBL_GREY=1.084,
    URIBL_RHS_DOB=0.276] autolearn=disabled

RCVD_REMOVED seems to be the culprit. I believe it's because amavis is stripping that down, and spamassassin doesn't like it:

Received: from mail.xx ([127.0.0.1])
    by localhost (mail.xx [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id U6DCLGNBdNtN for <[email protected]>;
    Tue, 22 Dec 2015 01:01:11 -0800 (PST)

I could just raise the threshold score to 6, but I'd rather fix this issue instead.

I haven't been able to find any best practices for AWS security groups. I figure there are two approaches I could take, but I'm not sure on if there are any particular drawbacks to either one.

Scenario 1:
Define small, specialized security groups such as "ssh," "mongodb," "web," etc, and then in essence "stacking" multiple security groups on each EC2 instance to specify which ports are open.

Scenario 2:
Define larger, more generic security groups such as "web1" which opens ports 80, 443, ssh, database, and apply this to any appropriate EC2 instances.

I think I'd rather go with scenario #1, but don't know if there are any disadvantages or technical issues with this approach. Is there a best practice?