From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] public mail server for ELOG?
Date: Wed, 28 Oct 2009 21:45:44 +0000 [thread overview]
Message-ID: <200910282145.45967.michaelkintzios@gmail.com> (raw)
In-Reply-To: <49bf44f10910281422n721c811cqbe099bfc228ea7de@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 2140 bytes --]
On Wednesday 28 October 2009 21:22:44 Grant wrote:
> >> >> > That kind of delivery limits the access to this mails to the local
> >> >> > maschine. If I want to read local I don't need mails, I could just
> >> >> > read the logfiles from portage in /var/log/
> >> >> >
> >> >> > But I am aware that solving this problem is nothing that portage
> >> >> > has to do, as it is no problem with portage at all.
> >> >> >
> >> >> > My mail was just to show that not everyone has a local mailserver
> >> >> > running on his maschine.
> >> >> >
> >> >> > Greetings
> >> >> >
> >> >> > Sebastian
> >> >>
> >> >> then let it store everything as elog and read that with elogv.
> >> >>
> >> >> mail is just an additional bonus feature.
> >> >
> >> > His initial mail said that he would like a copy of elogs to go to his
> >> > inbox at his ISP. Later mails imply he might want to read them over
> >> > IMAP so they are accessible at multiple locations.
> >> >
> >> > Sebastian,
> >> >
> >> > Have you looked at ssmtp? Very light, very small and you can protect
> >> > your login password with Unix file permissions instead of leaving them
> >> > open in make.conf
> >>
> >> Could I use ssmtp to send elog mail to my email address? I wouldn't
> >> even need a login password if this is all I use it for, right?
> >
> > Yes.
> >
> > ssmtp is an email sender, it knows how to talk smtp to receiving servers
> > or to relays. It doesn't receive mails.
> >
> > If the relay you use requires a username/password or ssl, it supports
> > that too.
>
> So I need a relay somewhere along with ssmtp to get a message to an
> email address?
>
> > [The receiving smtp server likely does not require a username/password,
> > but it is equally likely to not accept connection direct from you, hence
> > you should use your ISPs mail relay]
>
> I likely can't use my ISP's mail relay when traveling, right?
You should be able to, if they offer smtp_auth. Ideally over SSL/TLS so that
you don't send username/passwd in the clear. Most ISPs these days provide
this service as standard.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-10-28 21:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 16:36 [gentoo-user] public mail server for ELOG? Grant
2009-10-28 16:47 ` Volker Armin Hemmann
2009-10-28 17:35 ` Sebastian Beßler
2009-10-28 17:59 ` Alan McKinnon
2009-10-28 18:34 ` Sebastian Beßler
2009-10-28 18:44 ` Volker Armin Hemmann
2009-10-28 18:57 ` Alan McKinnon
2009-10-28 19:11 ` Sebastian Beßler
2009-10-28 19:27 ` Grant
2009-10-28 19:33 ` Alan McKinnon
2009-10-28 21:22 ` Grant
2009-10-28 21:45 ` Mick [this message]
2009-10-28 21:50 ` Keith Dart
2009-10-28 23:48 ` Alan McKinnon
2009-10-29 15:54 ` Albert Hopkins
2009-10-29 15:37 ` [gentoo-user] " Harry Putnam
2009-10-29 15:48 ` [gentoo-user] " Joshua Murphy
2009-10-28 22:23 ` Albert Hopkins
2009-10-29 11:50 ` Stroller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200910282145.45967.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox