Re: slrn: reply on Mac
andrew
> how may I configure slrn best in order to permit a reply to a posting?
Unfortunately I don't have a Mac but I believe that my personal setup of
Mutt and msmtp is also available for Mac?
Andrew
--
Do you think that's air you're breathing?
Patrick Lamaizière
> Or maybe there's a simple walkthrough how to change the postfix setup?
On leopard it's easy, postfix is already installed:
http://www.freshblurbs.com/how-enable-local-smtp-postfix-os-x-leopard
(I always use a local postfix to handle mails.)
Justin C
> Hi,
>
> how may I configure slrn best in order to permit a reply to a posting?
>
I'm using slrn on OS X 10.5.8 replying works. Let me look at my .slrnrc
file.... All the lines referencing mail are commented out so mine is
using using the standard sendmail commands and it's working.
Looking at /etc/postfix/main.cf it doesn't look like I've customised
anything there either. It appears to 'just work' ... however, it didn't
used to. Maybe one of the software updates fixed it, I couldn't say.
As an aside, TextMate makes a good text editor for news posts, and, if
you haven't done so already, Safari (and probably Firefox or [insert
browser name here]) can be be called to follow URLs in posts. I didn't
expect this stuff to work, but it does, so I'm happy.
Sorry I can't tell you what I've done to make mine work, but if you want
more info about my setup let me know and I'm happy to try and help.
Justin.
--
Justin C, by the sea.
Whiskers
> Hi,
>
> how may I configure slrn best in order to permit a reply to a posting?
>
> No, I do not mean a follow-up, but an actual reply.
>
> installed and I do not have an actual mail server around, just smtp,
> pop, imap.
[...]
I have msmtp set up on my Linux system; getting it to work with slrn wasn't
entirely plain sailing, but it does seem to work - if you get the email
copy of this article, then it works :))
--
-- ^^^^^^^^^^
-- Whiskers
-- ~~~~~~~~~~
Whiskers
> On Tue, 24 Nov 2009 23:14:26 +0000, Justin C wrote:
[...]
> Yeah, for any reason postfix already does know my usual email provider.
> It could work for many installations. Probably it's due to my provider's
> policy with smtp after pop (I just said it wrong the other way) is not
> known to postfix.
[...]
I don't know about gmx.de, but the 'international' gmx.com free webmail
service includes POP, IMAP, and SMTP (the webmail interface is horrid,
relying too much on javascript and sending 'multipart' emails with an
empty text/plain part and the message only in the text/html part and
lacking a plain text only option, but the conventional servers all seem to
be pretty reliable for light use). If you can sign up for that, or some
other free service that includes SMTP, that could be a practical solution.
(It's a good idea not to use your normal email address with newsgroups or
other public forums).
Christian Ebert
> Thanks, postfix itself does work properly here. However, my provider
> does expect pop after smtp
I guess you mean smtp after pop? If yes, that's not supported by
postfix without a lot of contortions which I've never been able
to get to work. Google for "postfix smtp after pop".
While I used a provider with smtp after pop authentication (not
very secure) I resorted to a fetchmail postconnect script, meaning
I polled for new mail and then sent - I guess that's what
Thunderbird and the likes do under the hood.
> and thus delivery always fails. I doubt
> whether postfix would be able to do a pop after smtp, especially since I
> do not want it to fetch the mail, since this is done via the usual mail
> application (Thunderbird).
>
> That's why I wonder how I could tell slrn to use a different mail
> program - always a question more related to Thunderbird, Apple Mail,
> postfix, sendmail etc., but maybe another slrn user figured out the
> solution already.
I use mutt, extremely easy to integrate with slrn; you might be
able to do something with AppleScript and Apple Mail, but I'm too
lazy to look into it ;-)
c
--
Was hei�t hier Dogma, ich bin Underdogma!
[ What the hell do you mean dogma, I am underdogma. ]
_F R E E_ _V I D E O S_ --->>> http://www.blacktrash.org/underdogma/
Christian Ebert
> Thanks, postfix itself does work properly here. However, my provider
Forgot to ask: why don't you use gmx? mail.gmx.net as relayhost
works fine with password auth here.
c
--
_B A U S T E L L E N_ lesen! --->> http://www.blacktrash.org/baustellen/
Patrick Lamaizière
> Thanks again for all help here. Any further ideas how postfix would
> have to be configured?
Something like :
main.cf
# INTERNET OR INTRANET
relayhost = [smtp_server]:port_number
# SASL smtp client
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/usr/local/etc/postfix/sasl_passwd
smtp_sasl_mechanism_filter = !gssapi, !external, static:all
(adjust the path, I use FreeBSD)
Put your username and password in the sasl_passwd file
[smtp_server]:port_number username:password
You will find more help in a postfix or mail newsgroup.
See also http://www.postfix.org/SASL_README.html
"Enabling SASL authentication in the Postfix SMTP client"
Michael Grimm
> I don't know about "SSL over SMTP" (SSMTP) on Port 465
> vs. StartTLS on Port 25 yet.
[...]
> Any further ideas how postfix would
> have to be configured?
Well it'been some time that I set this up, but may be it'll guide you to
get your configuration done (starting Leopard, now Snow Leopard).
1) I'm using SSL over SMTP on port 465
become admin (su - admin) for the following:
2) /etc/aliases
root: your-local-user-name
3) /etc/postfix/main.cf
# (added)
myorigin = your-domain.tld
relayhost = your-providers-mail-server.tld:465
smtp_enforce_tls = yes
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/smtp_sasl_passwords
smtp_sasl_security_options =
smtp_sasl_tls_security_options =
smtp_sasl_tls_verified_security_options =
# optional if you wan to see what's going on with the TLS negotiation in
# /var/log/mail.log
# smtp_tls_loglevel = 2
smtp_tls_CAfile = /System/Library/OpenSSL/certs/cert.pem
smtp_tls_per_site = hash:/etc/postfix/smtp_tls_sites
smtp_use_tls = yes
tls_random_source = dev:/dev/urandom
# (end)
4) import your mail provider's CERT key into your keychain access list (login part)
5) /System/Library/OpenSSL/certs/cert.pem (create)
sudo touch /System/Library/OpenSSL/certs/cert.pem
sudo chmod 666 /System/Library/OpenSSL/certs/cert.pem
sudo security find-certificate -a -p \
/System/Library/Keychains/SystemRootCertificates.keychain > \
/System/Library/OpenSSL/certs/cert.pem
sudo chmod 644 /System/Library/OpenSSL/certs/cert.pem
6) /etc/postfix/smtp_sasl_passwords (600 root:wheel)
your-providers-mail-server.tld your-remote-user-name:your-secret-password
7) /etc/postfix/smtp_tls_sites (644 root:wheel)
your-providers-mail-server.tld MUST_NOPEERMATCH
,----[ forgotten link I used for configuration ]-
| The MUST_NOPEERMATCH in the smtp_tls_sites file ignores certificate
| mismatches when negotiating TLS. This, overall, is not a good idea, but
| I didn't have time to play with it yet and configure the CA. Other
| options are NONE, MAY, and MUST, but some will require configuration of
| the CA so that a trust can be established with the server. This, I
| believe, is configured with smtp_tls_CAfile. When I get it working, I
| may post an update.
|
| Here's the update for the SSL certificate verification:
|
| If you want the verification process to work, you’ll need to provide
| valid certificate authority (CA) certificates to OpenSSL via postfix.
| For some reason, my computer did not have the default OpenSSL root CA
| certificates installed. So, I decided to import them from the system
| root CA keychain.
|
| Run the following:
|
| security find-certificate -a -p
| /System/Library/Keychains/SystemRootCertificates.keychain >
| /System/Library/OpenSSL/certs/cert.pem
|
| Include the following in /etc/postfix/main.cf:
|
| smtp_tls_CAfile = /System/Library/OpenSSL/certs/cert.pem
|
| Now you can change the MUST_NOPEERMATCH to just MUST, and the
| certificate verification should succeed if the certificate was signed
| with one of the system-accepted root certificates.
`----
8) sudo postmap /etc/postfix/smtp_sasl_passwords
sudo postmap /etc/postfix/smtp_tls_sites
9) restart/reload postfix (or reboot)
That shoud do the trick, if I haven't forgotten some important part to
add to my change notes ;-) And, the upgrade from Leopard to Snow Leopard
didn't overwrite these modifications, as I found out some minutes ago.
(And, sorry for exceeding 80 character per line.)
Regards,
Michael
--
to let
Michael Grimm
> On Wed, 25 Nov 2009 19:44:38 +0000 (UTC), Michael Grimm wrote:
>> 3) /etc/postfix/main.cf
>> # (added)
>> myorigin = your-domain.tld
Addition: that should be the mail address' domain part of your From:
> What's all this next about? I'll try next, but just follwed the default
> recommendation:
> # NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
> # POSTFIX STILL WORKS AFTER EVERY CHANGE.
All those options will postfix teach how to connect to your provider's
mail server using SMTP and SSL. Thus, you need them all, at least those
assigned a value.
>> 4) import your mail provider's CERT key into your keychain access list (login part)
>
> Is 5) the explanation for this step? Or how is it done?
No, 5) ...
>> 5) /System/Library/OpenSSL/certs/cert.pem (create)
>> sudo touch /System/Library/OpenSSL/certs/cert.pem
>> sudo chmod 666 /System/Library/OpenSSL/certs/cert.pem
>> sudo security find-certificate -a -p \
>> /System/Library/Keychains/SystemRootCertificates.keychain > \
>> /System/Library/OpenSSL/certs/cert.pem
>> sudo chmod 644 /System/Library/OpenSSL/certs/cert.pem
... will dump your keychain's content into
/System/Library/OpenSSL/certs/cert.pem in order to enable postfix to use
those keys. I did assume that you might use this kind of authentication
and thus having your provider's key stored into your keychain access
file, already.
> I do not have SystemRootCertificates.keychain, but just
> /System/Library/Keychains/X509Certificates
> (509 is my user id)
Then try to use that keychain file with your provider's key. If not
available yet, you need to get it from your provider. Have a look at
Google, because I do not have that openssl command at hand. Or, just
configure Mail.app the very same way you would like to use postfix and
proceed with 4).
Whiskers
> Martin Trautmann <t-...@gmx.net> wrote:
>> On Wed, 25 Nov 2009 19:44:38 +0000 (UTC), Michael Grimm wrote:
>
>>> 3) /etc/postfix/main.cf
>>> # (added)
>>> myorigin = your-domain.tld
>
> Addition: that should be the mail address' domain part of your From:
>
>> What's all this next about? I'll try next, but just follwed the default
>> recommendation:
>> # NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
>> # POSTFIX STILL WORKS AFTER EVERY CHANGE.
[...]
Now I understand how msmtp can claim to be 'simple' to set up! <grin>
Justin C
> On Tue, 24 Nov 2009 23:14:26 +0000, Justin C wrote:
>> file.... All the lines referencing mail are commented out so mine is
>> using using the standard sendmail commands and it's working.
>>
>> Looking at /etc/postfix/main.cf it doesn't look like I've customised
>> anything there either. It appears to 'just work' ... however, it didn't
>> used to. Maybe one of the software updates fixed it, I couldn't say.
>
> It could work for many installations. Probably it's due to my provider's
> policy with smtp after pop (I just said it wrong the other way) is not
> known to postfix.
You could write an applescript to tell mail to check for new mail, add
this, after a call to your mail_editor_command.
I've just tried this in my slrnrc:
set post_editor_command "mate -w -l %d %s; osascript ~/get_mail.scpt"
get_mail.scpt contains:
tell application "Mail"
check for new mail
end tell
slrn didn't complain, and mail was checked.
I now notice, in another post, that you use thunderbird - woulda been useful to have known!
Isn't it possible to have thunderbird as your mail editor in slrn?
Thomas Wiegner
> Would this be
> relayhost = mail.gmx.net:465
> or
> relayhost = gmx.net:465
> ?
>
> I tried both. With gmx.net it does try mx0.gmx.net and mx1.gmx.net, but
> does return a timeout only.
>
> With mail.gmx.net it tells me:
> warning: ...: defer service failure
> ...relay=none, delay=79, status=deferred (connect to
> mail.gmx.net[213.165.64.21]: server dropped connection without sending
> the initial SMTP greeting)
You have to set the relayhost in square brackets:
| relayhost = [mail.gmx.de]
http://www.postfix.org/postconf.5.html#relayhost
Without these postfix will do a MX lookup for the given host/domain
and thats not what you want.
Cheers,
Thomas
--
slrn packages for ubuntu and windows: http://www.foory.de/thw/slrn/
Whiskers
On 2009-11-28, Martin Trautmann <t-...@gmx.net> wrote:
> On Sat, 28 Nov 2009 11:30:01 +0100, Thomas Wiegner wrote:
>> You have to set the relayhost in square brackets:
>>
>> | relayhost = [mail.gmx.de]
>>
>> http://www.postfix.org/postconf.5.html#relayhost
>
> up.
>
> - Martin
You're welcome to send a test email to me.
Whiskers
I can only see this as a newsgroup post, not in email.
Justin C
> On Sat, 28 Nov 2009 21:13:32 +0000, Whiskers wrote:
.... errr.... I think that was a follow-up, not a reply. Try 'r' instead
of 'f'.
Whiskers
> On Sat, 28 Nov 2009 22:43:15 +0000, Justin C wrote:
>> >> You're welcome to send a test email to me.
>> >
>> > Test
>>
>> .... errr.... I think that was a follow-up, not a reply. Try 'r' instead
>> of 'f'.
>
> I guess this actually should trigger a send of email - it usually did
> before where sendmail had been available.
>
> - Martin
In slrn, the default action for F is to 'forward' the current article to
an email address. I've never found a use for that, and haven't tested it.
To send a 'courtesy copy' email of an outgoing newsgroup post, without the
original poster requesting it, requires changing the set cc_followup line
in ~/.slrnrc to 3 or 4 - that gives you a prompt each time you hit f to
followup. (The default is 1 - prompt if poster requested a copy). I
don't know of a keyboard command to over-ride that setting.
Justin C
> On Sat, 28 Nov 2009 22:43:15 +0000, Justin C wrote:
>> >
>> > Test
>>
>> .... errr.... I think that was a follow-up, not a reply. Try 'r' instead
>> of 'f'.
>
> I guess this actually should trigger a send of email - it usually did
> before where sendmail had been available.
'F' is 'forward', 'f' is followup, 'r' is reply, and, here at least 'R'
does nowt.