Tag Info

New answers tagged

0

This should just be an MTA configuration issue. Configure a Postfix smarthost on both the mail1 and mail2 machines to send all mail for the relevant domains (or all mail if all they do is receive email) to webmail1. The following describes a typical Postfix configuration to achieve this, either by adding a relayhost entry to main.cf (if you want all email ...


0

Ok so my whole installation was a mess. postconf was still configured to write mail to /var/mail/USERNAME . Dovecot "sent" and "draft" mails were saved to /home/USERNAME/mail/ using mbox so I reconfigured all that and decided to use mailDir To do so, I reconfigured postfix by doing postconf -e "home_mailbox = Maildir/" postconf -e "mailbox_command =" and ...


1

You define this parameter in main.cf smtpd_sasl_path = /var/run/dovecot/auth-client This tells postfix where path the unix socket for SASL connection. Yet, in dovecot config you define the SASL socket was in /var/spool/postfix/private/auth service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = ...


0

You could also try to add postfix user to sasl group.


1

I don't know to what extent you've redacted the output above, but in the important lines of the SQL query (Password mismatch, and the line that follows) it's comparing an MD5-hash to a very long string. MD5 hashes are 32 bytes long, so no string at all will ever MD5-hash to the sort of string you give, which looks to be 63 bytes long, and in addition is ...


1

Sorry for misleading comment above. When you use sasldb, then you doesn't saslauthd to running. So you can safely remove it from startup script. When you use system user to password checking, then you must run saslauthd. The first step is creating a database for sasldb using saslpassword binary # saslpasswd2 -c username@example.com Password: Again (for ...


2

Finally got my setup to work with postfix multiple instances masegaloeh mentioned. I tried to use exim4, but apt-get install exim4 automatically uninstalled postfix, without even a prompt! Anyways, here is how I got it to work: #Adds some lines to main.cf enabling multiple instance postmulti -e init #Creates a new instance at the directory ...


3

As you can see, there's no smtpd_sasl_path in our output of postconf -n Why? The answer is easy. Because there's no smtpd_sasl_path set. Have a look at your first snippet: There's a typo in it. You wrote smptd_sasl_path = private/auth -- but there's a difference between smtpd and smptd. Because Postfix doesn't have informations where to find the socket, ...


3

Dovecot allows you to configure a master user which can be used to access user mailboxes without knowing their passwords. The master user can be used with imapsync (as well as most other IMAP tools) to copy the messages between servers. From the dovecot configuration file on my server: By adding master=yes setting inside a passdb you make the passdb a ...


1

When both mail servers use the same mail format (mbox, Maildir, MBX), the simplest solution is to just copy over the directory structures containing the mails, e.g. using scp. This also preserves the Message-IDs, as opposed to tools like doveadm copy. Another possibility is to use the IMAP-protocol itself for IMAP copying using tools like imapsync. But in ...


0

You need to escape twice, so that \[git-.*\] becomes \\[git-.*\\]


1

You can use the Mailbox alias plugin requiring Dovecot 2.1.10+ which creates symlinks on the filesystem level to provide one directory with more than one name. The both directories have the same content. Example configuration where Sent and Trash are the real mailboxes for the aliases "Sent Items" and "Deleted Items": mail_plugins = $mail_plugins ...


1

The problem(s) are resolved. As seen in the comments there was a problem saying that my logs did not work. This was resolved following the the instructions on a question here (it is the not approved answer with CentOS 7 in mind) After the logs worked again the solution was ony 5 seconds away. The logs were saying following error: Feb 22 18:15:27 ...


1

Looks like you are missing last slash when you specified maildir directory in /etc/postfix/vmail_mailbox. Excerpt from man 5 postconf virtual_mailbox_maps (default: empty) ... The virtual(8) delivery agent uses this table to look up the per-recipient mailbox or maildir pathname. If the lookup result ends in a slash ("/"), maildir-style ...


1

Since you imply you're not getting any error, I'm wondering if the mailboxes you have set in /etc/postfix/vmail_mailbox do not match the /var/vmail/%d/%n Dovecot virtual mailbox structure. For example, I would expect it to contain something like: leesinblik@jeroened.be jeroened.be/leesinblik/ In any case, look in the /var/vmail directory and see where ...


0

It seems your configuration is fine, I sent a test mail for you at test@jeroened.be, and this is the reply of your server: Feb 22 14:57:22 iabsis postfix/smtp[12704]: DDAE720052E: to=<test@jeroened.be>, relay=mail.jeroened.be[5.196.227.108]:25, delay=6.5, delays=0.33/0.02/6.1/0.03, dsn=5.1.1, status=bounced (host mail.jeroened.be[5.196.227.108] said: ...


2

This error message: Feb 21 15:52:46 server dovecot: auth-worker(3609): Error: pam(test,<myip>): pam_authenticate() failed: Authentication failure can be caused by several reasons such as: User didn't exist Incorrect password Based on above useradd command useradd --shell /bin/bash --create-home --password <password> <username> I ...


2

It seems to be a bug that Gmail does not respect the ESMTPA in the Received header to show the MUA is a trusted host. Some possible workarounds come to mind: use split MX, that is, one Exim instance to receive and forward from authenticated clients, and a second to receive into mailboxes. That simulates the ISP-to-ISP mail that Gmail may be expecting, ...


5

[...] we import that mail in Gmail like any other emails from our boxes [...] That's wrong, as the mail headers tell as something different: Received: from server.webvizarts.com (server.webvizarts.com . [188.40.153.39]) by mx.google.com with ESMTPS id ge6si41332059wjd.24.2015.02.19.06.26.03 for <example@gmail.com> ...


1

For a mail server, there are free services that will check the various security measures for your domain. Check this site as an example: http://mxtoolbox.com/ Check your domain and implement the recommendations that the site suggests and your mail server should be secure. Since you have other services running on the server (assuming Ubuntu, and exposed to ...


-1

Check your nameserver in /etc/resolv.conf, try Google's 8.8.8.8: sudo vi /etc/resolv.conf Change the nameserver IP: nameserver 8.8.8.8 Then restart postfix: sudo /etc/init.d/postfix restart


7

Disclaimer: This answer was speculation one until GMail person confirmed it. Looks like it's GMail mishandle your fetched email here. Some peoples also report similar case with yours in here, here or here The problem is: GMail also deploying SPF measure when scanning email after fetching it via POP3. Normally SPF-checking take place in SMTP transaction ...


1

One last point I should mention in case someone is confused as I was, about why the mail ultimately gets put into /var/mail/rcook/ when postfix changed "rcook" to "rcook@example.net". This happens because in /etc/dovecot/conf.d/10-mail.conf I have this: mail_location = maildir:/var/mail/%n:LAYOUT=fs which strips off the domain name. Once @masegaloeh ...


2

Let met tell you the secret of email delivery process in linux, featuring sendmail binary and postfix. When your run date | mail -s 'testing' rcook you tell sendmail to send email to rcook, a recipient address without domain parts to postfix. Because you have parameter append_at_myorigin = yes (default value), then postfix will add domain parts to ...


3

In dovecot -n output, looks like you have enabled 'ssl-enforcing' mode ssl = required The result is here the dovecot output when telnet 127.0.0.1 143 * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS LOGINDISABLED] Dovecot ready. With 'ssl-enforcing' mode, IMAP client (javamail code) must issuing STARTTLS command ...


2

For SQL-lookup password, dovecot has additional documentation in here. For additional info you can read a thread on SO: How to securely generate SSHA256 or SSHA512 hashes in PHP?. In this answer I assume that you use MySQL for database. In order to matching dovecot auth scheme and your custom auth scheme, one of the method is your query must be returned ...


2

1: first you need to check the service saslauthd is running 2: because postfix running in a chroot you need to edit /etc/sysconfig/saslauthd and change the variable OPTIONS to OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd -r" Now create the directory for saslauthd under postfix chroot mkdir /var/spool/postfix/var/run/saslauthd 3: now after ...



Top 50 recent answers are included