to work around put the following line in your mutt profile
unset smtp_authenticators
songbird
On Mon, May 02, 2022 at 05:58:31PM -0400, songbird wrote:
Greg Wooledge wrote:
Also, bugs should be reported to bugs.debian.org, not here.
an FYI to fellow users can be helpful.
That may be true, but even in that case you should describe the issue
you've hit.
--
Please do not CC me for lis
Greg Wooledge wrote:
...
> The only difference between package versions 2.2.3-1 and 2.2.3-2 is
> the patch set that Debian applies.
ok, thanks, i filed a bug report.
songbird
On Mon, May 02, 2022 at 05:58:31PM -0400, songbird wrote:
> > On Mon, May 02, 2022 at 11:23:58AM -0400, songbird wrote:
> >> 2.2.3-1 version works
> >> 2.2.3-2 version does not work
> >
> > This isn't a useful bug report until you say *how* version 2.2.3-2 fails.
>
> mutt doesn't send mail.
*si
Greg Wooledge wrote:
> On Mon, May 02, 2022 at 11:23:58AM -0400, songbird wrote:
>>
>> 2.2.3-1 version works
>> 2.2.3-2 version does not work
>
> This isn't a useful bug report until you say *how* version 2.2.3-2 fails.
mutt doesn't send mail.
> Also, bugs should be reported to bugs.debian.or
On Mon, May 02, 2022 at 11:23:58AM -0400, songbird wrote:
>
> 2.2.3-1 version works
> 2.2.3-2 version does not work
This isn't a useful bug report until you say *how* version 2.2.3-2 fails.
Also, bugs should be reported to bugs.debian.org, not here.
On Fri 12 Nov 2021 at 15:03:24 (-0500), Greg Wooledge wrote:
> On Fri, Nov 12, 2021 at 08:58:18PM +0100, Hans wrote:
> > Greg Wooledge:
> > > chmod 1777 /var/tmp
> >
> > Yes, that works, of course! But I do not understand why the settings are
> > wrong.
>
> You said you've got /var on a separate
On Fri, Nov 12, 2021 at 08:58:18PM +0100, Hans wrote:
> Greg Wooledge:
> > chmod 1777 /var/tmp
>
> Yes, that works, of course! But I do not understand why the settings are
> wrong.
You said you've got /var on a separate partition. Was it always that
way (i.e. you created a /var partition during
Greg Wooledge:
chmod 1777 /var/tmp
Yes, that works, of course! But I do not understand why the settings are
wrong. I never changed these, so this could only be happened at some
upgrade, but the this should be discovered by other people, too.
However, maybe other applications do never use /va
On Fri, Nov 12, 2021 at 07:06:26PM +0100, Hans wrote:
> No, it is not /tmp, but /var/tmp. See here from the output:
> [2021-11-11 22:08:39] ../../mbox.c:895: mutt_mktemp returns "/var/tmp/mutt-
> protheus2-1000-47311-14301765248385272183".
> [2021-11-11 22:08:39] Temporärdatei konnte nicht erzeugt
Am Donnerstag, 11. November 2021, 21:53:53 CET schrieb Greg Wooledge:
No, it is not /tmp, but /var/tmp. See here from the output:
[2021-11-11 22:08:33] mutt_addr_is_user: no, all failed.
[2021-11-11 22:08:33] mutt_addr_is_user: no, all failed.
[2021-11-11 22:08:36] mutt_index_menu[807]: Got op
On Thu 11 Nov 2021 at 15:53:53 (-0500), Greg Wooledge wrote:
> On Thu, Nov 11, 2021 at 02:48:25PM -0600, David Wright wrote:
> > There should be some indication at this point of why it can't
> > delete your emails. The reason you see the filename
> > /home/username/.mutt-cache/scratchpad/mutt-hostn
On Thu, Nov 11, 2021 at 02:48:25PM -0600, David Wright wrote:
> There should be some indication at this point of why it can't
> delete your emails. The reason you see the filename
> /home/username/.mutt-cache/scratchpad/mutt-hostname… above is
> that I have set tmpdir="$HOME/.mutt-cache/scratchpad"
On Thu 28 Oct 2021 at 16:16:58 (+0200), Hans wrote:
> Am Donnerstag, 28. Oktober 2021, 15:38:34 CEST schrieb Greg Wooledge:
> [ … ] This is step-by-step what I do:
>
> Starting mutt from the commandline as normal user. Mutt in ncurses appears.
> Now I want to mark and delete all mails. I press S
On Thu 28 Oct 2021 at 17:17:19 (+0100), Tim Woodall wrote:
> On Thu, 28 Oct 2021, Hans wrote:
> >
> > I answer yes, and it appears "temporary file could not be created".
> >
> > Pressing again "q" and now answer "no", mutt closes.
> >
> > Does this help?
>
> check the ownership/permissions on /
On Thu 28 Oct 2021 at 17:04:59 (+0100), Tixy wrote:
> On Thu, 2021-10-28 at 17:48 +0200, Hans wrote:
> > Oh, and I forgot to mention or make clear:
> >
> > The file /var/mail/myusername does not be reduzed to 0, and as the user
> > myusername I can not manually delete this file, although (if I a
On Thu, 28 Oct 2021, Hans wrote:
I answer yes, and it appears "temporary file could not be created".
Pressing again "q" and now answer "no", mutt closes.
Does this help?
check the ownership/permissions on /tmp
Should be:
drwxrwxrwt 12 root root 8192 Oct 28 17:05 .
I've noticed some iss
On Thu, 2021-10-28 at 17:48 +0200, Hans wrote:
> Oh, and I forgot to mention or make clear:
>
> The file /var/mail/myusername does not be reduzed to 0, and as the user
> myusername I can not manually delete this file, although (if I am not
> wrong!),
> I should be able to, as it is rw for me.
On Thu, Oct 28, 2021 at 05:48:31PM +0200, Hans wrote:
> Oh, and I forgot to mention or make clear:
>
> The file /var/mail/myusername does not be reduzed to 0, and as the user
> myusername I can not manually delete this file, although (if I am not
> wrong!),
> I should be able to, as it is rw f
Oh, and I forgot to mention or make clear:
The file /var/mail/myusername does not be reduzed to 0, and as the user
myusername I can not manually delete this file, although (if I am not wrong!),
I should be able to, as it is rw for me.
Something special (maybe this is important): The directory
Am Donnerstag, 28. Oktober 2021, 16:48:20 CEST schrieb David Wright:
Thank you for all the help! First of all, I checked, if there is a nuttrc in my
~/HOME, but there is
none. But there is a Muttrc (yes, with capital letter) below /etc, so I suppose
this takes the
control.
However, I never cha
On Thu 28 Oct 2021 at 10:33:58 (-0400), Greg Wooledge wrote:
> I'm wondering, in particular, if there is some setting in mutt that
> tells it to attempt to delete the inbox file if it reaches 0 messages,
> and that perhaps you've enabled it. If so, you'll want to disable it.
That /would/ be a bu
On Thu, Oct 28, 2021 at 04:16:58PM +0200, Hans wrote:
> Am Donnerstag, 28. Oktober 2021, 15:38:34 CEST schrieb Greg Wooledge:
> Hi Greg,
>
> of course I can. This is step-by-step what I do:
>
> Starting mutt from the commandline as normal user. Mutt in ncurses appears.
> Now I want to mark and
On Thu 28 Oct 2021 at 16:16:58 (+0200), Hans wrote:
> Am Donnerstag, 28. Oktober 2021, 15:38:34 CEST schrieb Greg Wooledge:
> [ … ] This is step-by-step what I do:
>
> Starting mutt from the commandline as normal user. Mutt in ncurses appears.
> Now I want to mark and delete all mails. I press S
Am Donnerstag, 28. Oktober 2021, 15:38:34 CEST schrieb Greg Wooledge:
Hi Greg,
of course I can. This is step-by-step what I do:
Starting mutt from the commandline as normal user. Mutt in ncurses appears.
Now I want to mark and delete all mails. I press Shift+D, then it asks the for
the sample
On Thu, Oct 28, 2021 at 03:21:47PM +0200, Hans wrote:
> Hi folks,
>
> I got into an issue with mutt. Problem is, mutt can not delete mails and I
> myself can not delete
> the file below /var/mail/.
You are not *supposed* to delete your entire inbox file. You're only
supposed to modify it, pot
On Thu 16 Sep 2021 at 05:37:43 (-0500), Nate Bargmann wrote:
> * On 2021 15 Sep 21:36 -0500, David Wright wrote:
> > I think what your system is doing is as follows:
> >
> > You probably have in your (default) /etc/Muttrc:
>
> In my case, /etc/neomuttrc, and the following does exist.
>
> My assu
On Thu, Sep 16, 2021 at 07:43:25AM -0400, Greg Wooledge wrote:
Unfortunately, it breaks in Bourne-family shells.
snip
In Bourne/POSIX/bash, semicolon is a command terminator or separator,
and may not appear by itself, or at the start of a command. It may
appear at the end.
Good catch! I neve
On Thu, Sep 16, 2021 at 08:47:32AM +0100, Jonathan Dowland wrote:
> On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote:
> > I don't know why there's a ";" in front of it.
>
> That's (part of) my shell prompt. It's a convention originating in the
> rc shell (although I learned of it from
* On 2021 15 Sep 21:36 -0500, David Wright wrote:
> I think what your system is doing is as follows:
>
> You probably have in your (default) /etc/Muttrc:
In my case, /etc/neomuttrc, and the following does exist.
My assumptions have been that the system RC is ignored when a user's RC
exist. I am
* On 2021 16 Sep 02:35 -0500, Andrei POPESCU wrote:
> For neomutt in buster I have this in .neomuttrc:
>
> # neomutt disabled viewing text/* as text (except text/plain)
> # re-enable common file types received (requires corresponding .mailcap entry)
> auto_view text/x-diff
> auto_view text/x-patch
On Thu, Sep 16, 2021 at 08:47:32AM +0100, Jonathan Dowland wrote:
> On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote:
[...]
> >I don't know why there's a ";" in front of it.
>
> That's (part of) my shell prompt [...]
aaah :-)
Thanks for clearing that up. My hunch was at least
On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote:
Jonathan's message confused me too. As far as I can tell, "see" is
a *shell* command, not a mutt command.
Sorry for the confusion, I should have been clearer that it was a shell
command, intended to narrow the problem down to eithe
On Mi, 15 sep 21, 08:37:51, Nate Bargmann wrote:
> As there are a lot of Mutt/Neomutt users on this list, maybe someone can
> point me in the right direction.
>
> Recently via another mailing list a message was posted that included a
> diff file with the extension of .patch. The MIME encoding is
On Wed, Sep 15, 2021 at 09:34:50PM -0500, David Wright wrote:
[...]
> BTW, your shell command,
>
> !see --norun application/octet-stream:/dev/null
>
> will give you an answer in the context of a subshell, and
> not necessarily in the context of mutt itself [...]
Definitely, that's another po
On Wed 15 Sep 2021 at 16:21:12 (-0500), Nate Bargmann wrote:
> * On 2021 15 Sep 14:20 -0500, to...@tuxteam.de wrote:
> > On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote:
> > > On Wed, Sep 15, 2021 at 12:58:10PM -0500, Nate Bargmann wrote:
> > > > * On 2021 15 Sep 10:44 -0500, Jonathan
* On 2021 15 Sep 14:20 -0500, to...@tuxteam.de wrote:
> On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote:
> > On Wed, Sep 15, 2021 at 12:58:10PM -0500, Nate Bargmann wrote:
> > > * On 2021 15 Sep 10:44 -0500, Jonathan Dowland wrote:
> > > > What does this command report?
> > > >
> > >
On Wed, Sep 15, 2021 at 02:01:23PM -0400, Greg Wooledge wrote:
> On Wed, Sep 15, 2021 at 12:58:10PM -0500, Nate Bargmann wrote:
> > * On 2021 15 Sep 10:44 -0500, Jonathan Dowland wrote:
> > > What does this command report?
> > >
> > > ;see --norun application/octet-stream:/dev/null
> Jonathan
* On 2021 15 Sep 13:02 -0500, Greg Wooledge wrote:
> On Wed, Sep 15, 2021 at 12:58:10PM -0500, Nate Bargmann wrote:
> > * On 2021 15 Sep 10:44 -0500, Jonathan Dowland wrote:
> > > What does this command report?
> > >
> > > ;see --norun application/octet-stream:/dev/null
> >
> > In the message
On Wed, Sep 15, 2021 at 12:58:10PM -0500, Nate Bargmann wrote:
> * On 2021 15 Sep 10:44 -0500, Jonathan Dowland wrote:
> > What does this command report?
> >
> > ;see --norun application/octet-stream:/dev/null
>
> In the message window, "key not bound", in the view attachment window,
> "no ta
* On 2021 15 Sep 10:44 -0500, Jonathan Dowland wrote:
> On Wed, Sep 15, 2021 at 08:37:51AM -0500, Nate Bargmann wrote:
> > application/octet-stream; vim %s; description=Patch file;
> > nametemplate=%s.patch
>
> application/octet-stream is a fairly generic mime type (and an odd
> choice for a text
On Wed, Sep 15, 2021 at 08:37:51AM -0500, Nate Bargmann wrote:
application/octet-stream; vim %s; description=Patch file; nametemplate=%s.patch
application/octet-stream is a fairly generic mime type (and an odd
choice for a text file, but so it goes). You may find vim is not a
suitable tool for
On Sun, Apr 05, 2020 at 11:05:28AM +0200, Beatrice Torracca wrote:
> On Sat April 4th tomás wrote:
>
> > Since
> > mutt takes posession of the screen, it seems best to direct
> > strace's output to a file and examine it later. Like so:
> >
> > strace -f -o my_trace_file -e trace=open,%process mu
On Sat April 4th tomás wrote:
> Since
> mutt takes posession of the screen, it seems best to direct
> strace's output to a file and examine it later. Like so:
>
> strace -f -o my_trace_file -e trace=open,%process mutt
Hi,
I tried that. Then I realized I have to apologize.
My first try with m
On Sb, 04 apr 20, 14:43:24, Beatrice Torracca wrote:
> Hello,
>
> I have been trying to make mutt open pdf files from the
> view-attachment dialog.
>
> I am using a Debian buster (Linux beapc 4.19.0-8-amd64 #1 SMP Debian
> 4.19.98-1 (2020-01-26) x86_64 GNU/Linux) with Mutt 1.10.1
> (2018-07-13).
On Sat 04 Apr 2020 at 14:43:24 (+0200), Beatrice Torracca wrote:
>
> I have been trying to make mutt open pdf files from the
> view-attachment dialog.
>
> I was trying to make it open evince to view pdf files. It does not
> seem to recognize the mime type. I tried the same steps I followed
> with
On Sat, Apr 04, 2020 at 02:43:24PM +0200, Beatrice Torracca wrote:
> Hello,
>
> I have been trying to make mutt open pdf files from the
> view-attachment dialog.
>
> I am using a Debian buster (Linux beapc 4.19.0-8-amd64 #1 SMP Debian
> 4.19.98-1 (2020-01-26) x86_64 GNU/Linux) with Mutt 1.10.1
>
On Wed, Jul 10, 2019 at 09:06:32AM -0400, Greg Wooledge wrote:
> On Wed, Jul 10, 2019 at 09:31:13AM +0300, Reco wrote:
> > On Wed, Jul 10, 2019 at 10:35:33AM +0900, John Crawley wrote:
> > > On Thunderbird the OP was perfectly readable, and I had no idea it
> > > wasn't plain text till I checked th
Nick:
> On 2019-03-31 17:07 BST, Nick wrote:
>>
>> The not so good: no marker appears until I open messages. I
>> had expected that my imap_headers setting would cause the marker to
>> appear on all the qualifying messages in the index. How can I make
>> that happen?
>
> Solved: close mutt, del
On 2019-03-31 17:07 BST, Nick wrote:
> The not so good: no marker appears until I open messages. I
> had expected that my imap_headers setting would cause the marker to
> appear on all the qualifying messages in the index. How can I make
> that happen?
Solved: close mutt, delete .hcache files un
On Tue, Apr 25, 2017 at 11:29:18AM -0500, David Wright wrote:
> On Tue 25 Apr 2017 at 17:22:28 (+0200), Vincent Lefevre wrote:
> > On 2017-04-24 15:57:17 -0700, Mike McClain wrote:
> > > I'm running Debian Wheeze on a P3 1/2M memory. Mostly CL.
> > > Mutt 1.5.21 is the culprit ( or am I? )
> > >
On Tue 25 Apr 2017 at 17:22:28 (+0200), Vincent Lefevre wrote:
> On 2017-04-24 15:57:17 -0700, Mike McClain wrote:
> > I'm running Debian Wheeze on a P3 1/2M memory. Mostly CL.
> > Mutt 1.5.21 is the culprit ( or am I? )
> > I subscribe to mailing lists in digest form.
> > Mutt recognizes the f
On 2017-04-24 15:57:17 -0700, Mike McClain wrote:
> I'm running Debian Wheeze on a P3 1/2M memory. Mostly CL.
> Mutt 1.5.21 is the culprit ( or am I? )
> I subscribe to mailing lists in digest form.
> Mutt recognizes the fact when I'm viewing a Debian User digest but not
> when I'm reading a 'h
On Tue, Sep 27, 2016 at 07:53:57AM +0900, Mark Fletcher wrote:
> Lifted that from aptitude show archivemail. This is perfect, exactly
> what I was after! Thanks Brian!
Another vote for archivemail from me. I have a local patch to mine to add a
feature
to delete a mailbox if, after archiving, it
Mark Fletcher:
>
> So I was thinking of implementing a policy of deleting messages from
> this mail folder on my PC (the one Mutt is looking at) on a say monthly
> basis.
If you prefer a mutt-only solution (without archivemail) you could also
use a hook to mark all mails older than 30 days for
On Mon, Sep 26, 2016 at 04:01:01PM +0100, Brian wrote:
> On Mon 26 Sep 2016 at 23:36:54 +0900, Mark Fletcher wrote:
>
> > Any advice on the smoothest way to get background archiving (which in
> > this case means deletion) of old messages in this scenario? I'm not
> > married to a Mutt solution,
On Mon 26 Sep 2016 at 23:36:54 +0900, Mark Fletcher wrote:
> Any advice on the smoothest way to get background archiving (which in
> this case means deletion) of old messages in this scenario? I'm not
> married to a Mutt solution, any solution that will automatically delete
> the right mails at
On 9 June 2016 at 19:27, Morten Bo Johansen wrote:
> On 2016-06-08 Johann Spies wrote:
>
>
> I use the following in ~/.mailcap:
>
> text/html; chromium %s;
> text/html; /usr/bin/elinks -force-html -dump %s; copiousoutput
>
> and in ~/.muttrc:
>
> bind attachview-mailcap
> alternative
On 2016-06-08 Johann Spies wrote:
> Until a few weeks ago, I could open firefox from mutt by 'v' and then
> select the html-part of the email and press enter.
>
> Now firefox does not but w3m handles everything - which is not preferred
> when some links are important.
I use the following in ~/.ma
On Tue 17 May 2016 at 12:32:33 -0500, David Wright wrote:
> On Thu 12 May 2016 at 20:38:41 (+0100), Brian wrote:
>
> > For Exim and minimaldns the question is
> >
> > Does the hostname resolve to a fqdn (something with a dot in it)?
> >
> > 127.0.1.1 alum.anything_you_want
On Thu 12 May 2016 at 20:38:41 (+0100), Brian wrote:
> On Thu 12 May 2016 at 10:08:49 -0500, David Wright wrote:
> > On Thu 12 May 2016 at 11:33:10 (+0100), Brian wrote:
> > > On Wed 11 May 2016 at 14:51:31 -0500, David Wright wrote:
> > > > BTW when will dpkg-reconfigure exim4-config either st
Haines Brown wrote:
> Yes, I discovered that to be the case. So I am now able to configure the
> attachment file as I want:
> message_size_limit = 200M
But you do know, that just because your MTA does allow mails bigger than
200MiB (which will be ~130MB before base64 encoding), other MTA will
- Forwarded message from Brian -
Date: Fri, 13 May 2016 18:08:49 +0100
From: Brian
To: debian-user@lists.debian.org
Subject: Re: mutt attachment error
User-Agent: Mutt/1.5.23 (2014-03-12)
It appears from another mail
https://lists.debian.org/debian-user/2016/05/msg00565.html
that
On 13/05/2016 12:10, Haines Brown wrote:
I'm still having no luck increasing maximum attachment size.
I create file: /etc/exim4/exim4.conf.localmacros
I leave it default permissions: -rw-r--r-- 1 root root
It has a single line: MESSAGE_SIZE_LIMIT = 200M
followed by CR.
I am no expert on line e
On Fri 13 May 2016 at 07:10:02 -0400, Haines Brown wrote:
> I'm still having no luck increasing maximum attachment size.
>
> I create file: /etc/exim4/exim4.conf.localmacros
> I leave it default permissions: -rw-r--r-- 1 root root
> It has a single line: MESSAGE_SIZE_LIMIT = 200M
> followed by CR
On Fri 13 May 2016 at 12:01:02 -0400, Haines Brown wrote:
[...snip...]
> > WARNING WARNING WARNING^MESC[9d# This file was generated dynamically
> > from^MESC[10d# split config files in the /etc/exim4/conf.d/
[...snip...]
> I didn't understand the reference here to split configuration. I checke
- Forwarded message from Sven Hartge -
Date: Fri, 13 May 2016 15:41:53 +0200
From: Sven Hartge
To: debian-user@lists.debian.org
Subject: Re: mutt attachment error
User-Agent: tin/2.3.1-20141224 ("Tallant") (UNIX) (Linux/4.3.0-1-amd64
(x86_64)) tinews.pl/1.1.39
Haines Br
Haines Brown wrote:
> I'm still having no luck increasing maximum attachment size.
> I create file: /etc/exim4/exim4.conf.localmacros
> I leave it default permissions: -rw-r--r-- 1 root root
> It has a single line: MESSAGE_SIZE_LIMIT = 200M
> followed by CR.
> And I restart exim: # invoke-rc.d e
David Wright wrote:
> On Fri 13 May 2016 at 07:10:02 (-0400), Haines Brown wrote:
>> I'm still having no luck increasing maximum attachment size.
>>
>> I create file: /etc/exim4/exim4.conf.localmacros
>> I leave it default permissions: -rw-r--r-- 1 root root
>> It has a single line: MESSAGE_SIZE_
On Fri 13 May 2016 at 07:10:02 (-0400), Haines Brown wrote:
> I'm still having no luck increasing maximum attachment size.
>
> I create file: /etc/exim4/exim4.conf.localmacros
> I leave it default permissions: -rw-r--r-- 1 root root
> It has a single line: MESSAGE_SIZE_LIMIT = 200M
> followed by C
I'm still having no luck increasing maximum attachment size.
I create file: /etc/exim4/exim4.conf.localmacros
I leave it default permissions: -rw-r--r-- 1 root root
It has a single line: MESSAGE_SIZE_LIMIT = 200M
followed by CR.
And I restart exim: # invoke-rc.d exim4 reload
But:
# exim -bP | g
On Thu 12 May 2016 at 10:08:49 -0500, David Wright wrote:
> On Thu 12 May 2016 at 11:33:10 (+0100), Brian wrote:
> > On Wed 11 May 2016 at 14:51:31 -0500, David Wright wrote:
> > >
> > > BTW when will dpkg-reconfigure exim4-config either stop saying
> > > "hostname --fqdn did not return a ful
On Thu 12 May 2016 at 11:33:10 (+0100), Brian wrote:
> On Wed 11 May 2016 at 14:51:31 -0500, David Wright wrote:
> > On Tue 10 May 2016 at 17:43:03 (+0200), Sven Hartge wrote:
> > > David Wright wrote:
> > > > Isn't the Debian way to put
> > >
> > > > MESSAGE_SIZE_LIMIT=foo
> > >
> > > > into /e
On Wed 11 May 2016 at 14:51:31 -0500, David Wright wrote:
> On Tue 10 May 2016 at 17:43:03 (+0200), Sven Hartge wrote:
> > David Wright wrote:
> > > Isn't the Debian way to put
> >
> > > MESSAGE_SIZE_LIMIT=foo
> >
> > > into /etc/exim4/update-exim4.conf.conf and then run
> > > # dpkg-reconfigur
On Tue 10 May 2016 at 17:43:03 (+0200), Sven Hartge wrote:
> David Wright wrote:
> > On Tue 10 May 2016 at 11:07:47 (-0400), Haines Brown wrote:
>
> >> I tried to use mutt to send someone a zip file of about 50 Mb and got
> >> the error: "Error sending message, child exited 1 (). Could not send
>
On Wed 11 May 2016 at 18:28:59 +0200, to...@tuxteam.de wrote:
> just a little note: "exim -bP" dumps all configuration items Exim
> thinks it's seeing (after all Debian magic happened) So perhaps
> for debugging you might try:
>
> sudo exim -bP | grep size
>
> which, on my box gives:
>
> bo
On Wed, 11 May 2016 11:12:26 -0400
Haines Brown wrote:
>
> I took a look at /usr/share/doc/exim4/README.Debian.gz and found that
> to use a macro to change a default configuration value I need to
> define the new value in a local configuration file. I have a non-split
> configuration, and so it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
just a little note: "exim -bP" dumps all configuration items Exim
thinks it's seeing (after all Debian magic happened) So perhaps
for debugging you might try:
sudo exim -bP | grep size
which, on my box gives:
bounce_return_size_limit = 100K
Haines Brown wrote:
> I took a look at /usr/share/doc/exim4/README.Debian.gz and found that to
> use a macro to change a default configuration value I need to define the
> new value in a local configuration file. I have a non-split
> configuration, and so it seems I must create a
> /etc/exim4/exi
On Tue, May 10, 2016 at 07:58:36PM +0200, Sven Hartge wrote:
> Brian wrote:
> > On Tue 10 May 2016 at 17:43:03 +0200, Sven Hartge wrote:
> >> David Wright wrote:
> >> > On Tue 10 May 2016 at 11:07:47 (-0400), Haines Brown wrote:
>
> I tried to use mutt to send someone a zip file of about 50
On Wed, 11 May 2016 at 04:43, Brian wrote:
> On Tue 10 May 2016 at 12:56:47 -0600, Charlie Kravetz wrote:
>
> > On Tue, 10 May 2016 17:03:47 +0100
> > Brian wrote:
> > >
> > >Didn't spot that; exim's .confs can be confusing. What file is used for
> > >non-split configuration?
> > >
> >
> > Not m
On Tue 10 May 2016 at 12:56:47 -0600, Charlie Kravetz wrote:
> On Tue, 10 May 2016 17:03:47 +0100
> Brian wrote:
> >
> >Didn't spot that; exim's .confs can be confusing. What file is used for
> >non-split configuration?
> >
>
> Not meaning to send this to you, Brian, but I lost the previous mess
On Tue, 10 May 2016 17:03:47 +0100
Brian wrote:
>On Tue 10 May 2016 at 17:43:03 +0200, Sven Hartge wrote:
>
>> David Wright wrote:
>> > On Tue 10 May 2016 at 11:07:47 (-0400), Haines Brown wrote:
>>
>> >> I tried to use mutt to send someone a zip file of about 50 Mb and got
>> >> the erro
On Tue 10 May 2016 at 19:58:36 +0200, Sven Hartge wrote:
> Brian wrote:
> > On Tue 10 May 2016 at 17:43:03 +0200, Sven Hartge wrote:
> >> David Wright wrote:
> >>> Isn't the Debian way to put
>
> >>> MESSAGE_SIZE_LIMIT=foo
>
> >>> into /etc/exim4/update-exim4.conf.conf and then run
> >>> # d
Haines Brown wrote:
> I tried to use mutt to send someone a zip file of about 50 Mb and got
> the error: "Error sending message, child exited 1 (). Could not send
> message."
> I assumed the attachment was too large and so went to
> /etc/exim4/conf.d/main/02*/ and altered the configuration to be
Brian wrote:
> On Tue 10 May 2016 at 17:43:03 +0200, Sven Hartge wrote:
>> David Wright wrote:
>> > On Tue 10 May 2016 at 11:07:47 (-0400), Haines Brown wrote:
I tried to use mutt to send someone a zip file of about 50 Mb and got
the error: "Error sending message, child exited 1 (). Co
On Tue 10 May 2016 at 17:43:03 +0200, Sven Hartge wrote:
> David Wright wrote:
> > On Tue 10 May 2016 at 11:07:47 (-0400), Haines Brown wrote:
>
> >> I tried to use mutt to send someone a zip file of about 50 Mb and got
> >> the error: "Error sending message, child exited 1 (). Could not send
>
David Wright wrote:
> On Tue 10 May 2016 at 11:07:47 (-0400), Haines Brown wrote:
>> I tried to use mutt to send someone a zip file of about 50 Mb and got
>> the error: "Error sending message, child exited 1 (). Could not send
>> message."
>>
>> I assumed the attachment was too large and so went
On Tue 10 May 2016 at 10:28:24 -0500, David Wright wrote:
> On Tue 10 May 2016 at 11:07:47 (-0400), Haines Brown wrote:
> > I tried to use mutt to send someone a zip file of about 50 Mb and got
> > the error: "Error sending message, child exited 1 (). Could not send
> > message."
> >
> > I assume
On Tue 10 May 2016 at 11:07:47 (-0400), Haines Brown wrote:
> I tried to use mutt to send someone a zip file of about 50 Mb and got
> the error: "Error sending message, child exited 1 (). Could not send
> message."
>
> I assumed the attachment was too large and so went to
> /etc/exim4/conf.d/main/
On Mon, 29 Feb 2016 15:40:25 + (UTC) Curt sent:
> btw, speaking of yaks, I've got a couple of Tibetan yak
> > blankets, very light and warm.
>
> No kidding I have a couple of sweaters out of yak; light and warm is
> right. Beats the hell out of sheep.
Horses for courses. The wool from sh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 29, 2016 at 03:40:25PM +, Curt wrote:
> On 2016-02-29, Joel Roth wrote:
> >
> > I'm in no special hurry, but it's nice to read your
> > contributions here :)
> >
> > btw, speaking of yaks, I've got a couple of Tibetan yak
> > blankets,
On 2016-02-29, Joel Roth wrote:
>
> I'm in no special hurry, but it's nice to read your
> contributions here :)
>
> btw, speaking of yaks, I've got a couple of Tibetan yak
> blankets, very light and warm.
No kidding I have a couple of sweaters out of yak; light and warm is
right. Beats the hell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 29, 2016 at 02:12:34AM -1000, Joel Roth wrote:
[...]
> I'm in no special hurry, but it's nice to read your
> contributions here :)
*blush*
> btw, speaking of yaks, I've got a couple of Tibetan yak
> blankets, very light and warm.
Now y
On Mon, Feb 29, 2016 at 11:56:38AM +0100, to...@tuxteam.de wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> [setting To: to list, I hope that's OK with you]
>
> On Mon, Feb 29, 2016 at 01:09:35AM -1000, Joel Roth wrote:
> >
> > On Mon, Feb 29, 2016 at 11:17:31AM +0100, to...@tuxteam.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[setting To: to list, I hope that's OK with you]
On Mon, Feb 29, 2016 at 01:09:35AM -1000, Joel Roth wrote:
>
> On Mon, Feb 29, 2016 at 11:17:31AM +0100, to...@tuxteam.de wrote:
[...]
> > > Hi Tomás,
> > >
> > > I noticed that it is signed message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 29, 2016 at 12:32:31AM -1000, Joel Roth wrote:
> tomás wrote:
>
> > On Sun, Feb 28, 2016 at 10:21:43PM -1000, Joel Roth wrote:
> > > Hi,
> > >
> > > I have gpg installed (package gpgv).
> > >
> > > I tried putting "source /etc/Muttrc.d/g
Le primidi 11 ventôse, an CCXXIV, Joel Roth a écrit :
> Saving your message to a folder and running gpg -d on it
> returns the message text and this:
>
> gpg: Signature made Sun 28 Feb 2016 10:43:03 PM HST using DSA key ID
> 7AD1DA46
> gpg: Can't check signature: public key not found
tomás wrote:
> On Sun, Feb 28, 2016 at 10:21:43PM -1000, Joel Roth wrote:
> > Hi,
> >
> > I have gpg installed (package gpgv).
> >
> > I tried putting "source /etc/Muttrc.d/gpg.rc" at the end of
> > ~/.muttrc, and also putting "source /etc/Muttrc" at the
> > beginning.
>
> (1) Does it ask you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Feb 28, 2016 at 10:21:43PM -1000, Joel Roth wrote:
> Hi,
>
> I have gpg installed (package gpgv).
>
> I tried putting "source /etc/Muttrc.d/gpg.rc" at the end of
> ~/.muttrc, and also putting "source /etc/Muttrc" at the
> beginning.
(1) Doe
1 - 100 of 1694 matches
Mail list logo
