From: Erik Quaeghebeur <sup@equaeghe.nospammail.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] error when sending mail
Date: Tue, 1 Jun 2010 11:13:47 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1006011113190.1659@flfbcjrt.naqerj.pzh.rqh> (raw)
In-Reply-To: <1275397644-sup-1664@pinkfloyd.chass.utoronto.ca>
> Excerpts from Erik Quaeghebeur's message of Mon May 31 22:42:49 -0400 2010:
>
> > WARNING: Problem sending mail: File or folder does not exist -
> > <path/to/maildir/sent/folder>/tmp/1275359009.7145703845.sysopweg:2,S
On Tue, 1 Jun 2010, Ben Walton wrote:
>
> Sup version? Ruby version?
sup v0.11 (installed the gem)
ruby 1.8.7 (2010-01-10 patchlevel 249) [x86_64-linux] (ubuntu packages)
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-06-01 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 2:42 Erik Quaeghebeur
2010-06-01 13:07 ` Ben Walton
2010-06-01 15:13 ` Erik Quaeghebeur [this message]
2010-06-02 13:51 ` Ben Walton
2010-06-02 14:03 ` Erik Quaeghebeur
2010-06-02 14:08 ` Ben Walton
2010-06-02 15:48 ` Sebastian Schwarz
2010-06-02 19:52 ` Erik Quaeghebeur
2010-06-02 20:14 ` Ben Walton
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=alpine.DEB.2.00.1006011113190.1659@flfbcjrt.naqerj.pzh.rqh \
--to=sup@equaeghe.nospammail.net \
--cc=sup-talk@rubyforge.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