From: Sebastian Schwarz <seschwar@googlemail.com>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] error when sending mail
Date: Wed, 2 Jun 2010 17:48:09 +0200 [thread overview]
Message-ID: <20100602154809.GQ3617@pineapple.q.wohnheim-jahnplatz.de> (raw)
In-Reply-To: <1275487597-sup-8855@pinkfloyd.chass.utoronto.ca>
On 2010-06-02 at 10:08 -0400, Ben Walton wrote:
>> :sent_source: maildir:/home/equaeghe/Mail/sent
>
> Ok, this looks fine as long as /home/equaeghe/Mail/sent is a proper
> maildir setup.
Just a guess, but according to NewUserGuide.txt the mailbox
URIs start with maildir:// or mbox://. Therefore try:
:sent_source: maildir:///home/equaeghe/Mail/sent
Note the two extra slashes.
HTH,
Sebastian
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-06-02 15:48 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
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 [this message]
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=20100602154809.GQ3617@pineapple.q.wohnheim-jahnplatz.de \
--to=seschwar@googlemail.com \
--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