I have added a new group to my system, which I will add my user to, so my UID/GIDs are sync'ed with my company's server when using NFS (fixing write permission issues).
I've created a new 'production' group but when I try to change the GID, usermod complains it cannot find the GID I'm referring to:
$ getent group production
production:x:1002:
$ sudo groupmod -g 32783 1002
groupmod: group '1002' does not exist
I'm confused, why can it not find this gid?
I hope this is the right site to ask this, I wasn't sure if here or superuser was more appropriate.
I've installed mongrel2 via Home Brew, which installed it to:
/usr/local/Cellar/mongrel2/1.7.5
However, I am stuck with configuration using m2sh as I don't know where to find my sqlite database.
$ tree
.
├── INSTALL_RECEIPT.json
├── LICENSE
├── README.md
├── bin
│ ├── m2sh
│ └── mongrel2
└── lib
└── mongrel2
├── config_modules
│ ├── null.so
│ └── zmq.s o
└── filters
└── null.so
5 directories, 8 files
locate config.sqlite provides no results, and I have no mongrel2 files anywhere in /etc.
So I've read a variety of tutorials and how-to's and I'm struggling to make sense of how to get SMTP auth working with virtual mailboxes in Postfix. I used this Ubuntu tutorial to get set up. I'm using Courier-IMAP and POP3 for reading mail which seems to be working without issue.
However, the credentials used to read a mailbox are not working for SMTP. I can see from /var/log/auth.log that PAM is being used, does this require a UNIX user account to work? As I'm using virtual mailboxes to avoid creating user accounts.
li305-246 saslauthd[22856]: DEBUG: auth_pam: pam_authenticate failed: Authentication failure
li305-246 saslauthd[22856]: do_auth : auth failure: [user=fred] [service=smtp] [realm=] [mech=pam] [reason=PAM auth error]
/var/log/mail.log
li305-246 postfix/smtpd[27091]: setting up TLS connection from mail-pb0-f43.google.com[209.85.160.43]
li305-246 postfix/smtpd[27091]: Anonymous TLS connection established from mail-pb0-f43.google.com[209.85.160.43]: TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)
li305-246 postfix/smtpd[27091]: warning: SASL authentication failure: Password verification failed
li305-246 postfix/smtpd[27091]: warning: mail-pb0-f43.google.com[209.85.160.43]: SASL PLAIN authentication failed: authentication failure
I've created accounts in userdb as per this tutorial. Does Postfix also use authuserdb?
What debug information is needed to help diagnose my issue?
main.cf:
# TLS parameters
smtpd_tls_cert_file = /etc/ssl/certs/smtpd.crt
smtpd_tls_key_file = /etc/ssl/private/smtpd.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
# SMTP parameters
smtpd_sasl_local_domain =
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
broken_sasl_auth_clients = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination
smtp_tls_security_level = may
smtpd_tls_security_level = may
smtpd_tls_auth_only = no
smtp_tls_note_starttls_offer = yes
smtpd_tls_CAfile = /etc/ssl/certs/cacert.pem
smtpd_tls_loglevel = 1
smtpd_tls_received_header = yes
smtpd_tls_session_cache_timeout = 3600s
tls_random_source = dev:/dev/urandom
/etc/postfix/sasl/smtpd.conf
pwcheck_method: saslauthd
mech_list: plain login
/etc/default/saslauthd
START=yes
PWDIR="/var/spool/postfix/var/run/saslauthd"
PARAMS="-m ${PWDIR}"
PIDFILE="${PWDIR}/saslauthd.pid"
DESC="SASL Authentication Daemon"
NAME="saslauthd"
MECHANISMS="pam"
MECH_OPTIONS=""
THREADS=5
OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd"
/etc/courier/authdaemonrc
authmodulelist="authuserdb"
I've only modified one line in authdaemonrc and restarted the service as per this tutorial. I've added accounts to /etc/courier/userdb via userdb and userdbpw and run makeuserdb as per the tutorial.
SOLVED
Thanks to Jenny D for suggesting use of rimap to auth against localhost IMAP server (which reads userdb credentials).
I updated /etc/default/saslauthd to start saslauthd correctly (this page was useful)
MECHANISMS="rimap"
MECH_OPTIONS="localhost"
THREADS=0
OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd -r"
After doing this I got the following error in /var/log/auth.log:
li305-246 saslauthd[28093]: auth_rimap: unexpected response to auth request: * BYE [ALERT] Fatal error: Account's mailbox directory is not owned by the correct uid or gid:
li305-246 saslauthd[28093]: do_auth : auth failure: [user=fred] [service=smtp] [realm=] [mech=rimap] [reason=[ALERT] Unexpected response from remote authentication server]
This blog post detailed a solution by setting IMAP_MAILBOX_SANITY_CHECK=0 in /etc/courier/imapd.
Then restart your courier and saslauthd daemons for config changes to take effect.
sudo /etc/init.d/courier-imap restart
sudo /etc/init.d/courier-authdaemon restart
sudo /etc/init.d/saslauthd restart
Watch /var/log/auth.log while trying to send email. Hopefully you're good!
I've followed this guide to get postfix set up. I've not completed it yet, as from sending test emails, email is no longer being delivered since switching to Maildir from mbox.
I have created a Maildir directory with cur, new and tmp sub directories.
~$ ll
drwxrwxr-x 5 greg greg 4096 2012-07-07 16:40 Maildir/
~$ ll Maildir/
drwxrwxr-x 2 greg greg 4096 2012-07-07 16:40 cur
drwxrwxr-x 2 greg greg 4096 2012-07-07 16:40 new
drwxrwxr-x 2 greg greg 4096 2012-07-07 16:40 tmp
Send a test email.
~$ netcat mail.example.com 25
220 ubuntu ESMTP Postfix (Ubuntu)
ehlo example.com
250-ubuntu
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
mail from: [email protected]
250 2.1.0 Ok
rcpt to: [email protected]
250 2.1.5 Ok
data
354 End data with <CR><LF>.<CR><LF>
Subject: test email
Hi,
Just testing.
.
250 2.0.0 Ok: queued as 56B541EA53
quit
221 2.0.0 Bye
Check the mail queue.
~$ mailq
Mail queue is empty
Check if mail has been delivered.
~$ ls -l Maildir/new
total 0
Some postfix settings:
~$ sudo postconf home_mailbox
home_mailbox = Maildir/
~$ sudo postconf mailbox_command
mailbox_command =
/var/log/mail.log
Jul 7 16:57:33 li305-246 postfix/smtpd[21039]: connect from example.com[178.79.168.xxx]
Jul 7 16:58:14 li305-246 postfix/smtpd[21039]: 56B541EA53: client=example.com[178.79.168.xxx]
Jul 7 16:58:33 li305-246 postfix/cleanup[21042]: 56B541EA53: message-id=<20120707155814.56B541EA53@ubuntu>
Jul 7 16:58:33 li305-246 postfix/qmgr[20882]: 56B541EA53: from=<[email protected]>, size=321, nrcpt=1 (queue active)
Jul 7 16:58:33 li305-246 postfix/smtp[21043]: 56B541EA53: to=<[email protected]>, relay=none, delay=30, delays=30/0.01/0/0, dsn=5.4.6, status=bounced (mail for example.com loops back to myself)
Jul 7 16:58:33 li305-246 postfix/cleanup[21042]: 1F68B1EA55: message-id=<20120707155833.1F68B1EA55@ubuntu>
Jul 7 16:58:33 li305-246 postfix/bounce[21044]: 56B541EA53: sender non-delivery notification: 1F68B1EA55
Jul 7 16:58:33 li305-246 postfix/qmgr[20882]: 1F68B1EA55: from=<>, size=1999, nrcpt=1 (queue active)
Jul 7 16:58:33 li305-246 postfix/qmgr[20882]: 56B541EA53: removed
Jul 7 16:58:33 li305-246 postfix/smtp[21043]: 1F68B1EA55: to=<[email protected]>, relay=none, delay=0, delays=0/0/0/0, dsn=5.4.6, status=bounced (mail for example.com loops back to myself)
Jul 7 16:58:33 li305-246 postfix/qmgr[20882]: 1F68B1EA55: removed
Jul 7 16:58:36 li305-246 postfix/smtpd[21039]: disconnect from domain.me[178.79.168.xxx]
Jul 7 17:10:38 li305-246 postfix/master[20878]: terminating on signal 15
Jul 7 17:10:39 li305-246 postfix/master[21254]: daemon started -- version 2.8.5, configuration /etc/postfix
Any ideas?
I have several domains on my VPS server, and postfix relaying the email to the appropriate gmail accounts via a virtual users table. This week I performed a sudo apt-get upgrade, this may be unrelated.
As of 2am on July 8th I'm seeing a lot of the following lines in my mail.log:
conversation with gmail-smtp-in.l.google.com[209.85.143.27] timed out while receiving the initial server greeting
conversation with alt1.gmail-smtp-in.l.google.com[74.125.79.27] timed out while receiving the initial server greeting
conversation with alt2.gmail-smtp-in.l.google.com[74.125.53.27] timed out while receiving the initial server greeting
Some message have got through though:
to=<[email protected]>, orig_to=<[email protected]>, relay=alt3.gmail-smtp-in.l.google.com[74.125.45.27]:25, delay=1130, delays=0.22/0/1128/1.8, dsn=2.0.0, status=sent (250 2.0.0 OK 1310095301 x67si39929948yhm.8)
I've seen this issue reported a lot around the internet but with no real solutions. I checked my postfix config but can't see that anything has changed.
postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
broken_sasl_auth_clients = yes
config_directory = /etc/postfix
inet_interfaces = all
inet_protocols = all
mailbox_size_limit = 0
mydestination = $myhostname, localhost, localhost.localdomain
myhostname = domainx.com
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 109.123.86.72/32
myorigin = /etc/mailname
readme_directory = no
recipient_delimiter = +
relayhost =
smtp_tls_note_starttls_offer = yes
smtp_tls_security_level = may
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Linux)
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination
smtpd_sasl_auth_enable = yes
smtpd_sasl_local_domain =
smtpd_sasl_path = private/auth-client
smtpd_sasl_security_options = noanonymous
smtpd_sasl_type = dovecot
smtpd_tls_CAfile = /etc/ssl/certs/dovecot.pem
smtpd_tls_auth_only = no
smtpd_tls_cert_file = /etc/ssl/certs/server.crt
smtpd_tls_key_file = /etc/ssl/private/server.key
smtpd_tls_loglevel = 1
smtpd_tls_received_header = yes
smtpd_tls_security_level = may
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtpd_tls_session_cache_timeout = 3600s
smtpd_use_tls = yes
tls_random_source = dev:/dev/urandom
virtual_alias_domains = domain.com, domain.co.uk, domainb.co.uk, domain.net
virtual_alias_maps = hash:/etc/postfix/valiases
I've tried flushing my mail queues (deleting all deferred mail) and restarting the server. I guess I'm running Linux and not Windows so this didn't help :)
I can post more configs if needed. Any ideas?
I've setup some virtual users for certain domains. I've got a local domain (and plan to add some virtual mailboxes but I'll save that for later).
localhost postfix/smtpd[23466]: NOQUEUE: reject: RCPT from somedomain.com[173.xxx.198.xxx]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<somedomain.com>
I've been over these settings. Each time I've adjusted /etc/postfix/valiases I've run postmap valiases. I've then run postfix reload (and /etc/init.d/postfix restart to be sure).
My main.cf (substituting domain.com in):
$ postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
broken_sasl_auth_clients = yes
config_directory = /etc/postfix
inet_interfaces = all
inet_protocols = all
mailbox_size_limit = 0
mydestination = $myhostname, localhost, localhost.localdomain
myhostname = domain.com
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 109.123.86.72/32
myorigin = /etc/mailname
readme_directory = no
recipient_delimiter = +
relayhost =
smtp_tls_note_starttls_offer = yes
smtp_tls_security_level = may
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Linux)
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination
smtpd_sasl_auth_enable = yes
smtpd_sasl_local_domain =
smtpd_sasl_path = private/auth-client
smtpd_sasl_security_options = noanonymous
smtpd_sasl_type = dovecot
smtpd_tls_auth_only = no
smtpd_tls_cert_file = /etc/ssl/certs/server.crt
smtpd_tls_key_file = /etc/ssl/private/server.key
smtpd_tls_loglevel = 1
smtpd_tls_received_header = yes
smtpd_tls_security_level = may
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtpd_tls_session_cache_timeout = 3600s
smtpd_use_tls = yes
tls_random_source = dev:/dev/urandom
virtual_alias_domains = hash:/etc/postfix/vdomains
virtual_alias_maps = hash:/etc/postfix/valiases
/etc/postfix/vdomains
domaina.com
domainb.com
/etc/postfix/valiases
[email protected] [email protected] # works
@domainb.com [email protected] # doesn't work
[email protected] [email protected] # doesn't work
[email protected] [email protected] # doesn't work
Any ideas?
I've lifted most of this from Wordpress, so any path on the domain like say /search or /list is directed to /index.php. Fine that works.
However, it should not do that if the file being requested exists in the document root. So if I request /exists.php it should run that script. Instead it's ignoring files on the filesystem and continues to serve index.php.
<VirtualHost *:80>
DocumentRoot /home/sites/dev
ServerName dev.vbox
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule . /index.php
ErrorLog /var/log/apache2/dev.error.log
</VirtualHost>
I've gone through the mod_rewrite documentation and various Google search results but I don't see anything wrong with my rewrite conditions. If the requested filename is a file or a directory, do not redirect to /index.php.
I've cd to the doc root and listed the contents of that directory, the file I'm requesting exists. My apache access log has entries for /exists.php.
The document root is a mounted directory that lives on the my Mac and the VM serving the request is Ubuntu install.
UPDATE: Thanks for responses on this but I'm going to drop exim and try Postfix.
Example:
*@domain-a.com > [email protected]
*@domain-b.com > [email protected]
*@domain-c.com > [email protected]
I tried adding the following to /etc/exim4/exim4.conf.template but the director isn't matching:
domaina_director:
driver = redirect
domains = dsearch;/etc/exim4/fwd_domains
data = ${lookup{$local_part}lsearch{/etc/exim4/fwd_domains/$domain}}
no_more
I've created the directory /etc/exim4/fwd_domains and in that, the file domain-a.com:
# cat domain-a.com
*: [email protected]
Update: I'm not convinced this syntax is correct. More importantly, my director doesn't seem to be picked up before reaching this point.
Run update-exim4.conf & restart exim4.
Send test e-mail:
# mail [email protected]
Subject: jdhfdjks
dsfhjdshf
.
Cc:
This appears in /var/log/exim4/mainlog:
2010-07-07 22:21:51 1OWd03-0002Zv-Kx <= root@primarydomain U=root P=local S=332
2010-07-07 22:21:51 1OWd03-0002Zv-Kx ** [email protected]: Unrouteable address
2010-07-07 22:21:51 1OWd03-0002Zx-MB <= <> R=1OWd03-0002Zv-Kx U=Debian-exim P=local S=1111
2010-07-07 22:21:51 1OWd03-0002Zv-Kx Completed
2010-07-07 22:21:51 1OWd03-0002Zx-MB => /var/mail/mail <root@primarydomain> R=mail4root T=address_file
2010-07-07 22:21:51 1OWd03-0002Zx-MB Completed
My director doesn't fire and the e-mail ends up in root's mailbox. Any ideas?