-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add lmtp_add_received_headers bool setting #74
Conversation
At least I'd call it "lmtp_add_received_header" since there's only a single header being added. |
sirainen: agree, thanks for the input |
Please accept, comment or close |
Sorry for the delay, we'll try to look at this soon. |
Well, I hate adding new settings, but I guess this can be useful. So mainly:
|
Big +1 on this. Ping @bjne |
Ping!? @bjne |
Sorry for the delay. Will fix soon! |
Add the ability to prevent dovecot/lmtp from adding received header. This is useful if one needs to use LMTP, but does not want additional received headers because: 1) dovecot does not have correct information to add to the headers, and causes misleading/incorrect information 2) does not want to expose internal information The default value is true, as current behavior
0f53bc8
to
df465ae
Compare
@sirainen sorry for the delay, the fixes you requested are done. |
@tomsommer @bjoe2k4 guess my part is done now, sorry for taking the time |
@sirainen can you please merge now? |
Created internal merge request for this. I am not sure when that will roll out in a release though. |
@stephanbosch why not just merge it? |
@sirainen is there any progress here? |
…d_received_headers
Time flies... |
So it does, I'll check what's going with this. |
thx |
merged |
Add the ability to prevent dovecot/lmtp from adding received
headers. This is useful if one needs to use LMTP, but does
not want additional received headers because:
headers, and causes misleading/incorrect information
The default value is true, as current behavior