LMTP#247
Open
runout-at wants to merge 11 commits into
Open
Conversation
merge vexim2 to runout
insensitiveclod
added a commit
to insensitiveclod/vexim2
that referenced
this pull request
May 14, 2019
-- As inspired by vexim#247 -- Added pgsql-lmtp and mysql-lmtp variants of files that require modification -- Added dovecot-lmtp.txt variant with instructions -- README.md has been altered with info on how to enable - postgresql > 9.5 has no 'NOCREATEUSER' ability; altered pgsql.sql and README.md
This was referenced Jun 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a rewrite of my original LMTP idea ( #150 ).
I do run this in production for about 2 month now.
As @Udera mentioned it in #233 i'd put the code for a PR together.
Right now config is very simple. Later this could be integrated in the DB, UI,...
Do we want this per domain or per user or a combination?
If 'per user' we could set the user table type-field to 'lmtp' and the smtp field to the socket or command.
Actually this PR fixes an issue if VEXIM_LOCALPART_SUFFIX is set.
Mails with a To:localpart+suffix... were not handled correctly in the vacation and forward routers.