Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Riley <rileyrg@gmail.com>
To: ding@gnus.org
Subject: Re: smtpmail authentication again
Date: Sat, 07 Jan 2012 06:33:11 +0100	[thread overview]
Message-ID: <yi7h14oz54.fsf@news.eternal-september.org> (raw)
In-Reply-To: <m3ty48dz66.fsf@stories.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> Ideally it would be set by a group/topic parameter and also overridden
>> at will.  It would be a logical name, which retrieves the rest of the
>> info from auth-source (defaulting to the machine name, unless a logical
>> name is also specified).
>>
>> So you'd have
>>
>> machine X port smtp ...
>> machine Y port smtp login alpha nickname alphaY
>> machine Y port smtp login beta nickname betaY
>>
>> and then setting the new group/topic parameter to "X" gives you the
>> first one, "Y" gives you alphaY because it matches first in the file,
>> "alphaY" and "betaY" give you the second and third lines respectively.
>
> I haven't thought a lot about it, but I think it would have to be more
> ... complicated.  :-)
>
> That is, I think a common use case would be to make lots of things
> change based on what identity you're using.
>
> If you're answering work email, you want to have that special
> lawyer-mandated signature, your work From address, and you have to use
> your company's outgoing SMTP server.
>
> If it's personal email, you have funny signature, and you post via
> Gmail with your Gmail From address.
>
> So I think the most natural fit here would be to just add some smtpmail
> variables to the group/topic parameters.
>
> I think.

So long as the passwords are encrypted in the authinfo.gpg....




  parent reply	other threads:[~2012-01-07  5:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17 16:06 Richard Riley
2012-01-03 22:25 ` Lars Magne Ingebrigtsen
2012-01-05  8:03   ` Kostas Zorbadelos
2012-01-05 19:00     ` Richard Riley
2012-01-05  9:29   ` Leo
2012-01-05 19:02     ` Richard Riley
2012-01-07  2:07   ` Ted Zlatanov
2012-01-07  2:16     ` Ted Zlatanov
2012-01-07  2:28       ` Lars Magne Ingebrigtsen
2012-01-07  2:43         ` Ted Zlatanov
2012-01-26 18:58           ` Lars Ingebrigtsen
2012-01-26 22:44             ` Ted Zlatanov
2012-01-27 17:59               ` Lars Ingebrigtsen
2012-01-27 19:17                 ` Ted Zlatanov
2012-01-27 18:25                   ` Lars Ingebrigtsen
2012-01-28 11:30                     ` Steinar Bang
2012-02-01 18:48                     ` Ted Zlatanov
2012-02-01 18:53                       ` Johann 'Myrkraverk' Oskarsson
2012-02-01 19:02                         ` Ted Zlatanov
2012-02-02  7:44                           ` Richard Riley
2012-01-07  5:33         ` Richard Riley [this message]
2012-01-07 13:10           ` Ted Zlatanov
2012-01-07 14:45             ` Richard Riley
2012-01-08 19:36               ` Ted Zlatanov
2012-01-10  2:34                 ` Richard Riley
2012-01-10 14:37                   ` Ted Zlatanov
2012-01-10 14:47                     ` Ted Zlatanov
2012-01-11  5:45                       ` Richard Riley
2012-01-11 13:39                         ` Ted Zlatanov
2012-01-12 23:47                           ` Richard Riley
2012-01-11 22:59                       ` Eric S Fraga
2012-01-10 16:26                     ` Richard Riley

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=yi7h14oz54.fsf@news.eternal-september.org \
    --to=rileyrg@gmail.com \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).