On Mon, 22 Sep 2003, Pat Lashley wrote:
> Return-Path doesn't exist at all until final delivery, at which point, I
> believe it is optional.
from RFC2821 (which, I realize, is smtp and not lmtp)
When the delivery SMTP server makes the "final delivery" of a
message, it inserts a return-path
But i already have the second stone in my way and the name is CYRADM. The problem is
that i have installed cyrus-imap into /opt directory, the library are into
/opt/lib/sasl2 and the include files are into /opt/include/sasl. Then, i´km trying
to compile cyradm following the documentation and i
--On Monday, September 22, 2003 19:32:07 -0700 Chris Stromsoe
<[EMAIL PROTECTED]> wrote:
Why? Return-Path is clearly a header. What's special about it as opposed
to Subject or Date or From or anything else?
It's not a standard header, as such. Subject, Date, From, and most other
headers are wr
On Mon, 22 Sep 2003, Pat Lashley wrote:
> --On Monday, September 22, 2003 19:02:11 -0700 Chris Stromsoe <[EMAIL PROTECTED]>
> wrote:
> > On Mon, 22 Sep 2003, Pat Lashley wrote:
> >
> >> Can't you get what you want using the "envelope" extension?
> >
> > Probably. "But..." the rules are being gene
--On Monday, September 22, 2003 19:02:11 -0700 Chris Stromsoe
<[EMAIL PROTECTED]> wrote:
On Mon, 22 Sep 2003, Pat Lashley wrote:
Can't you get what you want using the "envelope" extension?
Probably. "But..." the rules are being generated by smartsieve. Relying
on smartsieve to know that return
On Mon, 22 Sep 2003, Pat Lashley wrote:
> --On Monday, September 22, 2003 18:08:23 -0700 Chris Stromsoe
> <[EMAIL PROTECTED]> wrote:
>
> > From what I can tell, ...
> >
> > While there may not be much call to match against the last-hop
> > received header (unless maybe you want to take different a
--On Monday, September 22, 2003 18:08:23 -0700 Chris Stromsoe
<[EMAIL PROTECTED]> wrote:
From what I can tell, ...
While there may not be much call to match against the last-hop received
header (unless maybe you want to take different actions depending on the
origin of mail from different remote
>From what I can tell, lmtpengine.c:lmtpmod() calls lmtpengine.c:savemsg()
to read the message and get it onto disk, then lmtpd.c:deliver() to call
sieve rules and deliver the message.
lmtpengine.c:savemsg() calls fprintf() to add the Return-Path header to
the output on disk. lmtpengine.c:fill_ca
Christian Schulte schrieb:
Are the changes from 2.1.13 to 2.1.14 also in 2.2-cvs ? I setup a
test-murder with two backends, one frontend and one mupdate-master.
Everything seems to work except renaming/transferring mailboxes with
similar behaviour.
Could it be that in imapd.c => function cmd
On Tue, 23 Sep 2003, Christian Schulte wrote:
> Could it be that in imapd.c => function cmd_xfer() it should call
> mboxname_tointernal() instead of mboxname_hiersep_tointernal() ? The
> problem seems to be that imapd does not correctly transform the
> mailbox-name to the internal representation i
Luc Germain schrieb:
Actually, I'm pretty sure this has been fixed in 2.1.14 (now that I've
done the research and couldn't come up with a code path that
would cause
this ;-).
Could you try the new version and let me know?
I installed 2.1.14 on all servers in the murder, and now I can succe
On Monday 22 September 2003 15:45, Danny García Hernández wrote:
> ldd command show:
>
> [EMAIL PROTECTED] cyrus-imapd-2.2.1-BETA]$ ldd
> /usr/lib/perl5/site_perl/5.6.1/i386-linux/auto/Cyrus/IMAP/IMAP.so
> libssl.so.2 => /lib/libssl.so.2 (0x40018000)
> libcrypto.so.2 => /lib/libcryp
ldd command show:
[EMAIL PROTECTED] cyrus-imapd-2.2.1-BETA]$ ldd
/usr/lib/perl5/site_perl/5.6.1/i386-linux/auto/Cyrus/IMAP/IMAP.so
libssl.so.2 => /lib/libssl.so.2 (0x40018000)
libcrypto.so.2 => /lib/libcrypto.so.2 (0x40046000)
libc.so.6 => /lib/libc.so.6 (0x4010c000)
What does
'ldd /usr/lib/perl5/site_perl/5.6.1/i386-linux/auto/Cyrus/IMAP/IMAP.so'
show?
--Jo
On Monday 22 September 2003 15:21, Danny García Hernández wrote:
> Yes, i did it.
>
> My cyrus-imap was compiled with sasl support. Right now, i need to compile
> the perl scripts and cyradm administrat
Yes, i did it.
My cyrus-imap was compiled with sasl support. Right now, i need to compile
the perl scripts and cyradm administrative tool, and here is the the
problem. I was looking for into Makefiel.PL and changind the SASL_INC and
SASL_LIB values, the compile process finish OK, but executing c
I don't have a patch, but it should be fairly easy, just open the two
files "imap/lmtpengine.c" and "imap/message.c" and search for 'X' (quote
X quote) and comment the lines, it should be one line per file.
I am using version 2.1.13 and the lines are:
lmtpengine.c line 861
message.c line 271
Pat
Hello,
I'm trying to use cyrdeliver with another user than cyrus. So I wondered what I have
to do to achieve that?
When I run cyrdeliver with another user than cyrus I get the following error message:
command "/usr/sbin/cyrdeliver -a wojtek -m user.wojtek" exited 75 couldn't connect to
lmtp
I guess you want to specify "--with-sasl=/opt/include/sasl" or something
along that line to ./configure. Have you tried it ?
On Mon, Sep 22, 2003 at 09:28:57PM +0200, Danny García Hernández wrote:
> Ken, thank for the first answer to my fisrt problem with cyrus-imapd.
>
> But i already have the
Ken, thank for the first answer to my fisrt problem
with cyrus-imapd.
But i already have the second stone in my way and
the name is CYRADM. The problem is that i have installed cyrus-imap into /opt
directory, the library are into /opt/lib/sasl2 and the include files are
into /opt/include/
Could you show me the modification and let me test them?
Thanks
[EMAIL PROTECTED]
> Actually most of the users just set a default charset and everything
> works fine with them.
> I know it breaks the standard, but we have to do it.
>
>
> Rob Siemborski wrote:
>
> >On Mon, 22 Sep 2003, Rayed Alra
Actually most of the users just set a default charset and everything
works fine with them.
I know it breaks the standard, but we have to do it.
Rob Siemborski wrote:
On Mon, 22 Sep 2003, Rayed Alrashed wrote:
I just modified my Cyrus IMAP to make it accept 8 bit subjects without
changing it
Danny García Hernández wrote:
Hello, i´m trying to install a cyrus-imapd-2_2 server with virtual
domains support. Right now i have a server (cyrus-imap-2.1.9) with this
support, using mysql and one cyrus.conf file by domain. Also, I have
separated imap directory for each (/var/imap/example1.n
Hello, i´m trying to install a cyrus-imapd-2_2
server with virtual domains support. Right now i have a server
(cyrus-imap-2.1.9) with this support, using mysql and one cyrus.conf file
by domain. Also, I have separated imap directory for each
(/var/imap/example1.net and /var/imap/example2.n
On Mon, 22 Sep 2003, Rayed Alrashed wrote:
> I just modified my Cyrus IMAP to make it accept 8 bit subjects without
> changing it to the letter 'X', I changed these two files:
> imap/lmtpengine.c
> imap/message.c
> I tested it and it seems to work fine.
>
> My question is this change safe? I am af
I have been using lmtp and am considering using procmail instead
Will sieve work with procmail as well
Thanks
Ram
Before I start digging through the source, does lmtpd add the Return-Path
header before or after calling sieve routines? The first recipe below
works, the second does not.
# works
require ["fileinto","regex"];
if allof (header :regex "From" ".*") {
fileinto "test1";
}
#fails
require ["fi
Hello all,
I just modified my Cyrus IMAP to make it accept 8 bit subjects without
changing it to the letter 'X', I changed these two files:
imap/lmtpengine.c
imap/message.c
I tested it and it seems to work fine.
My question is this change safe? I am afraid it might break Cyrus
database format.
27 matches
Mail list logo
