Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Riley <rileyrg@googlemail.com>
To: Philipp Haselwarter <philipp.haselwarter@gmx.de>
Cc: ding@gnus.org
Subject: Re: smtp credential, multiple smtp, posting styles and smtpmail
Date: Fri, 11 Feb 2011 00:45:53 +0100	[thread overview]
Message-ID: <8j7hd7fo7i.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87aai31nrs.fsf@netarch.haselwarter.org> (Philipp Haselwarter's message of "Fri, 11 Feb 2011 00:19:03 +0100")

Philipp Haselwarter <philipp.haselwarter@gmx.de> writes:

> "RR" == Richard Riley <rileyrg@googlemail.com> writes:
>
> RR> Philipp Haselwarter <philipp.haselwarter@gmx.de> writes:
>
> ---8<---[snipped 51 lines: my config]---8<---
>
> RR> Yes, this is similar but superior to what I posted yesterday and
> RR> uses a switch to change the smtp server at message send time based
> RR> on the address which in turn is set in the gnus posting style. It
> RR> was this posting that got me thinking that I ought to be able to set
> RR> all I need in the posting style and not need to call the change smtp
> RR> function or equivalent.
>
> RR> Since I cant see your .authinfo.gpg, I am assuming it contains names
> RR> where the machine names match the second element in the smtp list
> RR> elements? This is certainly cleaner than using msmtp and so I'll
> RR> give it a go - thanks! Its certainly more comprehensive with the
> RR> auth mechs being checked,
>
> err.. the inline authinfo.gpg is a cleartext ascii example corresponding
> to the smtp portion in my .authinfo.gpg, K i should show it :)

Yes, I understand what it is - we discussed it before - but something
was attached to the original post which wouldnt open here (authinfo.gpg)
in my gnus ... dont know why. The ways of mime attachments are many
... . The reason I asked was that it wasnt clear to me what was being
matched : to be honest I still am not sure how authinfo works - its
pretty convoluted - but I do have it working now with the smtp-account
matching - thanks for that - but only after I used "from" in my posting
style and not "address". "works for me" ;)

It now means I dont need to use msmtp so this is great!


> The approach I'm using has the advantage, that you never have to worry
> if all the parameters are set correctly, as it just auto-adjusts.
> If you choose a semi-static setup with posting styles (supposing that
> would work), you'd sort of have to stick with that account for the
> group. I can simply add the From: and get everything taken care of.



  reply	other threads:[~2011-02-10 23:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10  9:03 Richard Riley
2011-02-10  9:20 ` Julien Danjou
2011-02-10  9:36   ` Richard Riley
2011-02-10 11:33     ` Philipp Haselwarter
2011-02-10 11:58       ` Richard Riley
2011-02-10 23:19         ` Philipp Haselwarter
2011-02-10 23:45           ` Richard Riley [this message]
2011-02-11 14:06             ` Ted Zlatanov
2011-02-10 23:15       ` Richard Riley
     [not found]   ` <ygfd3n0nrpj.fsf_-_@vserv.viteno.net>
     [not found]     ` <87y65ouqa5.fsf@keller.adm.naquadah.org>
2011-02-10 11:21       ` Your public key Norbert Koch
2011-02-14  2:20 ` smtp credential, multiple smtp, posting styles and smtpmail Lars Ingebrigtsen

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=8j7hd7fo7i.fsf@news.eternal-september.org \
    --to=rileyrg@googlemail.com \
    --cc=ding@gnus.org \
    --cc=philipp.haselwarter@gmx.de \
    /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).