similar to: [Fwd: Re: Bug in BODYSTRUCTURE]

Displaying 20 results from an estimated 2000 matches similar to: "[Fwd: Re: Bug in BODYSTRUCTURE]"

2017 Apr 08
2
usbhid-ups: Failed to open device, skipping. (Permission denied)
Charles Lepple writes: > On Sun, Apr 2, 2017 at 2:59 AM, Sam Varshavchik <mrsam at courier-mta.com> > wrote: > > Having trouble configuring nut 2.7.4 on Fedora 25, with a new Tripp Lite > > UPS. > > > > I'm running XFCE, and XFCE's Power Manager sees the UPS just fine. lsusb > > gives: > > > > Bus 006 Device 002: ID 09ae:3016 Tripp
2007 Jul 01
5
[Bug 11441] New: Minor display corruption
http://bugs.freedesktop.org/show_bug.cgi?id=11441 Summary: Minor display corruption Product: xorg Version: 7.1 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: mrsam
2017 Apr 07
0
usbhid-ups: Failed to open device, skipping. (Permission denied)
On Sun, Apr 2, 2017 at 2:59 AM, Sam Varshavchik <mrsam at courier-mta.com> wrote: > Having trouble configuring nut 2.7.4 on Fedora 25, with a new Tripp Lite > UPS. > > I'm running XFCE, and XFCE's Power Manager sees the UPS just fine. lsusb > gives: > > Bus 006 Device 002: ID 09ae:3016 Tripp Lite I'm still catching up on mail, so apologies if this was
2024 Jan 20
0
NUT and Eaton UPS produce a lot of error messages
Thanks for the info! First, regarding the later detail about starting `usbhid-ups`: the "Resource busy" indicates that likely an earlier instance of the NUT driver (in its own service unit) is still running and holding the device. In a worse case, some other programs might consider this a HID device (same class family as keyboards and mice) and grab it somehow, or it gets passed through
2017 Apr 01
2
usbhid-ups: Failed to open device, skipping. (Permission denied)
Having trouble configuring nut 2.7.4 on Fedora 25, with a new Tripp Lite UPS. I'm running XFCE, and XFCE's Power Manager sees the UPS just fine. lsusb gives: Bus 006 Device 002: ID 09ae:3016 Tripp Lite nut-scanner -U has no issues either: # nut-scanner -U Scanning USB bus. [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "09AE" productid =
2017 Sep 11
2
new NUT release please!
On 9/10/2017 6:41 PM, Sam Varshavchik wrote: > Dutchman01 writes: > >> Hello all, >> >> ? >> >> I request a new NUT release as current dates back to March 9, 2016: NUT 2.7.4 >> >> The fact stays that not all distro?s use latest snapshots/commits from github >> dev tree. >> >> ? >> >> So please do release a new up to
2017 Nov 12
1
Cyberpower model numbers in the HCL
Charles Lepple writes: > On Nov 12, 2017, at 10:08 AM, Sam Varshavchik wrote: > > > > The HCL has an entry for a Cyberpower model CP1500AVRLCD. Not listed is > the CP1500PFCLCD model, a newer, premium version of the unit; but the HCL > does have an entry for the CP1000PFCLCD model. > > > > Pretty sure that the CP1500PFCLCD will work; but figure I ask if anyone
2017 Apr 08
1
usbhid-ups: Failed to open device, skipping. (Permission denied)
Stuart Gathman writes: > On 04/07/2017 09:15 PM, Sam Varshavchik wrote: > > Charles Lepple writes: > > > >> > >> Full gory details here: https://github.com/networkupstools/nut/pull/122 > > > > This particular new unit came with its own USB cable, and this unit is > > plugged into a relatively old server. The motherboard is about ten > >
2004 Oct 01
1
Dovecot/IMP Bug with RFC822.SIZE and BODYSTRUCTURE
Ok, I have narrowed my IMP/Dovecot attachment problem down to what I think is a bug in Dovecot. The test that follow are performed on 0.99.11. When you download an attachment in IMP it uses the php function imap_fetchbody() which contacts the IMAP server and retrieves just the mime chunk you are looking for. It does this by first fetching some information about the email, and then grabs the
2024 Jan 20
1
NUT and Eaton UPS produce a lot of error messages
Stefan Schumacher via Nut-upsuser writes: > I am considering returning the device to the online shop I bought. As > it is, it's nothing but trouble. Can you recommend a small UPS (1 > Server) that is guaranteed to work flawlessly with NUT? I've had good experience with Cyberpower units, as long as they're included NUT's hardware list. -------------- next part
2020 Mar 03
3
[PATCH] lib-imap: imap-bodystructure: add test with empty header field
This causes the body structure to be incorrect. The RFC says it's fine o have empty header field values. --- This just adds a failing test, inspired from an e-mail spotted in the wild. Ideas welcome to fix it. src/lib-imap/test-imap-bodystructure.c | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/lib-imap/test-imap-bodystructure.c
2017 Dec 08
3
Mailsploit problem in responce of BODYSTRUCTURE
Hi, I tried to see a mail that have a strange From header in bellow URL: https://www.mailsploit.com/index Then, I got BODYSTRUCTURE response contain next: ((NIL NIL "service" "paypal.com")) Are this problem already founded by anyone? So already fixed? -- TACHIBANA Masashi QUALITIA CO., LTD. mailto:tachibana at qualitia.co.jp
2005 Feb 02
1
assertion failed in imap-bodystructure.c
Hello, I'm currently testing dovecot/imap (Version 0.99.13). I found this in the log: imap(xxxxx): [ID 265587 mail.crit] file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) dovecot: [ID 684838 mail.error] child 7376 (imap) killed with signal 6 The user tried to setup a new folder (with Thunderbird)
2009 Nov 12
2
fetch bodystructure filename problem rfc2231
Hi, I have a problem with the filename of attachments in some clients. # dovecot 1.2.(5|7) * 3 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 13 1 NIL NIL NIL NIL)("text" "plain" ("charset" "UTF-8" "name" "ISO-8859-1''testanh%E4ng.txt") NIL NIL
2012 May 10
1
BODYSTRUCTURE bug?
Hi! I've found a bug in Content-Type parsing. It's old instance of dovecot 1.1. Maybe fixed in newer versions. I have a mail with header: Content-Type: multipart/signed; boundary="------------080705010808010608030700"; protocol="application/x-pkcs7-signature";micalg="SHA1" and it works, but when the boundary is in different order Content-Type:
2018 Nov 15
1
FETCH BODY vs FETCH BODYSTRUCTURE + FETCH BODY.PEEK
Hello, we are developing a web page, for a ticket system, to show the email messages ordered by the biggest attachments size present in an IMAP folder, with a pagination of 100 messages per page. Each raw represents a message with "DATE, FROM, SUBJECT, the preview (the first 500 chars of the text/html of the messsage) and the list of the attachments (name + size) it contains. The
2003 Jan 06
1
Assert in imap-bodystructure.c
First let me thank you for my initial newby question about poping from a pop3 server and delivering into my Dovecot maildir folders. Now I'm getting an assertion in imap-bodystructure.c and one of my imap folders is now inaccessable. I think the two are related. Whenever I select the folder from my email client (kmail) I get two log entries in the dovecot log of the format:
2017 Nov 27
2
Re: kvm/libvirt on CentOS7 w/Windows 10 Pro guest
On 11/25/2017 07:25 AM, Sam Varshavchik wrote: > > I don't use virtio drivers. My Windows 10 guest setup is as plain as it can be. > > Starting with qemu 2.9, there is some kind of a problem that prevents Windows 10 from rebooting itself properly. I've also read about others reporting this issue as well. It's possible that the problem started before 2.9. Fedora 25, with
2017 Dec 08
0
Mailsploit problem in responce of BODYSTRUCTURE
On Fri, Dec 08, 2017 at 18:47:37 +0900, TACHIBANA Masashi wrote: > Hi, > > I tried to see a mail that have a strange From header in bellow URL: > > https://www.mailsploit.com/index > > Then, I got BODYSTRUCTURE response contain next: > > ((NIL NIL "service" "paypal.com")) > > Are this problem already founded by anyone? > So already
2009 May 04
2
Problem with BODYSTRUCTURE (wrong charset)
Hi, I've changed a program that fetches mail via IMAP from an Exchange Server to use our Dovecot machine. But now I'm experiencing strange problems with seem to be caused by a wrong BODYSTRUCTURE answer that causes wrong charset handling. When fetchting the BODYSTRUCTURE I see this: Dovecot: 88 UID fetch 32 (BODYSTRUCTURE) * 1 FETCH (UID 32 BODYSTRUCTURE ("text"