search for: from_

I feel like I'm going totally crazy. Is it just me, or have embedded From_ lines really been breaking mbox messages since (at least) dovecot 1.0? I found a whole lot of broken messages in an old mailbox of mine and when I looked closer at it, it seemed like Dovecot was ignoring the Content-Length header and truncating the messages at the first embedded From_ line...

Sorry, couldn't find this in the archives. Under freebsd 4.x, the native mail.local that sendmail uses by default writes From_ lines that include the origin address. This is very readily parsable and handy for quick greps in mboxes. But deliver defaults it to MAILER-DAEMON. I see you can specify the envelope From_ with "-f", but I'm not sure how that's useful. Also I'm trying to figure out the ins...

(Using dovecot 1.0 RC7 on Fedora Core 5) <scene set> Hitherto we have used UW-IMAP on a "farm" of Linux machines mounting NFS from a NetApp. (The UW-IMAP author doesn't like use of NFS, but with careful use of NFS mount arguments ('noac,actimeo=0' etc.) and trying to ensure that all activity for a given user takes place within one machine in the farm, we seem to

If I send mail with content like this: From <test.dovecot at m.box> Wed Jan 09 01:33:55 2008 From <test.dovecot at m.box> Wed Jan 09 01:33:55 2008 From <test.dovecot at m.box> Wed Jan 09 01:33:55 2008 From <test.dovecot at m.box> Wed Jan 09 01:33:55 2008 and instead single messages created many messages. Inside mbox file it looks like real_message_headers Status:

Hi! I'm using procmail to filter my email. (I have to use it because of various features that are not supported by sieve.) However, I'd like to deliver mail to my mboxes using dovecots deliver program in order to update index files and speed up mbox access. Using "| $DELIVER -m <mboxname>" in my procmail receipes, everything works fine, except that the envelope sender

I just upgraded our test server from rc6 to rc10... ISSUE #1 I noticed that we no longer are getting two "From_" lines. However, the one that was good (had the original sender e-mail address) is now gone. The one with "dovecot.deliver" remains. I attempted to add "-d test" to the mailbox_command line in main.cf as follows: mailbox_command = /opt/dovecot/libexec/dovecot/deliver -...

...on, which uses it's own status headers (X-Mozilla*) that were not recognised by Evolution. I have no idea which mbox subformat was always used throughout the different programs and versions... 1) Any way to check for that? To make things worse... Thunder(burden) seems to have used a modified From_ line syntax... "^From -<address> <date>$" Ideally I'd like migrate all mail into dovecot (for storage reasons again, mbox) retaining the different status flags (read, forwarded, etc.) and getting rid of the proprietary headers (of course only when they were. First thi...

Hello, I was asking what was the motivation for not having the envelope From in the Maildir format, as defined in the qmail spec : "The message is delivered without an extra UUCP- style From_ line, without any >From quoting, and without an extra blank line at the end." which may sound silly since we lose an important piece of information. Same question about the motivation in Courrier (Maildir++) for emulating a hierarchy for subfolders (like in .folder.subfolder.subsubfolde...

...,s,1) exten => _X.,n,GotoIfTime(13:01-17:00|mon-fri|*|*?opened,s,1) exten => _X.,n,GotoIfTime(17:01-23:59|fri|*|*?closed,s,1) exten => _X.,n,GotoIfTime(*|sat-sun|*|*?closed,s,1) exten => _X.,n,Goto(closed,s,1) [opened] include=parkedcalls exten => s,1,MixMonitor(incoming-from_${CALLERIDNUM}-${TIMESTAMP}-${UNIQUEID}.wav ) ; Removed exten 201 and replaced with 238 on 8/24/06 ;exten => s,n,Dial(Sip/201&Sip/209&Sip/211|20) exten => s,n,Dial(Sip/238&Sip/209&Sip/211|20) exten => s,n,Dial(Sip/227&Sip/225&Sip/213|20) exten => s,n,Goto(ivr...

...quot;); } ! if (*argv[i]) ! envelope_sender = argv[i]; } else { print_help(); i_fatal_status(EX_USAGE, While this fixed my SEGFAULT, it still leaves the "From_" line with the default "dovecot.deliver" as the return path, something I don't want. It should be "MAILER-DAEMON" or some-such just like all the other LDAs in the case of a NULL return path. Perhaps there needs to be a new parameter so one can specify what a NULL retur...

Hey All, I''m running into a problem whereby some nodes are struggling to retrieve the metadata for files. I''ve moved all the nodes across to 0.25.1 to try and eliminate version inconsistencies though they still appear. I''ve also started using asynchronous stored configs as well. I''m wondering if this has anything to do with performance on the box and if there

...rposes.) I've been able to do this with Sieve, but it has the side effect that the messages' received and saved dates are set to the current date, and Apple Mail (at least) uses one of these to display the message date. Without the Sieve filter in place, the dates are retained based on the From_ line as I would like. Does anyone know of any way I can either - retain the date when delivering using Sieve? - systematically mark a specific set of messages as read *after* delivery instead, perhaps with doveadm(1)? (even marking *everything* read would work in this particular case. I couldn...

Hi, I wonder why the puppet agent on the server itself will not run: ---snip--- # puppet agent --test Error: Could not run Puppet configuration client: Puppet::Node does not respond to from_s; can not intern instances from text/plain Error: Could not run: can''t convert Puppet::Util::Log into Integer ---pins--- whereas the client on a test box tells me: ---snip--- # puppet agent --test Info: Retrieving plugin Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/pe_vers...

...packet. - Parsing an invalid message address like "From: (" caused an assert-crash in v1.1.4 and v1.1.5. - Folding whitespace wasn't handled correctly inside quoted-strings, causing some messages to be parsed incorrectly. - mbox: Fixed saving messages that begin with a valid From_-line. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://dovecot.org/pipermail/dovecot-news/attachments/20081030/38905e63/attachment.bin

...packet. - Parsing an invalid message address like "From: (" caused an assert-crash in v1.1.4 and v1.1.5. - Folding whitespace wasn't handled correctly inside quoted-strings, causing some messages to be parsed incorrectly. - mbox: Fixed saving messages that begin with a valid From_-line. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://dovecot.org/pipermail/dovecot-news/attachments/20081030/38905e63/attachment.bin

...rd can be now either hex or base64 encoded. The encoding is detected automatically based on the password string length. + Allow running only Dovecot master and dovecot-auth processes with protocols=none setting + deliver: -f <envelope sender> parameter can be used to set mbox From_-line's sender address + deliver: Log all mail saves and failures + Tru64 SIA passdb support. Patch by Simon L Jackson. - INBOX was listed twice in mailbox list if namespace prefix was used - INBOX-prefixed namespaces were a bit broken - kqueue: Fix 100% CPU usage - deliver: Duplicate stor...

...rd can be now either hex or base64 encoded. The encoding is detected automatically based on the password string length. + Allow running only Dovecot master and dovecot-auth processes with protocols=none setting + deliver: -f <envelope sender> parameter can be used to set mbox From_-line's sender address + deliver: Log all mail saves and failures + Tru64 SIA passdb support. Patch by Simon L Jackson. - INBOX was listed twice in mailbox list if namespace prefix was used - INBOX-prefixed namespaces were a bit broken - kqueue: Fix 100% CPU usage - deliver: Duplicate stor...

...werk.nl by rosie.bitwizard.nl (fetchmail-4.2.9 POP3 run by bitwiz) Approved: R.E.Wolff@BitWizard.nl for <wolff@localhost> (single-drop); Fri Dec 4 15:18:20 1998 Received: by haarlem-2.vuurwerk.nl (mbox bitwiz) (with Cubic Circle's cucipop (v1.31 1998/05/13) Fri Dec 4 15:18:16 1998) X-From_: linux-security-request@redhat.com Fri Dec 4 15:16:19 1998 Received: from groningen.vuurwerk.nl (IDENT:root@groningen.vuurwerk.nl [194.178.232.19]) by haarlem-2.vuurwerk.nl (8.9.1/8.9.1) with ESMTP id PAA16181 for <bitwiz@haarlem-2.vuurwerk.nl>; Fri, 4 Dec 1998 15:16:18 +0100 Received: fr...

I found something interesting via strace. lda is writing a timestamp with utime before doign the fsync, but I'm really not a C guy, so I have no idea why that's going on via procmail and not via commandline. I assume it's related to the choice of pread64 vs read. when called from commandline (working): read(0, "July 14-20, 2013\n10 courses. Bon"..., 4096) = 4096

Hi, I''m trying to add libapache2-mod-php5 as a dependency in my php5 module here is what I get info: Loading facts in raidcontroller info: Loading facts in raidcontroller debug: Format s not supported for Puppet::Resource::Catalog; has not implemented method ''from_s'' err: Could not retrieve catalog from remote server: Error 400 on SERVER: Duplicate definition: Package[libapache2-mod-php5] is already defined in file /etc/puppet/modules/php5/manifests/init.pp at line 18; cannot redefine at /etc/puppet/modules/php5/manifests/init.pp:18 on node webserver...