Resolve email delivery issue on “From and EnvelopeFrom 2nd level mail domains are different”. Is this a...
We send email from our main domain "vocalsound.org". It is delivered through our hosting provider, which however sends it through a shared mailserver hosted on their generic domain (webland.ch).
This is getting to be a problem, since "From and EnvelopeFrom 2nd level mail domains are different", as for example SpamAssasin notes:
Some recipents such as gmail do not have a problem with this, they will simply mark the mail with a "sent through" / "via" note, such as: "someone@vocalsound.org via webland.ch".
Other mail servers (such as: laposte.net, free.fr, register.it) however will flag the email as SPAM, independently of its content, or even refuse to connect: "560 5.7.1 Service Service refused. LPN007_510". Or in some cases, they even pretend to deliver the email (the smtp connection is successful) but the email will never reach its intended recipient, not even as spam.
This is a huge problem not only for newsletters, but even for our daily correspondence: in order to keep in touch with some contacts, we had to open a gmail account because otherwise they will not receive our email.
Some years ago, we had our hosting at another provider, but never encountered this issue, since our mails resulted to be sent directly from our domain.
My questions:
1) Can this be considered a "bad practice" or even "misconfiguration" by our hosting provider, or is this usual practice on shared hosting?
2) To resolve the issue, should we consider changing hosting provider?
email smtp hosting shared-hosting
asked Jan 21 at 14:13
1NN1NN
789
add a comment |
We send email from our main domain "vocalsound.org". It is delivered through our hosting provider, which however sends it through a shared mailserver hosted on their generic domain (webland.ch).
This is getting to be a problem, since "From and EnvelopeFrom 2nd level mail domains are different", as for example SpamAssasin notes:
Some recipents such as gmail do not have a problem with this, they will simply mark the mail with a "sent through" / "via" note, such as: "someone@vocalsound.org via webland.ch".
Other mail servers (such as: laposte.net, free.fr, register.it) however will flag the email as SPAM, independently of its content, or even refuse to connect: "560 5.7.1 Service Service refused. LPN007_510". Or in some cases, they even pretend to deliver the email (the smtp connection is successful) but the email will never reach its intended recipient, not even as spam.
This is a huge problem not only for newsletters, but even for our daily correspondence: in order to keep in touch with some contacts, we had to open a gmail account because otherwise they will not receive our email.
Some years ago, we had our hosting at another provider, but never encountered this issue, since our mails resulted to be sent directly from our domain.
My questions:
1) Can this be considered a "bad practice" or even "misconfiguration" by our hosting provider, or is this usual practice on shared hosting?
2) To resolve the issue, should we consider changing hosting provider?
email smtp hosting shared-hosting
asked Jan 21 at 14:13
1NN1NN
789
Consider setting up your own mail server on vocalsound.org
– Moab
Jan 21 at 14:15
The total SpamAssasin score is low enough for this not to be considered serious. For analysis, we need to have the headers of such an email.
– harrymc
Jan 21 at 14:45
add a comment |
We send email from our main domain "vocalsound.org". It is delivered through our hosting provider, which however sends it through a shared mailserver hosted on their generic domain (webland.ch).
This is getting to be a problem, since "From and EnvelopeFrom 2nd level mail domains are different", as for example SpamAssasin notes:
Some recipents such as gmail do not have a problem with this, they will simply mark the mail with a "sent through" / "via" note, such as: "someone@vocalsound.org via webland.ch".
Other mail servers (such as: laposte.net, free.fr, register.it) however will flag the email as SPAM, independently of its content, or even refuse to connect: "560 5.7.1 Service Service refused. LPN007_510". Or in some cases, they even pretend to deliver the email (the smtp connection is successful) but the email will never reach its intended recipient, not even as spam.
This is a huge problem not only for newsletters, but even for our daily correspondence: in order to keep in touch with some contacts, we had to open a gmail account because otherwise they will not receive our email.
Some years ago, we had our hosting at another provider, but never encountered this issue, since our mails resulted to be sent directly from our domain.
My questions:
1) Can this be considered a "bad practice" or even "misconfiguration" by our hosting provider, or is this usual practice on shared hosting?
2) To resolve the issue, should we consider changing hosting provider?
email smtp hosting shared-hosting
asked Jan 21 at 14:13
1NN1NN
789
We send email from our main domain "vocalsound.org". It is delivered through our hosting provider, which however sends it through a shared mailserver hosted on their generic domain (webland.ch).
This is getting to be a problem, since "From and EnvelopeFrom 2nd level mail domains are different", as for example SpamAssasin notes:
Some recipents such as gmail do not have a problem with this, they will simply mark the mail with a "sent through" / "via" note, such as: "someone@vocalsound.org via webland.ch".
Other mail servers (such as: laposte.net, free.fr, register.it) however will flag the email as SPAM, independently of its content, or even refuse to connect: "560 5.7.1 Service Service refused. LPN007_510". Or in some cases, they even pretend to deliver the email (the smtp connection is successful) but the email will never reach its intended recipient, not even as spam.
This is a huge problem not only for newsletters, but even for our daily correspondence: in order to keep in touch with some contacts, we had to open a gmail account because otherwise they will not receive our email.
Some years ago, we had our hosting at another provider, but never encountered this issue, since our mails resulted to be sent directly from our domain.
My questions:
1) Can this be considered a "bad practice" or even "misconfiguration" by our hosting provider, or is this usual practice on shared hosting?
2) To resolve the issue, should we consider changing hosting provider?
email smtp hosting shared-hosting
email smtp hosting shared-hosting
asked Jan 21 at 14:13
1NN1NN
789
asked Jan 21 at 14:13
1NN1NN
789
asked Jan 21 at 14:13
1NN1NN
789
asked Jan 21 at 14:13
1NN1NN
789
asked Jan 21 at 14:13
1NN1NN
789
789
Consider setting up your own mail server on vocalsound.org
– Moab
Jan 21 at 14:15
The total SpamAssasin score is low enough for this not to be considered serious. For analysis, we need to have the headers of such an email.
– harrymc
Jan 21 at 14:45
add a comment |
Consider setting up your own mail server on vocalsound.org
– Moab
Jan 21 at 14:15
The total SpamAssasin score is low enough for this not to be considered serious. For analysis, we need to have the headers of such an email.
– harrymc
Jan 21 at 14:45
Consider setting up your own mail server on vocalsound.org
– Moab
Jan 21 at 14:15
Consider setting up your own mail server on vocalsound.org
– Moab
Jan 21 at 14:15
The total SpamAssasin score is low enough for this not to be considered serious. For analysis, we need to have the headers of such an email.
– harrymc
Jan 21 at 14:45
The total SpamAssasin score is low enough for this not to be considered serious. For analysis, we need to have the headers of such an email.
– harrymc
Jan 21 at 14:45
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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',
autoActivateHeartbeat: false,
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%2fsuperuser.com%2fquestions%2f1396635%2fresolve-email-delivery-issue-on-from-and-envelopefrom-2nd-level-mail-domains-ar%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1396635%2fresolve-email-delivery-issue-on-from-and-envelopefrom-2nd-level-mail-domains-ar%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
Consider setting up your own mail server on vocalsound.org
– Moab
Jan 21 at 14:15
The total SpamAssasin score is low enough for this not to be considered serious. For analysis, we need to have the headers of such an email.
– harrymc
Jan 21 at 14:45