* [ISSUE] Attachment not found
@ 2020-11-04 10:30 Anachron
2020-11-04 11:18 ` leahneukirchen
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Anachron @ 2020-11-04 10:30 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
New issue by Anachron on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/191
Description:
I've accidentally added a wrong attachment path and sent the mail, now the recipient received a line with `# cannotopen (path)` which looks ugly.
Is it possible to mute errors like this or even prevent me from sending mails with attachments that cannot be read?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Attachment not found
2020-11-04 10:30 [ISSUE] Attachment not found Anachron
@ 2020-11-04 11:18 ` leahneukirchen
2020-11-06 19:20 ` Anachron
2020-11-08 14:10 ` [ISSUE] [CLOSED] " leahneukirchen
2 siblings, 0 replies; 4+ messages in thread
From: leahneukirchen @ 2020-11-04 11:18 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
New comment by leahneukirchen on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/191#issuecomment-721672761
Comment:
Hm, trying to reproduce this I get:
```
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_6cc04cbb64e51ce3738d8d8a_=_"
This is a multipart message in MIME format.
------_=_6cc04cbb64e51ce3738d8d8a_=_
mmime: error attaching file '/etc/issuez': No such file or directory
------_=_6cc04cbb64e51ce3738d8d8a_=_--
```
But status is 0, so this should be fixed and then reported (or even made fatal).
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Attachment not found
2020-11-04 10:30 [ISSUE] Attachment not found Anachron
2020-11-04 11:18 ` leahneukirchen
@ 2020-11-06 19:20 ` Anachron
2020-11-08 14:10 ` [ISSUE] [CLOSED] " leahneukirchen
2 siblings, 0 replies; 4+ messages in thread
From: Anachron @ 2020-11-06 19:20 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 232 bytes --]
New comment by Anachron on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/191#issuecomment-723255447
Comment:
Yep, I believe this should be a trivial fix? It not I can write a simple wrapper running "test -f".
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ISSUE] [CLOSED] Attachment not found
2020-11-04 10:30 [ISSUE] Attachment not found Anachron
2020-11-04 11:18 ` leahneukirchen
2020-11-06 19:20 ` Anachron
@ 2020-11-08 14:10 ` leahneukirchen
2 siblings, 0 replies; 4+ messages in thread
From: leahneukirchen @ 2020-11-08 14:10 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
Closed issue by Anachron on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/191
Description:
I've accidentally added a wrong attachment path and sent the mail, now the recipient received a line with `# cannotopen (path)` which looks ugly.
Is it possible to mute errors like this or even prevent me from sending mails with attachments that cannot be read?
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-11-08 14:10 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-04 10:30 [ISSUE] Attachment not found Anachron
2020-11-04 11:18 ` leahneukirchen
2020-11-06 19:20 ` Anachron
2020-11-08 14:10 ` [ISSUE] [CLOSED] " leahneukirchen
Github messages for mblaze
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://inbox.vuxu.org/mblaze-github
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V1 mblaze-github mblaze-github/ http://inbox.vuxu.org/mblaze-github \
mblaze-github@inbox.vuxu.org
public-inbox-index mblaze-github
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://inbox.vuxu.org/vuxu.github.mblaze
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git