Postfix smtp_connection_cache_destinations / scache / Connection Cache
up vote
0
down vote
favorite
I'm currently running postfix v2.11 and I'm trying to setup connection caching to specific destination, in my case it is telenet.be so that it uses resources efficiently of sending more emails in opened connection and saves resources instead of opening conneciton / sending the email / closing the connection after every email.
I've read the docs http://www.postfix.org/CONNECTION_CACHE_README.html but maybe I am missing or misinterpreting something.
OP question: how to correctly setup connection caching per destination?
On what conditions it is activated as it says scache is enabled by default?
main.cf
transport_maps = hash:/etc/postfix/transport_telenet
smtp_connection_cache_destinations = telenet.be
smtp_connection_cache_on_demand = yes
smtp_connection_cache_time_limit = 30s
connection_cache_status_update_time = 30s
master.cf
telenet unix - - n - 5 smtp
-o telenet_initial_destination_concurrency=5
-o smtp_connection_cache_on_demand=yes
I am not seeing it using it, or it is missing IT!
logs
/scache[3133]: statistics: start interval Nov 20 15:23:26
/scache[3133]: statistics: domain lookup hits=0 miss=187 success=0%
/scache[3133]: statistics: start interval Nov 20 15:23:56
/scache[3133]: statistics: domain lookup hits=0 miss=199 success=0%
/scache[3133]: statistics: start interval Nov 20 15:24:26
/scache[3133]: statistics: domain lookup hits=0 miss=196 success=0%
qshape
T 5 10 20 40 80 160 320 640 1280 1280+
TOTAL 6636 0 0 0 0 32 3804 2800 0 0 0
telenet.be 6636 0 0 0 0 32 3804 2800 0 0 0
caching connection-pooling postfix-mta persistent-connection
asked Nov 20 at 13:38
Arnoldas
1012
add a comment |
up vote
0
down vote
favorite
I'm currently running postfix v2.11 and I'm trying to setup connection caching to specific destination, in my case it is telenet.be so that it uses resources efficiently of sending more emails in opened connection and saves resources instead of opening conneciton / sending the email / closing the connection after every email.
I've read the docs http://www.postfix.org/CONNECTION_CACHE_README.html but maybe I am missing or misinterpreting something.
OP question: how to correctly setup connection caching per destination?
On what conditions it is activated as it says scache is enabled by default?
main.cf
transport_maps = hash:/etc/postfix/transport_telenet
smtp_connection_cache_destinations = telenet.be
smtp_connection_cache_on_demand = yes
smtp_connection_cache_time_limit = 30s
connection_cache_status_update_time = 30s
master.cf
telenet unix - - n - 5 smtp
-o telenet_initial_destination_concurrency=5
-o smtp_connection_cache_on_demand=yes
I am not seeing it using it, or it is missing IT!
logs
/scache[3133]: statistics: start interval Nov 20 15:23:26
/scache[3133]: statistics: domain lookup hits=0 miss=187 success=0%
/scache[3133]: statistics: start interval Nov 20 15:23:56
/scache[3133]: statistics: domain lookup hits=0 miss=199 success=0%
/scache[3133]: statistics: start interval Nov 20 15:24:26
/scache[3133]: statistics: domain lookup hits=0 miss=196 success=0%
qshape
T 5 10 20 40 80 160 320 640 1280 1280+
TOTAL 6636 0 0 0 0 32 3804 2800 0 0 0
telenet.be 6636 0 0 0 0 32 3804 2800 0 0 0
caching connection-pooling postfix-mta persistent-connection
asked Nov 20 at 13:38
Arnoldas
1012
I'll need to investigate this next week with the newer version of postfix as this most likely hides under STARTTLS With Postfix versions < 3.4, the Postfix shared connection cache cannot be used with TLS. Historically, the Postfix SMTP client has supported multiple deliveries per plaintext connection. Postfix 3.4 introduces support for multiple deliveries per TLS-encrypted connection.
– Arnoldas
Nov 22 at 15:04
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm currently running postfix v2.11 and I'm trying to setup connection caching to specific destination, in my case it is telenet.be so that it uses resources efficiently of sending more emails in opened connection and saves resources instead of opening conneciton / sending the email / closing the connection after every email.
I've read the docs http://www.postfix.org/CONNECTION_CACHE_README.html but maybe I am missing or misinterpreting something.
OP question: how to correctly setup connection caching per destination?
On what conditions it is activated as it says scache is enabled by default?
main.cf
transport_maps = hash:/etc/postfix/transport_telenet
smtp_connection_cache_destinations = telenet.be
smtp_connection_cache_on_demand = yes
smtp_connection_cache_time_limit = 30s
connection_cache_status_update_time = 30s
master.cf
telenet unix - - n - 5 smtp
-o telenet_initial_destination_concurrency=5
-o smtp_connection_cache_on_demand=yes
I am not seeing it using it, or it is missing IT!
logs
/scache[3133]: statistics: start interval Nov 20 15:23:26
/scache[3133]: statistics: domain lookup hits=0 miss=187 success=0%
/scache[3133]: statistics: start interval Nov 20 15:23:56
/scache[3133]: statistics: domain lookup hits=0 miss=199 success=0%
/scache[3133]: statistics: start interval Nov 20 15:24:26
/scache[3133]: statistics: domain lookup hits=0 miss=196 success=0%
qshape
T 5 10 20 40 80 160 320 640 1280 1280+
TOTAL 6636 0 0 0 0 32 3804 2800 0 0 0
telenet.be 6636 0 0 0 0 32 3804 2800 0 0 0
caching connection-pooling postfix-mta persistent-connection
asked Nov 20 at 13:38
Arnoldas
1012
I'm currently running postfix v2.11 and I'm trying to setup connection caching to specific destination, in my case it is telenet.be so that it uses resources efficiently of sending more emails in opened connection and saves resources instead of opening conneciton / sending the email / closing the connection after every email.
I've read the docs http://www.postfix.org/CONNECTION_CACHE_README.html but maybe I am missing or misinterpreting something.
OP question: how to correctly setup connection caching per destination?
On what conditions it is activated as it says scache is enabled by default?
main.cf
transport_maps = hash:/etc/postfix/transport_telenet
smtp_connection_cache_destinations = telenet.be
smtp_connection_cache_on_demand = yes
smtp_connection_cache_time_limit = 30s
connection_cache_status_update_time = 30s
master.cf
telenet unix - - n - 5 smtp
-o telenet_initial_destination_concurrency=5
-o smtp_connection_cache_on_demand=yes
I am not seeing it using it, or it is missing IT!
logs
/scache[3133]: statistics: start interval Nov 20 15:23:26
/scache[3133]: statistics: domain lookup hits=0 miss=187 success=0%
/scache[3133]: statistics: start interval Nov 20 15:23:56
/scache[3133]: statistics: domain lookup hits=0 miss=199 success=0%
/scache[3133]: statistics: start interval Nov 20 15:24:26
/scache[3133]: statistics: domain lookup hits=0 miss=196 success=0%
qshape
T 5 10 20 40 80 160 320 640 1280 1280+
TOTAL 6636 0 0 0 0 32 3804 2800 0 0 0
telenet.be 6636 0 0 0 0 32 3804 2800 0 0 0
caching connection-pooling postfix-mta persistent-connection
caching connection-pooling postfix-mta persistent-connection
asked Nov 20 at 13:38
Arnoldas
1012
asked Nov 20 at 13:38
Arnoldas
1012
asked Nov 20 at 13:38
Arnoldas
1012
asked Nov 20 at 13:38
Arnoldas
1012
asked Nov 20 at 13:38
Arnoldas
1012
1012
I'll need to investigate this next week with the newer version of postfix as this most likely hides under STARTTLS With Postfix versions < 3.4, the Postfix shared connection cache cannot be used with TLS. Historically, the Postfix SMTP client has supported multiple deliveries per plaintext connection. Postfix 3.4 introduces support for multiple deliveries per TLS-encrypted connection.
– Arnoldas
Nov 22 at 15:04
add a comment |
I'll need to investigate this next week with the newer version of postfix as this most likely hides under STARTTLS With Postfix versions < 3.4, the Postfix shared connection cache cannot be used with TLS. Historically, the Postfix SMTP client has supported multiple deliveries per plaintext connection. Postfix 3.4 introduces support for multiple deliveries per TLS-encrypted connection.
– Arnoldas
Nov 22 at 15:04
I'll need to investigate this next week with the newer version of postfix as this most likely hides under STARTTLS With Postfix versions < 3.4, the Postfix shared connection cache cannot be used with TLS. Historically, the Postfix SMTP client has supported multiple deliveries per plaintext connection. Postfix 3.4 introduces support for multiple deliveries per TLS-encrypted connection.
– Arnoldas
Nov 22 at 15:04
I'll need to investigate this next week with the newer version of postfix as this most likely hides under STARTTLS With Postfix versions < 3.4, the Postfix shared connection cache cannot be used with TLS. Historically, the Postfix SMTP client has supported multiple deliveries per plaintext connection. Postfix 3.4 introduces support for multiple deliveries per TLS-encrypted connection.
– Arnoldas
Nov 22 at 15:04
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53394299%2fpostfix-smtp-connection-cache-destinations-scache-connection-cache%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53394299%2fpostfix-smtp-connection-cache-destinations-scache-connection-cache%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I'll need to investigate this next week with the newer version of postfix as this most likely hides under STARTTLS With Postfix versions < 3.4, the Postfix shared connection cache cannot be used with TLS. Historically, the Postfix SMTP client has supported multiple deliveries per plaintext connection. Postfix 3.4 introduces support for multiple deliveries per TLS-encrypted connection.
– Arnoldas
Nov 22 at 15:04