search for: from_s

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 instead. Figuring

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

(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 =

Hi. I'm migrating all my mail archive (some 60 GB) from Evolution (which is really a broken piece of software) into dovecot. Now I face the problem how to do this best... Evolution (which is still a old 2.32.x version) itself uses mbox files, in a special hierarchical structure to allow subfolders and that like. It also stores it's own status info in X-Evolution and X-Evolution-Source

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

I have a Asterisk PBX System with Redhat Linux Fedora 4, Webmin version 1.400 and I am simply trying to configure into the "Extensions.conf" script an entry that will add to the "Auto-Attendant" a line that will allow a "Caller" to enter a "0" (Zero) will then ring the extension(s) of the "Operator" to speak directly with the "OPERATOR"

After recently adding the -f parameter to the call to the deliver command which is called by Postfix, I found that e-mail with a null return path (MAIL FROM:<>) was causing Dovecot deliver to SEGFAULT. I verified this by making this patch to deliver.c (notice I fixed a typo here, too): *** deliver.c.orig Fri Oct 13 07:32:28 2006 --- deliver.c Fri Oct 27 21:26:08 2006 ***************

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

I'm trying to mark several hundred thousand messages as read as they are delivered via dovecot-lda(1). (I'm importing some mail from another format for migration purposes.) 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.

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_versi...

http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz.sig The invalid message address parsing bug is pretty important since it allows a remote user to send broken mail headers and prevent the recipient from accessing the mailbox afterwards, because the process will always just crash trying to parse the header. This is assuming that the IMAP

http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.6.tar.gz.sig The invalid message address parsing bug is pretty important since it allows a remote user to send broken mail headers and prevent the recipient from accessing the mailbox afterwards, because the process will always just crash trying to parse the header. This is assuming that the IMAP

I've still over 200 mails unread in the mailing list, and important things left in TODO. This release is an improvement over rc7 anyway, hopefully I'll have time to fix the rest soon. http://dovecot.org/releases/dovecot-1.0.rc8.tar.gz http://dovecot.org/releases/dovecot-1.0.rc8.tar.gz.sig * GSSAPI: Changed POP3 service name to "pop", which is what the standard says *

I've still over 200 mails unread in the mailing list, and important things left in TODO. This release is an improvement over rc7 anyway, hopefully I'll have time to fix the rest soon. http://dovecot.org/releases/dovecot-1.0.rc8.tar.gz http://dovecot.org/releases/dovecot-1.0.rc8.tar.gz.sig * GSSAPI: Changed POP3 service name to "pop", which is what the standard says *

Ran into a weird problem, and this seemed a good forum to toss it out into -- if I've gaffed, please let me know. Just upgraded my RH5.0 box to RH5.2. Went well, worked nearly seamlessly. When running 5.0, though, I'd installed the opie-fied ftpd that comes with the most recent opie package (ftp://ftp.inner.net/pub/opie/opie-2.32.tar.gz) and had it work without a hitch. I'd also

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 webserver1...