Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] error when sending mail
Date: Wed, 02 Jun 2010 10:08:56 -0400	[thread overview]
Message-ID: <1275487597-sup-8855@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <alpine.DEB.2.00.1006020958510.1883@flfbcjrt.naqerj.pzh.rqh>

Excerpts from Erik Quaeghebeur's message of Wed Jun 02 10:03:19 -0400 2010:

> <path/to/maildir/sent/folder> is what I replaced the actual path
> given in the error message with (it was /home/equaeghe/Mail/sent);
> it now does seem a useless modification

And a dumb question from me: /home/equaeghe/Mail/sent does contain the
maildir subfolders cur, new and tmp?

> :sent_source: maildir:/home/equaeghe/Mail/sent

Ok, this looks fine as long as /home/equaeghe/Mail/sent is a proper
maildir setup.

> > This is normal.
> 
> Ah. Can I change it so that it does save sent mails? Or should I 
> explicitly set Fcc when sending mail?

Sorry, I meant normal in the sense that sending the mail and storing
mail in the sent source are two separate (non-atomic) actions.  When
you hit the send key, the message is dumped into $sendmail for
transport.  It's then written to the sent source.  These are
independent.  One may succeed while the other fails.

Thanks
-Ben

-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-06-02 14: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
2010-06-02 13:51 ` Ben Walton
2010-06-02 14:03   ` Erik Quaeghebeur
2010-06-02 14:08     ` Ben Walton [this message]
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=1275487597-sup-8855@pinkfloyd.chass.utoronto.ca \
    --to=bwalton@artsci.utoronto.ca \
    --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