Dear all,
i have a mail server vpopmail.
Now, i want to copy from each message to a directory.i find a way to do
it.
i put following line in .qmail-default :
|formail -X ~/text.txt
Of course above line is test.Given line doesn't retrieves Return* header
field.
My question:
How i retrieve
On Monday 18 May 2009 00:58:40 Timo Sirainen wrote:
On Wed, 2009-05-06 at 13:16 +0200, Stefan Roese wrote:
I'm experiencing a problem with some mails in deliver. Here the logged
error message:
deliver(ste...@roese.nl): 2009-05-06 11:57:36 Panic: file
index-mail-headers.c: line 141
Timo Sirainen schrieb:
On Mon, 2009-05-18 at 01:40 +0200, Robert Schetterer wrote:
could you include an example for having
acl_shared_dict in sql ?
See if you can get it working with these kind of settings:
http://www.dovecot.org/list/dovecot/2009-April/038922.html
Thanks Timo, i will
Just a comment about the documentation for postfix integration when
using receipient delimiter and delivery of user+...@domain.ext to
u...@domain:
http://wiki.dovecot.org/LDA/Postfix
I had some issues to get this working, so thought I'd share my
experience. Dovecot version 1.2.rc3. Postfix
John Fawcett schrieb:
Just a comment about the documentation for postfix integration when
using receipient delimiter and delivery of user+...@domain.ext to
u...@domain:
http://wiki.dovecot.org/LDA/Postfix
I had some issues to get this working, so thought I'd share my
experience.
John Fawcett schrieb:
Just a comment about the documentation for postfix integration when
using receipient delimiter and delivery of user+...@domain.ext to
u...@domain:
http://wiki.dovecot.org/LDA/Postfix
Hi John, just for info, in my test server i use
Hi again,
I am having some troubles sending all data to a file. When I finish to send all
data to a file, I tried to open it and the file is corrupted.
The first think I noticed is that all chars are capitalized what destroy all
the file format.
Where are the chars capitalized?
Any other idea
On M 18 May, 2009, at 01:00 , Timo Sirainen wrote:
On Mon, 2009-05-18 at 00:57 +0200, Giuliano Gavazzi wrote:
There's only one point that escapes me, why perform the conversion
when migrating (using the --convert option) given that on the system
where I did not perform it the flags have been
john...@erba.tv schrieb:
John Fawcett schrieb:
Just a comment about the documentation for postfix integration when
using receipient delimiter and delivery of user+...@domain.ext to
u...@domain:
http://wiki.dovecot.org/LDA/Postfix
Hi John, just for info, in my test server i use
Hi John,
no i didnt wrote that, i only have u...@domain.ext
layout in use currently in my test servers
--
Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
Hi Robert
I probably didn't make it clear. The problem with the
published syntax is that it does not work for
receipient
john...@erba.tv schrieb:
Hi John,
no i didnt wrote that, i only have u...@domain.ext
layout in use currently in my test servers
--
Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
Hi Robert
I probably didn't make it clear. The problem with the
published syntax is that it
On May 18, 2009, at 6:42 AM, Rui Carneiro wrote:
I am having some troubles sending all data to a file. When I finish
to send all data to a file, I tried to open it and the file is
corrupted.
The first think I noticed is that all chars are capitalized what
destroy all the file format.
On May 18, 2009, at 3:56 AM, John Fawcett wrote:
Can anyone see a reason for not using always ${us...@${domain}
instead of ${us...@${nexthop}?
${domain} is a somewhat recent addition to Postfix. I guess the docs
could say to use ${domain} instead of ${nexthop} if Postfix is newer
than X
Hi Scott,
One could always run the mailstore on LVM and then you could snapshot the
mount and then fsck it while still technically in use. It would probably slow
down the filesystem, but it is still live.
Uhm, and then you have a nice and fsck'd snapshot, but your live filesystem
will still be
${domain} is a somewhat recent addition to Postfix. I guess the docs
could say to use ${domain} instead of ${nexthop} if Postfix is newer than
X (should look up what version added that).
${domain} parameter has been added starting with Postfix 2.5, which means
that people using enterprise
I use public namespace for group mailboxes. If someone sends email
from this mailbox , MTA detects it and delivers copy of that message
to mailbox/Sent folder, to keep history of all messages available for
every group member. I'd like to set Seen flag on all messages that
dovecots deliver puts
Citando Timo Sirainen t...@iki.fi:
Nope. If you still see corruption, try with some simple test mails and
see if it's adding garbage, losing contents or adding more content.
I tried something more advanced than that. I hexdumped my pdf test file and on
the first line I get:
25 50 44
Matthijs Kooijman wrote:
Hi Scott,
One could always run the mailstore on LVM and then you could snapshot the
mount and then fsck it while still technically in use. It would probably slow
down the filesystem, but it is still live.
Uhm, and then you have a nice and fsck'd snapshot, but your
On Mon, 2009-05-18 at 17:35 +0100, Rui Carneiro wrote:
I think binary data is being corrupted anywhere before
fts_backend_build_more() and I don't have any idea where.
All the data comes from lib-mail/message-decoder.c. Hmm. Looks like it
tries to force giving only valid UTF-8 output. I guess
So far the crashes continue, but I haven't seen anything in particular
that sets it off. I'll trying coming up with a way of reproducing it and
get back to you if I can. In the meantime, I'm upgrading to the latest
version to see if anything changes.
Timo Sirainen wrote:
On Thu, 2009-04-23
On May 17, 2009, at 2:42 PM, Timo Sirainen wrote:
On Wed, 2009-05-13 at 15:04 -0400, Jonathan Siegle wrote:
Having some problems compiling on AIX 5.3 with IBM vac version 8.
Programs that I had problems building:
test-mail
test-imap
test-index
Should be fixed in hg now?
Yes fixed. Is it
On Mon, 2009-05-18 at 13:57 -0400, Jonathan Siegle wrote:
Yes fixed. Is it to early to be reporting stuff like this?
No, it's not too early. Better early than late :)
I now have this error(rev 9321:4c4b95def1fa):
ssl-proxy.c, line 12.5: 1506-343 (S) Redeclaration of ssl_proxy_new
On Mon, May 18, 2009 at 6:30 PM, Max Ivanov ivanov.ma...@gmail.com wrote:
I use public namespace for group mailboxes. If someone sends email
from this mailbox , MTA detects it and delivers copy of that message
to mailbox/Sent folder, to keep history of all messages available for
every group
On May 18, 2009, at 2:02 PM, Timo Sirainen wrote:
On Mon, 2009-05-18 at 13:57 -0400, Jonathan Siegle wrote:
Yes fixed. Is it to early to be reporting stuff like this?
No, it's not too early. Better early than late :)
I now have this error(rev 9321:4c4b95def1fa):
ssl-proxy.c, line 12.5:
mr.maX wrote:
${domain} is a somewhat recent addition to Postfix. I guess the docs
could say to use ${domain} instead of ${nexthop} if Postfix is newer
than X (should look up what version added that).
${domain} parameter has been added starting with Postfix 2.5, which
means that people
Timo Sirainen wrote:
On Sun, 2009-02-22 at 12:49 +0100, e-frog wrote:
Trying 1.2.beta1 with expire plugin currently:
When I set mail_location = maildir:~/.maildir the expire plugin doesn't
delete messages.
Should be fixed in hg now.
My guess is that mail_location is not respected by
Hi everyone:
I use dovecot only as the imap server, For smtp and pop3, I use apache james.
The dovecot version: 1.1.14
And the configuration is :
protocols: imap
ssl_disable: yes
login_dir: /var/run/dovecot/login
login_executable: /usr/libexec/dovecot/imap-login
mail_location:
I'm current maintainer of dovecot packages in ALTLinux distro and I
plan to make possible to install multiple dovecot versions
side-by-side (1.0, 1.1, 1.2) to make upgrade process easier and more
robust.
Is there any consequences of doing that? I worry about locking
maildirs and mboxes, does
On May 19, 2009, at 1:05 AM, Max Ivanov wrote:
I'm current maintainer of dovecot packages in ALTLinux distro and I
plan to make possible to install multiple dovecot versions
side-by-side (1.0, 1.1, 1.2) to make upgrade process easier and more
robust.
So you mean actually running both at the
29 matches
Mail list logo
