From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] Can't seem to send mail
Date: Mon, 08 Jun 2009 14:44:50 -0400 [thread overview]
Message-ID: <1244486438-sup-3501@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <AAB8FA5E-9E58-4C24-9290-F3C80155E55D@talkhouse.com>
Excerpts from Joe W?lfel's message of Mon Jun 08 14:05:34 -0400 2009:
> It looks like sendmail isn't functioning and doesn't generate any
> errors. Maybe it's a mac problem. I haven't tried it on anything
> else yet.
Personally, I don't think sendmail has _ever_ been functional, but
that's just the grumpy side of me that has to configure it on clunky
old boxes still! :)
It's likely working, but has a local delivery setup configured. Try
using `mailq` to see if anything is sitting in the outbound queue.
You may also want to look in /var/spool/mail for mbox files sitting
there with the messages (or bounces) sent from sup.
If you want to get your hands dirty, I recommend exim as the
replacment for sendmail. I like it's configuration and acl setup
better than postfix, but that would also work. If you just want to
send mail quickly and easily, try msmtp or a similar package.
HTH.
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090608/1f82e67c/attachment.bin>
next prev parent reply other threads:[~2009-06-08 18:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 15:21 Joe Wölfel
2009-06-08 15:50 ` Andrei Thorp
2009-06-08 15:52 ` Ben Walton
2009-06-08 18:05 ` Joe Wölfel
2009-06-08 18:42 ` Andrei Thorp
2009-06-08 18:44 ` Ben Walton [this message]
2009-06-08 20:03 ` Joe Wölfel
2009-06-08 20:53 ` Andrei Thorp
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=1244486438-sup-3501@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
/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