From: Peter Salazar <cycleofsong@gmail.com>
To: David Bremner <david@tethera.net>
Cc: fauno <fauno@kiwwwi.com.ar>, notmuch@notmuchmail.org
Subject: Re: file-error "not a regular file"
Date: Tue, 29 Dec 2015 00:54:24 -0500 [thread overview]
Message-ID: <CAE+_6TzCar9+y66p4hVL0U=dLFOR9uEUkSLJJ=pCDqJ6-bLkXw@mail.gmail.com> (raw)
In-Reply-To: <87ege6d41j.fsf@zancas.localnet>
[-- Attachment #1: Type: text/plain, Size: 2274 bytes --]
Hi David,
Thanks for looking into this. Much appreciated.
Yes, following your steps, emacs -q followed by "M-x load-library <return>
notmuch", I was able to send an email without the error. It prompted me for
my smtp server, username, and password, then returned this:
Sending email
Sending email done
Invalid image size (see `max-image-size')
Mark set
Saving file
/Users/peter/Dropbox/mail/gmail/sent/tmp/1451367804.6837_72197_1.Infinity.local...
Wrote
/Users/peter/Dropbox/mail/gmail/sent/tmp/1451367804.6837_72197_1.Infinity.local
Sending...done
To answer your other question, yes, there is an Fcc: header when I try to
send email from my regular Emacs configuration. It's the same header I saw
when I sent email from the minimal configuration:
Fcc: /Users/peter/Dropbox/mail/gmail/sent
That directory does indeed exist:
drwxr-xr-x@ 9 peter staff 306 Dec 27 21:54 *sent*
And it contains:
.DS_Store .mbsyncstate *.nnmaildir* .uidvalidity *cur* *new*
*tmp*
Does this give us any leads?
Thanks again.
On Mon, Dec 28, 2015 at 9:46 AM, David Bremner <david@tethera.net> wrote:
> fauno <fauno@kiwwwi.com.ar> writes:
>
> > Peter Salazar <cycleofsong@gmail.com> writes:
> >
> >> Hello,
> >>
> >> I'm using notmuch-mode from within Emacs to send email using
> async/mbsync
> >> through Gmail. However, every time I send email from within Emacs, I get
> >> this error:
> >
> > i got this message too for fcc with default values, i'm on emacs 24.5
> > with notmuch 0.21
> >
>
> Can either of you replicate the problem with a minimal configuration,
> ideally with "emacs -q", followed by "M-x load-library <return>
> notmuch"?
>
> If so, does the path in the Fcc header exist? If so, what is it? a file,
> a directory, a symlink?
>
> For me, in emacs 24.5 / notmuch 0.21, with emacs -q, if that path is
> missing I am prompted to create it. If I refuse, then I later get a
> message about not being a maildir.
>
> I guess the tl;dr is that I can't duplicate this problem. Looking at the
> traceback Peter provided, it looks like he is using
> "send-message-without-bullets" to send the message. Since this isn't a
> notmuch function, it's likely bypassing the notmuch fcc setup that
> notmuch-mua-send and notmuch-mua-send-and-exit do.
>
>
> d
>
>
[-- Attachment #2: Type: text/html, Size: 4404 bytes --]
next prev parent reply other threads:[~2015-12-29 5:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 3:07 file-error "not a regular file" Peter Salazar
2015-12-28 4:01 ` fauno
2015-12-28 14:46 ` David Bremner
2015-12-29 0:36 ` fauno
2015-12-30 9:38 ` Michal Sojka
2015-12-30 14:14 ` notmuch-mua and jl-encrypt (was: file-error "not a regular file") fauno
2016-01-02 21:24 ` Michal Sojka
2015-12-29 5:54 ` Peter Salazar [this message]
2015-12-29 20:44 ` file-error "not a regular file" David Bremner
2015-12-29 21:34 ` Peter Salazar
2015-12-29 21:48 ` David Edmondson
2016-01-04 10:11 ` Peter Salazar
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE+_6TzCar9+y66p4hVL0U=dLFOR9uEUkSLJJ=pCDqJ6-bLkXw@mail.gmail.com' \
--to=cycleofsong@gmail.com \
--cc=david@tethera.net \
--cc=fauno@kiwwwi.com.ar \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).