Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Erik Quaeghebeur <sup@equaeghe.nospammail.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] error when sending mail
Date: Mon, 31 May 2010 22:42:49 -0400	[thread overview]
Message-ID: <1275360058-sup-177@sysopweg> (raw)

Hi,


When sending mail, I get this warning:

WARNING: Problem sending mail: File or folder does not exist - <path/to/maildir/sent/folder>/tmp/1275359009.7145703845.sysopweg:2,S

However, the mail was sent (and did arrive), but it was not saved as a 
sent messages in my sent-mail maildir folder (which is totally empty).

Any ideas about how to solve/diagnose this?


TIA,

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


             reply	other threads:[~2010-06-01  2:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01  2:42 Erik Quaeghebeur [this message]
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
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=1275360058-sup-177@sysopweg \
    --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