LMTP delivery to Dovecot stops working in 3.1.4-1

On Friday, January 06, 2017 01:04:21 AM you wrote:

What does the line for dovecot-lmtp in master.cf look like?

Scott K

I don't have anything about dovecot-lmtp in master.cf. The only uncommented line I have about lmtp in master.cf is "lmtp unix - - n - - lmtp". In main.cf, I have "mailbox_transport = lmtp:unix:/var/spool/postfix/private/dovecot-lmtp".

I have the same problem.

My master.cf has no line mentioning "dovecot-lmtp".

My main.cf has line "mailbox_transport = lmtp:unix:/var/spool/postfix/private/dovecot-lmtp".

When upgrading Postfix, the process modified my "master.cf" from "lmtp unix - - n - - lmtp" to "lmtp unix - - n - - smtp".

Is it possible that there is trailing whitespace on the lmtp line in master.cf? That would explain the issue.

Based on the reported contents of the line, I'm assuming that's the case and uploading 3.1.4-2. If that doesn't fix it, please reopen this bug.

No, there is no trailing whitespace on any of the lines related to lmtp in either of my configuration files.

No trailing whitespace.

On Friday, January 06, 2017 05:30:12 PM you wrote:
> No, there is no trailing whitespace on any of the lines related to lmtp
> in either of my configuration files.

The regex is improved in 3.1.4-2, so please check again once you've upgraded
to that version.

Scott K

I just upgraded and still have exactly the same problem as before.

On Sat, Jan 07, 2017 at 01:26:41PM -0000, Michael Marley wrote:
> I just upgraded and still have exactly the same problem as before.

During the upgrade, did it say that it was changing master.cf as below?

In master.cf:
  using smtp binary for lmtp service (symlink removed)

In either case, please send me unredacted (other than any passwords) master.cf
and /var/log/apt/term.log from the upgrade?

lamont

Here is the relevant section of term.log. It does say that it is removing the symlink and updating the configuration.

Here is the master.cf file.

3.1.4-3 should be uploaded this weekend, with the fix.

@mamarley - A postfix package with the fix (for testing) is in ppa:lamont/postfix -- can you confirm that the bug is fixed with that version?

thanks

Sure, but it appears to be FTBFS at the moment.

There is a new test version in the ppa. This one built. :/

That works, thanks!

This bug was fixed in the package postfix - 3.1.4-2

---------------
postfix (3.1.4-2) unstable; urgency=medium

  * Update postfix Suggestions.
  * Update postfix-sqlite postinst/prerm to reflect that addmap is idempotent.
  * Restore so.1.0.1 symlinks for map libraries and change how new entries are
    added. Closes: #850400
  * Be more aggressive in retiring usage of lmtp binary. Closes: #850430
    LP: #1654453
  * Check symlinks separately in postfix-script, to allow library symlinks.
    This will go away once the symlinks are dropped again.

 -- LaMont Jones <email address hidden> Fri, 06 Jan 2017 08:41:36 -0700

Hello! Cna you help how to install it?
I added:
 add-apt-repository ppa:lamont/postfix

The problem:
W: GPG error: http://ppa.launchpad.net/lamont/postfix/ubuntu zesty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY CD264BE5EA87984F
E: The repository 'http://ppa.launchpad.net/lamont/postfix/ubuntu zesty InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

How can I install so I can use postfix the last fix fo the fatal: unknown service: private/dovecot-lmtp/tcp?

THANKS!

When upgrading Postfix, I have this same problem. Upgrading process modified my "master.cf" from "lmtp unix - - - - - lmtp" to "lmtp unix - - y - - smtp".

I change again smtp -> lmtp : "lmtp unix - - y - - lmtp" and all began to work.