StevieD's questions

I'm running a mail server for about 30 people. I have had zero issues with it. But last week, several users began reporting an error in their email client, Outlook:

Checking the server mail log around the time of the error, I could only find these entries all happening around the same time. I'm not even sure if these entries are related to the Outlook error (doesn't seem to have anything to do with smtp) but the fact that the connections are closed all around the same time and the long "waiting for input" times looks suspicious:

 81218 Jan 18 11:56:56 ip-172-30-0-131 dovecot: imap(t.olixxxx)<3739040></Z84+joPNhRsOgYu>: Connection closed (IDLE running for 0.001 + waiting input for 1175.376 secs, 2 B in + 10 B out, state=wait-input) in=182 out=172366 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0        body_bytes=0
 81219 Jan 18 11:56:56 ip-172-30-0-131 dovecot: imap(s.damxxxx)<3739037><iQY3+joPottsOgYu>: Connection closed (IDLE running for 0.001 + waiting input for 1174.763 secs, 2 B in + 10 B out, state=wait-input) in=182 out=799331 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0        body_bytes=0
 81220 Jan 18 11:56:59 ip-172-30-0-131 postfix/smtpd[3740240]: warning: hostname 179.hosted-by.198xd.com does not resolve to address 45.129.14.179: Name or service not known
 81221 Jan 18 11:56:59 ip-172-30-0-131 postfix/smtpd[3740240]: connect from unknown[45.129.14.179]
 81222 Jan 18 11:57:00 ip-172-30-0-131 dovecot: imap(j.pomexxxxx)<3739095><k7z3/zoPqLdsOgYu>: Connection closed (IDLE running for 0.001 + waiting input for 1078.221 secs, 2 B in + 10 B out, state=wait-input) in=165 out=801497 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=       0 body_bytes=0
 81223 Jan 18 11:57:00 ip-172-30-0-131 dovecot: imap(a.cerxxxxx)<3739042><JCXQ+joPu5JsOgYu>: Connection closed (IDLE running for 0.001 + waiting input for 1169.527 secs, 2 B in + 10 B out, state=wait-input) in=182 out=303618 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0        body_bytes=0
 81224 Jan 18 11:57:00 ip-172-30-0-131 dovecot: imap(h.foxxxxx)<3739034><kpEo+joP9g5sOgYu>: Connection closed (IDLE running for 0.001 + waiting input for 1180.675 secs, 2 B in + 10 B out, state=wait-input) in=194 out=1927 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 bo       dy_bytes=0
 81225 Jan 18 11:57:00 ip-172-30-0-131 dovecot: imap(dxxxxxx)<3739057><xljV/DoPPnZsOgYu>: Connection closed (IDLE running for 0.001 + waiting input for 1135.454 secs, 2 B in + 10 B out, state=wait-input) in=182 out=458253 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 bod       y_bytes=0

The errors aren't happening all the time for users but often enough to be annoying. I'm running dovecot and postfix on Debian bullseye.

I'm migrating my nameserver machines from a datacenter into a cloud service (AWS) by replacing each of the physical machines with virtual machines. The nameservers I am migrating are authoritative for dozens of different domains.

During this process, I noticed something weird that has me confused:

The nameservers I want to migrate use the following authoritative nameservers:

ns1.example.com 
ns2.example.com

example.com is an old, legacy name for the nameservers and I am also the owner the example.com domain. When I went to check the zone records at example.com, I discovered the exact same zone records:

ns1.example.com 
ns2.example.com

This was unexpected. Basically, the example.com domain is authoritative for itself. I imagined I would have been using the registrar to manage the zone record and it would contain the ip addresses of each of the nameservers for example.com. Otherwise, what prevents the example.com name records from getting spoofed? Should I start using the registrar's nameservers to point to the authoritative name servers?

The current nameserver config was set up by someone else and I'm very rusty with setting up a DNS. Any guidance appreciated.

Running apk add oh-my-zsh on a docker container I get:

/ # apk add oh-my-zsh
ERROR: unable to select packages:
  oh-my-zsh (no such package):
    required by: world[oh-my-zsh]

The package seems to exist: https://pkgs.alpinelinux.org/package/edge/testing/x86/oh-my-zsh

Here is the docker file I'm building from:

FROM alpine:latest
RUN apk update
RUN apk add curl
RUN apk add zsh
RUN apk add git
RUN apk add oh-my-zsh

I want to use fail2ban to block specific ip addresses with:

sudo fail2ban-client set apache banip 111.111.111.111

I get:

 NOK: ('apache',)
Sorry but the jail 'apache' does not exist

I'm also confused because the jail.conf file does not contain an entry for [apache]. I tried adding it manually and restarting fail2ban. That didn't help.

All the tutorials I've found talk about the [apache] jail but it's absent on my stock version of jail.conf.

I'm running Debian 10 (buster).

If I have a path like this with a symlink:

/this/one/two/three

Is there is a quick one-liner for determining if one more more segments in the path is a symlink? For example, I'd want to detect if this, one, two, or three in the example above was a symlink.

One way is to compare the path containing the symlink to the output of readlink -f <path>. Wondering if there is a faster way.

I'm looking into the best way to manage the /etc/rsnapshot file which tells rsnapshot what to backup. I have about a hundred servers. While I could modify the /etc/rsnapshot file manually, I'm sure someone has invented this wheel before. Can anyone point me in the right direction?

I've got a cron job that runs a perl script that check the status of apache:

my $status = `sudo apachectl status`;

The cron job is run every minute without a problem. Sooner or later, however, I'll start getting the following error emailed from the cronjob:

'www-browser --dump http://localhost:80/server-status' failed.
Maybe you need to install a package providing www-browser or you
need to adjust the APACHE_LYNX variable in /etc/apache2/envvars

The error can also be generated if I run this from the command line:

www-browser --dump http://localhost:80/server-status

What's particularly odd, though, is that the apache report gets generated just fine except it has the error shown above at the end of it.

Does anyone know what explains this behavior and how I might get apache to not generate this error?

I'm tweaking my roundcube configuration which is using postfix/dovecot on the backend.

One annoyance is that if bad credentials are provided, it takes roundcube 20 to 30 seconds to respond. I was able to get this down to a more reasonable 8 seconds by setting $config['imap_timeout'] = 1 but that's still pretty slow.

Judging by the logs, roundcube tries to login 5 or 6 times before giving up. Is there a way to change how many times it logs in? Is there another way to improve response time?

I got this command:

ssh -A [email protected] rsync -avz /etc/apache2/ssl [email protected]:/etc/apache2

It throws an error:

Host key verification failed
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.1]

So I modified the command to this:

ssh -A -o "StrictHostKeyChecking=no" [email protected] rsync -avz -e "ssh -o StrictHostKeyChecking=no" /etc/apache2/ssl [email protected]:/etc/apache2

I still get the same error, however.

UPDATE If I first manually ssh into the example.org machine using agent forwarding and then ssh into 172.30.0.139 from example.org and then exit and then run the rsync command, everything works. I would of course like to avoid having to jump through this extra hoop.

I have files in a .zip archive I want to upload to a remote server over ssh. I want to avoid uploading and then unzipping because the remote server has limited space.

I could unzip the archive locally and then upload the unzipped files. That seems wasteful and then I have to do some cleanup.

Ideally, I'd like the files that get unpacked from the archive to get sent directly to the remote server instead of saved to the local host. Is there a way to do this over ssh?

I have an EC2 instance which requires a private key to log in with SSH.

I want to give someone easy access to the WordPress instance running on the server. They may need to modify some custom code on the server.

What is the most hasslefree way of getting this person temporary access to the server and then revoke? Should I set up a new key pair and then change back to the old key pair once they are done? Or is there a better way?

I set up and ran a couple of mail servers on ipv4 address on amazon ec2. These addresses were previously blacklisted and it took some work to stop some emails from getting blocked. The other problem is that amazon limits you to only 5 elastic ipv4 addresses per region (an elastic ip is equivalent of a static ip).

I plan to set up other mail servers on ec2. To avoid the problems above, I want to set up the mail servers with ipv6 out of the box and I want that ipv6 address to be the main static ip address for the machine and basically ignore the ipv4 address (except for when using ssh, etc.).

Is this possible? Will I run into problems with some mail servers not being able to talk to my ipv6 machine because they are ipv4? If so, is it possible to advertise the non-static ipv4 address instead? I'm not sure how this all works. I'm new to ipv6.

I'm using Debian buster. I changed the time zone with timedatectl and restarted postfix and dovecot but log records in mail.log are still showing UTC time. How do I fix this?

I've followed instructions here exactly: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/recognize-expanded-volume-linux.html for "Example: Extending the file system of NVMe EBS volumes" trying to grow a disk from 10 GB to 20 GB.

When I get to step 6, sudo xfs_growfs -d /, I get xfs_growfs: / is not a mounted XFS filesystem

Tried rebooting instance but that didn't help.

lsblk yields:

NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
nvme0n1      259:0    0   20G  0 disk
├─nvme0n1p1  259:1    0 19.9G  0 part /
├─nvme0n1p14 259:2    0    3M  0 part
└─nvme0n1p15 259:3    0  124M  0 part /boot/efi

df -h outputs:

Filesystem       Size  Used Avail Use% Mounted on
udev             224M     0  224M   0% /dev
tmpfs             47M  2.2M   45M   5% /run
/dev/nvme0n1p1    20G  9.1G  9.6G  49% /
tmpfs            233M     0  233M   0% /dev/shm
tmpfs            5.0M     0  5.0M   0% /run/lock
tmpfs            233M     0  233M   0% /sys/fs/cgroup
/dev/nvme0n1p15  124M  262K  124M   1% /boot/efi
tmpfs             47M     0   47M   0% /run/user/1000

Notice the available space on the /dev/nvme0n1p1 device says 49% but according to the Used/Avail columns it should be more like 99%.

I'm testing remote smtp login on a server and keep getting 535 5.7.8 Error: authentication failed: authentication failure errors in the syslog and mail.log. Postfix is configured to use system user names and passwords.

I generated a user name and password with perl -MMIME::Base64 -e 'print encode_base64("username");' and perl -MMIME::Base64 -e 'print encode_base64("password");'

I am logging into the server with openssl s_client -starttls smtp -connect email.example.com:587 and using the auth login to input the user name and password.

I've turned on dovecot debugging but not seeing much in logs other than the authentication failure message.

Postfix main.cf:

# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.

smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination
#smtpd_sasl_type = dovecot
#smtpd_sasl_auth_enable = yes
myhostname = email.example.org
mydomain = example.com
myorigin = example.com
home_mailbox = Maildir/
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
mydestination = $myhostname, email.example.com, ip-172-30-0-39.ec2.internal, localhost.ec2.internal, localhost, $mydomain, localhost.$mydomain
relayhost =
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
inet_protocols = all

dovecot:

auth_debug = yes
auth_debug_passwords = yes
auth_mechanisms = plain login
auth_verbose = yes
mail_location = maildir:~/Maildir
mail_privileged_group = mail
namespace inbox {
  inbox = yes
  location =
  mailbox Drafts {
    special_use = \Drafts
  }
  mailbox Junk {
    special_use = \Junk
  }
  mailbox Sent {
    special_use = \Sent
  }
  mailbox "Sent Messages" {
    special_use = \Sent
  }
  mailbox Trash {
    special_use = \Trash
  }
  prefix =
}
passdb {
  driver = pam
}
protocols = " imap"
service auth {
  unix_listener /var/spool/postfix/private/auth {
    group = postfix
    mode = 0666
    user = postfix
  }
  unix_listener auth-userdb {
    mode = 0666
  }
}
service imap-login {
  inet_listener imap {
    port = 143
  }
  inet_listener imaps {
    port = 993
    ssl = yes
  }
}
ssl_cert = </etc/dovecot/private/dovecot.pem
ssl_client_ca_dir = /etc/ssl/certs
ssl_dh = # hidden, use -P to show it
ssl_key = # hidden, use -P to show it
userdb {
  driver = passwd
}

service auth {
  # auth_socket_path points to this userdb socket by default. It's typically
  # used by dovecot-lda, doveadm, possibly imap process, etc. Users that have
  # full permissions to this socket are able to get a list of all usernames and
  # get the results of everyone's userdb lookups.
  #
  # The default 0666 mode allows anyone to connect to the socket, but the
  # userdb lookups will succeed only if the userdb returns an "uid" field that
  # matches the caller process's UID. Also if caller's uid or gid matches the
  # socket's uid or gid the lookup succeeds. Anything else causes a failure.
  #
  # To give the caller full permissions to lookup all users, set the mode to
  # something else than 0666 and Dovecot lets the kernel enforce the
  # permissions (e.g. 0777 allows everyone full permissions).
  unix_listener auth-userdb {
    mode = 0666
    #user =
    #group =
  }

  # Postfix smtp-auth
  unix_listener /var/spool/postfix/private/auth {
    mode = 0666
    user = postfix
    group = postfix
  }

  # Auth process is run as this user.
  #user = $default_internal_user
}

service auth-worker {
  # Auth worker process is run as root by default, so that it can access
  # /etc/shadow. If this isn't necessary, the user should be changed to
  # $default_internal_user.
  #user = root
}

service dict {
  # If dict proxy is used, mail processes should have access to its socket.
  # For example: mode=0660, group=vmail and global mail_access_groups=vmail
  unix_listener dict {
    #mode = 0600
    #user =
    #group =
  }
}

I'm trying to get a roundcube/dovecot/postfix on a debian box on amazon running. I can log in and receive emails, but I cannot send. I get an error in roundcube, smtp authentication error (220) Authentication failed.

Roundcube error logs:

[24-Sep-2020 08:47:24 +0000]: <a83d4mll> PHP Error: STARTTLS failed (POST /?_task=mail&_unlock=loading1600937244456&_framed=1&_lang=en_US&_action=send)
[24-Sep-2020 08:47:24 +0000]: <a83d4mll> PHP Error: Invalid response code received from server (POST /?_task=mail&_unlock=loading1600937244456&_framed=1&_lang=en_US&_action=send)
[24-Sep-2020 08:47:24 +0000]: <a83d4mll> SMTP Error: Authentication failure: STARTTLS failed (Code: ) in /opt/bitnami/apps/roundcube/htdocs/program/lib/Roundcube/rcube.php on line 1702 (POST /?_task=mail&_unlock=loading1600937244456&_framed=1&_lang=en_US&_action=send)

roundcube SMTP log:

[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Connecting to tls://webmail.theomnihealthgroup.com:587...
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Recv: 220 mail.theomnihealthgroup.com ESMTP Postfix (Debian/GNU)
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Send: EHLO webmail.theomnihealthgroup.com
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Recv: 250-mail.theomnihealthgroup.com
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Recv: 250-PIPELINING
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Recv: 250-SIZE 10240000
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Recv: 250-VRFY
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Recv: 250-ETRN
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Recv: 250-STARTTLS
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Recv: 250-ENHANCEDSTATUSCODES
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Recv: 250-8BITMIME
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Recv: 250-DSN
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Recv: 250-SMTPUTF8
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Recv: 250 CHUNKING
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Send: STARTTLS
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Recv: 220 2.0.0 Ready to start TLS
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Send: QUIT
[24-Sep-2020 08:52:08 +0000]: <a83d4mll> Recv: ^V^C^C^A,^L^@^A(^C^@^] <80>ÄS<96>ñrgY(v^P¿<97>Åjò<¬<9e>ò^U­')gÔ<86>hG|¦^P^H^D^A^@Dv(RV<92>Tíìãô^HÂè<9c>è<98>ûÐU§­Ð^Bfã<87><9a>4BNPÙ<82>GÏs¬

I'm pretty sure this has to do with the certs but I'm not sure how to fix it.

• Roundcube is running on apache at https://webmail.theomnihealthgroup.com
• I have an ssl cert associated with the webmail domain
• server is at theomnihealthgroup.org

postfix main.cf:

# Debian specific:  Specifying a file name will cause the first
# line of that file to be used as the name.  The Debian default
# is /etc/mailname.
#myorigin = /etc/mailname

smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

readme_directory = no

# See http://www.postfix.org/COMPATIBILITY_README.html -- default to 2 on
# fresh installs.
compatibility_level = 2



# TLS parameters
stmpd_tls_security_level = may
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
#smtpd_tls_cert_file=/opt/bitnami/letsencrypt/certificates/webmail.theomnihealthgroup.com.crt
#smtpd_tls_key_file=/opt/bitnami/letsencrypt/certificates/webmail.theomnihealthgroup.com.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.

smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination
myhostname = mail.theomnihealthgroup.com
#myhostname = theomnihealthgroup.com
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = theomnihealthgroup.com
mydomain = theomnihealthgroup.com
mydestination = $myhostname, ip-172-30-0-246.ec2.internal, localhost.ec2.internal, localhost, $mydomain, localhost.$mydomain
relayhost =
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
inet_protocols = all
home_mailbox = Maildir/
local_recipient_maps = proxy:unix:passwd.byname $alias_maps
policyd-spf_time_limit = 3600
smtpd_recipient_restrictions =
   permit_mynetworks,
   permit_sasl_authenticated,
   reject_unauth_destination,
   check_policy_service unix:private/policyd-spf
# Milter configuration
milter_default_action = accept
milter_protocol = 6
smtpd_milters = local:opendkim/opendkim.sock
non_smtpd_milters = $smtpd_milters

dovecot config:

mail_location = maildir:~/Maildir
mail_privileged_group = mail
namespace inbox {
  inbox = yes
  location =
  mailbox Drafts {
    special_use = \Drafts
  }
  mailbox Junk {
    special_use = \Junk
  }
  mailbox Sent {
    special_use = \Sent
  }
  mailbox "Sent Messages" {
    special_use = \Sent
  }
  mailbox Trash {
    special_use = \Trash
  }
  prefix =
}
passdb {
  driver = pam
}
protocols = " imap"
service auth {
  unix_listener /var/spool/postfix/private/auth {
    mode = 0666
  }
  unix_listener auth-userdb {
    mode = 0666
  }
}
service imap-login {
  inet_listener imap {
    port = 143
  }
}
ssl_cert = </etc/dovecot/private/dovecot.pem
ssl_client_ca_dir = /etc/ssl/certs
ssl_dh = # hidden, use -P to show it
ssl_key = # hidden, use -P to show it
userdb {
  driver = passwd
}

roundcube config.inc.php

$config = array();
$config['debug_level'] = 1;
$config['smtp_debug'] = true;

// Database connection string (DSN) for read+write operations
// Format (compatible with PEAR MDB2): db_provider://user:password@host/database
// Currently supported db_providers: mysql, pgsql, sqlite, mssql, sqlsrv, oracle
// For examples see http://pear.php.net/manual/en/package.database.mdb2.intro-dsn.php
// NOTE: for SQLite use absolute path (Linux): 'sqlite:////full/path/to/sqlite.db?mode=0646'
//       or (Windows): 'sqlite:///C:/full/path/to/sqlite.db'
$config['db_dsnw'] = 'mysql://bn_roundcube:22223abcde@localhost:3306/bitnami_roundcube';

// The IMAP host chosen to perform the log-in.
// Leave blank to show a textbox at login, give a list of hosts
// to display a pulldown menu or set one host as string.
// Enter hostname with prefix ssl:// to use Implicit TLS, or use
// prefix tls:// to use STARTTLS.
// Supported replacement variables:
// %n - hostname ($_SERVER['SERVER_NAME'])
// %t - hostname without the first part
// %d - domain (http hostname $_SERVER['HTTP_HOST'] without the first part)
// %s - domain name after the '@' from e-mail address provided at login screen
// For example %n = mail.domain.tld, %t = domain.tld
$config['default_host'] = 'mail.theomnihealthgroup.com';

// SMTP server host (for sending mails).
// Enter hostname with prefix ssl:// to use Implicit TLS, or use
// prefix tls:// to use STARTTLS.
// Supported replacement variables:
// %h - user's IMAP hostname
// %n - hostname ($_SERVER['SERVER_NAME'])
// %t - hostname without the first part
// %d - domain (http hostname $_SERVER['HTTP_HOST'] without the first part)
// %z - IMAP domain (IMAP hostname without the first part)
// For example %n = mail.domain.tld, %t = domain.tld

# Also tried: $config['smtp_server'] = 'tls://theomnihealthgroup.com';
$config['smtp_server'] = 'tls://webmail.theomnihealthgroup.com';

// SMTP port. Use 25 for cleartext, 465 for Implicit TLS, or 587 for STARTTLS (default)
$config['smtp_port'] = 587;

// SMTP username (if required) if you use %u as the username Roundcube
// will use the current username for login
$config['smtp_user'] = '%u';

// SMTP password (if required) if you use %p as the password Roundcube
// will use the current user's password for login
$config['smtp_pass'] = '%p';
$config['smtp_auth_type'] = '';

// provide an URL where a user can get support for this Roundcube installation
// PLEASE DO NOT LINK TO THE ROUNDCUBE.NET WEBSITE HERE!
$config['support_url'] = 'https://community.bitnami.com/';

// Name your service. This is displayed on the login screen and in the window title
$config['product_name'] = 'Omni Mail';

// This key is used to encrypt the users imap password which is stored
// in the session record. For the default cipher method it must be
// exactly 24 characters long.
// YOUR KEY MUST BE DIFFERENT THAN THE SAMPLE VALUE FOR SECURITY REASONS
$config['des_key'] = 'KJDKJIJEIKDJ';

// List of active plugins (in plugins/ directory)
$config['plugins'] = array(
    'archive',
    'zipdownload',
);

// skin name: folder from skins/
$config['skin'] = 'elastic';
$config['default_port'] = 143;
$config['mime_param_folding'] = 0;

I'm running rsync via ssh to a remote machine. After running the command, I'd like to confirm that the command I sent to the remote machine is the one that actually ran. Is this logged somewhere? The remote machine is a debian box.

I have a /etc/hosts file that has something like this line for 127.0.0.1 for hostnames I'm using for development sites:

127.0.0.1 localhost site1.example.com site2.example.com site3.example.com

I noticed that things broke, however, if I added in a domain with just digits to the entry:

127.0.0.1 localhost site1.example.com site2.example.com site3.example.com 10.example.com site4.example.com

With this line, site4.example.com no longer resolved to 127.0.0.1 but to the IP address for example.com. So it's as if it didn't exist in the /etc/hosts file. The first couple of sites still resolved to 127.0.0.1. But anything placed after the 10.example.com entry no longer resolves to 127.0.0.1. If I remove the 10.example.com entry, it resolves to 127.0.0.1.

Anyone knows why a subdomain with all digits might mess with /etc/hosts?

This is on a Mac.

Running Debian Stretch 9.5 with apache2. After upgrading from Debian 8, I can no longer access phpmyadmin from http://localhost/phpmyadmin. I get a page not found error. Everything looks good on the apache config side:

• apache2.conf contains IncludeOptional conf-enabled/*.conf
• /etc/apache2/conf-enabled contains phpmyadmin.conf which symlinks to config in /etc/phpmyadmin/apache.conf
• I purposefully introduced syntax error into phpmyadmin config file and reloaded apache and it choked as expected. So apache is definitely loading the config file.
• Alias in config file is set to Alias /phpmyadmin /usr/share/phpmyadmin which is where the phpmyadmin files are installed.

I have uninstalled and reinstalled the phpmyadmin package but that didn't help. I followed the instructions in /usr/share/doc/phpmyadmin/README.debian.gz which said to run sudo dpkg-reconfigure -plow phpmyadmin but that didn't help either.

I think I'm overlooking something basic in my apache config but I'm not sure what. Thanks.

I've got a production server running older websites running on a Debian Jesse machine with PHP package 5.3.3-7+squeeze26. I have a development machine set up with a newer PHP package (5.6.29-0+db8ul) running in VirtualBox. When I import one of the old websites and try to run it on the development machine, I get PHP errors like: php Call-time pass-by-reference has been removed.

My development machine is running phpmyadmin and apache which, I assume, rely on the newer version of php. So what are my options for getting these older website running on the development machine?

a) Can I run two versions of php side by side on the machine and have this website run on the older version?

b) Should I uninstall current version of php on development machine and run it off an older version of php5? In this case, what do I do about apache2 and phpmyadmin? Do those have to be rolled back, too?

c) Should I just set up a new virtual machine with an old version of php? Though this is probably the best option and the one I'm leaning toward, I'm still curious to know if options a and b are possible.