How do you setup system email to send to a Gmail account?
Often when I'm working on a terminal, I'll see the "you have new mail in..." message. I know I can see this mail by looking in my system's mail folder (/var/mail/
), but this is inconvenient. Also, if the message is important, such as a notice about low system resources, or drive problems, or a failed cron job, I may not see that message or check the system's mail folder for weeks or more.
How can I set it up so that all these messages get sent to a real email service, like Gmail, which I check daily?
email mail
add a comment |
Often when I'm working on a terminal, I'll see the "you have new mail in..." message. I know I can see this mail by looking in my system's mail folder (/var/mail/
), but this is inconvenient. Also, if the message is important, such as a notice about low system resources, or drive problems, or a failed cron job, I may not see that message or check the system's mail folder for weeks or more.
How can I set it up so that all these messages get sent to a real email service, like Gmail, which I check daily?
email mail
add a comment |
Often when I'm working on a terminal, I'll see the "you have new mail in..." message. I know I can see this mail by looking in my system's mail folder (/var/mail/
), but this is inconvenient. Also, if the message is important, such as a notice about low system resources, or drive problems, or a failed cron job, I may not see that message or check the system's mail folder for weeks or more.
How can I set it up so that all these messages get sent to a real email service, like Gmail, which I check daily?
email mail
Often when I'm working on a terminal, I'll see the "you have new mail in..." message. I know I can see this mail by looking in my system's mail folder (/var/mail/
), but this is inconvenient. Also, if the message is important, such as a notice about low system resources, or drive problems, or a failed cron job, I may not see that message or check the system's mail folder for weeks or more.
How can I set it up so that all these messages get sent to a real email service, like Gmail, which I check daily?
email mail
email mail
edited 6 hours ago
Pablo Bianchi
2,92521535
2,92521535
asked Aug 24 '11 at 13:26
CerinCerin
2,32084175
2,32084175
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
See this:
Users can control their own mail delivery by specifying destinations in a file called .forward in their home directories.
So, when you do this:
echo "yourmail@example.com" > ~/.forward
the mails should be forwarded to the e-mail you've specified (in this case, yourmail@example.com
)
1
But you also need to be certain that the messages will be received. most IPs from residential ISPs from which email is sent from (i.e. the sending server originates at a residential IP) get marked as spam and/or ignored by people. You may be able to make it work, but the issue is then dealing with spam.
– Thomas Ward♦
Aug 24 '11 at 14:43
1
@The Evil Phoenix: I'm not suggesting to send this mail to just some random guy out there - I have the forwarding set to my regular mail inbox, so that the mail intended for me goes somewhere where I'll see it (I did whitelist the equivalent ofuser@mybox.example.net
, but that's about it). On a side note, SMTP is a best-effort protocol - you can never be completely certain the messages will be delivered.
– Piskvor
Aug 24 '11 at 14:56
1
@The Evil One, This is my problem, as I get my internet through Comcast or Verizon. So getting sendmail to send email is easy. Getting sendmail to send email and get it to reach the recipient is hard, because both Comcast and Verizon block outgoing email sent without authorization.
– Cerin
Sep 30 '11 at 18:32
On system's I've confirmed have working sendmail, adding ~/.forward doesn't seem to have any effect.
– Cerin
Oct 15 '11 at 14:54
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f58480%2fhow-do-you-setup-system-email-to-send-to-a-gmail-account%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
See this:
Users can control their own mail delivery by specifying destinations in a file called .forward in their home directories.
So, when you do this:
echo "yourmail@example.com" > ~/.forward
the mails should be forwarded to the e-mail you've specified (in this case, yourmail@example.com
)
1
But you also need to be certain that the messages will be received. most IPs from residential ISPs from which email is sent from (i.e. the sending server originates at a residential IP) get marked as spam and/or ignored by people. You may be able to make it work, but the issue is then dealing with spam.
– Thomas Ward♦
Aug 24 '11 at 14:43
1
@The Evil Phoenix: I'm not suggesting to send this mail to just some random guy out there - I have the forwarding set to my regular mail inbox, so that the mail intended for me goes somewhere where I'll see it (I did whitelist the equivalent ofuser@mybox.example.net
, but that's about it). On a side note, SMTP is a best-effort protocol - you can never be completely certain the messages will be delivered.
– Piskvor
Aug 24 '11 at 14:56
1
@The Evil One, This is my problem, as I get my internet through Comcast or Verizon. So getting sendmail to send email is easy. Getting sendmail to send email and get it to reach the recipient is hard, because both Comcast and Verizon block outgoing email sent without authorization.
– Cerin
Sep 30 '11 at 18:32
On system's I've confirmed have working sendmail, adding ~/.forward doesn't seem to have any effect.
– Cerin
Oct 15 '11 at 14:54
add a comment |
See this:
Users can control their own mail delivery by specifying destinations in a file called .forward in their home directories.
So, when you do this:
echo "yourmail@example.com" > ~/.forward
the mails should be forwarded to the e-mail you've specified (in this case, yourmail@example.com
)
1
But you also need to be certain that the messages will be received. most IPs from residential ISPs from which email is sent from (i.e. the sending server originates at a residential IP) get marked as spam and/or ignored by people. You may be able to make it work, but the issue is then dealing with spam.
– Thomas Ward♦
Aug 24 '11 at 14:43
1
@The Evil Phoenix: I'm not suggesting to send this mail to just some random guy out there - I have the forwarding set to my regular mail inbox, so that the mail intended for me goes somewhere where I'll see it (I did whitelist the equivalent ofuser@mybox.example.net
, but that's about it). On a side note, SMTP is a best-effort protocol - you can never be completely certain the messages will be delivered.
– Piskvor
Aug 24 '11 at 14:56
1
@The Evil One, This is my problem, as I get my internet through Comcast or Verizon. So getting sendmail to send email is easy. Getting sendmail to send email and get it to reach the recipient is hard, because both Comcast and Verizon block outgoing email sent without authorization.
– Cerin
Sep 30 '11 at 18:32
On system's I've confirmed have working sendmail, adding ~/.forward doesn't seem to have any effect.
– Cerin
Oct 15 '11 at 14:54
add a comment |
See this:
Users can control their own mail delivery by specifying destinations in a file called .forward in their home directories.
So, when you do this:
echo "yourmail@example.com" > ~/.forward
the mails should be forwarded to the e-mail you've specified (in this case, yourmail@example.com
)
See this:
Users can control their own mail delivery by specifying destinations in a file called .forward in their home directories.
So, when you do this:
echo "yourmail@example.com" > ~/.forward
the mails should be forwarded to the e-mail you've specified (in this case, yourmail@example.com
)
answered Aug 24 '11 at 14:01
PiskvorPiskvor
1,1121119
1,1121119
1
But you also need to be certain that the messages will be received. most IPs from residential ISPs from which email is sent from (i.e. the sending server originates at a residential IP) get marked as spam and/or ignored by people. You may be able to make it work, but the issue is then dealing with spam.
– Thomas Ward♦
Aug 24 '11 at 14:43
1
@The Evil Phoenix: I'm not suggesting to send this mail to just some random guy out there - I have the forwarding set to my regular mail inbox, so that the mail intended for me goes somewhere where I'll see it (I did whitelist the equivalent ofuser@mybox.example.net
, but that's about it). On a side note, SMTP is a best-effort protocol - you can never be completely certain the messages will be delivered.
– Piskvor
Aug 24 '11 at 14:56
1
@The Evil One, This is my problem, as I get my internet through Comcast or Verizon. So getting sendmail to send email is easy. Getting sendmail to send email and get it to reach the recipient is hard, because both Comcast and Verizon block outgoing email sent without authorization.
– Cerin
Sep 30 '11 at 18:32
On system's I've confirmed have working sendmail, adding ~/.forward doesn't seem to have any effect.
– Cerin
Oct 15 '11 at 14:54
add a comment |
1
But you also need to be certain that the messages will be received. most IPs from residential ISPs from which email is sent from (i.e. the sending server originates at a residential IP) get marked as spam and/or ignored by people. You may be able to make it work, but the issue is then dealing with spam.
– Thomas Ward♦
Aug 24 '11 at 14:43
1
@The Evil Phoenix: I'm not suggesting to send this mail to just some random guy out there - I have the forwarding set to my regular mail inbox, so that the mail intended for me goes somewhere where I'll see it (I did whitelist the equivalent ofuser@mybox.example.net
, but that's about it). On a side note, SMTP is a best-effort protocol - you can never be completely certain the messages will be delivered.
– Piskvor
Aug 24 '11 at 14:56
1
@The Evil One, This is my problem, as I get my internet through Comcast or Verizon. So getting sendmail to send email is easy. Getting sendmail to send email and get it to reach the recipient is hard, because both Comcast and Verizon block outgoing email sent without authorization.
– Cerin
Sep 30 '11 at 18:32
On system's I've confirmed have working sendmail, adding ~/.forward doesn't seem to have any effect.
– Cerin
Oct 15 '11 at 14:54
1
1
But you also need to be certain that the messages will be received. most IPs from residential ISPs from which email is sent from (i.e. the sending server originates at a residential IP) get marked as spam and/or ignored by people. You may be able to make it work, but the issue is then dealing with spam.
– Thomas Ward♦
Aug 24 '11 at 14:43
But you also need to be certain that the messages will be received. most IPs from residential ISPs from which email is sent from (i.e. the sending server originates at a residential IP) get marked as spam and/or ignored by people. You may be able to make it work, but the issue is then dealing with spam.
– Thomas Ward♦
Aug 24 '11 at 14:43
1
1
@The Evil Phoenix: I'm not suggesting to send this mail to just some random guy out there - I have the forwarding set to my regular mail inbox, so that the mail intended for me goes somewhere where I'll see it (I did whitelist the equivalent of
user@mybox.example.net
, but that's about it). On a side note, SMTP is a best-effort protocol - you can never be completely certain the messages will be delivered.– Piskvor
Aug 24 '11 at 14:56
@The Evil Phoenix: I'm not suggesting to send this mail to just some random guy out there - I have the forwarding set to my regular mail inbox, so that the mail intended for me goes somewhere where I'll see it (I did whitelist the equivalent of
user@mybox.example.net
, but that's about it). On a side note, SMTP is a best-effort protocol - you can never be completely certain the messages will be delivered.– Piskvor
Aug 24 '11 at 14:56
1
1
@The Evil One, This is my problem, as I get my internet through Comcast or Verizon. So getting sendmail to send email is easy. Getting sendmail to send email and get it to reach the recipient is hard, because both Comcast and Verizon block outgoing email sent without authorization.
– Cerin
Sep 30 '11 at 18:32
@The Evil One, This is my problem, as I get my internet through Comcast or Verizon. So getting sendmail to send email is easy. Getting sendmail to send email and get it to reach the recipient is hard, because both Comcast and Verizon block outgoing email sent without authorization.
– Cerin
Sep 30 '11 at 18:32
On system's I've confirmed have working sendmail, adding ~/.forward doesn't seem to have any effect.
– Cerin
Oct 15 '11 at 14:54
On system's I've confirmed have working sendmail, adding ~/.forward doesn't seem to have any effect.
– Cerin
Oct 15 '11 at 14:54
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f58480%2fhow-do-you-setup-system-email-to-send-to-a-gmail-account%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