OK, I'm stumped: how on earth is the 2.4 sieveshell utility
actually supposed to be able to talk to a 2.4 timsieved server?
We're using cyrus-imapd-2.4.17-8.el7_1 and cyrus-sasl-2.1.26-20.el7_2
on Red Hat Enterprise Linux 7.3, using Active Directory as our Keberos
KDC. The issue we&#x
Dan,
You nailed it. Mere presence of sasldb plugin makes it work.
The code doesn't look kosher to me though.
In sasl_server_new() there's a line:
serverconn->sparams->canon_user = &_sasl_canon_user_lookup;
which unconditionally set canon_user callback to the function that performs both
canonical
In the absence of an [sasl_]auxprop_plugins statement, all plugins will be
queried. For example, running pluginviewer (or saslpluginviewer on debian)
should typically list sasldb if it's installed on your system.
The canon_user plugins and auxprop plugins are coded within the same code,
and so ar
use admin user.
i also tried to change to sasl_pwcheck_method to 'alwaystrue' to make sure no
authentication problems stand in the way, but that also didn't help.
I'm at loss now. Anymore troubleshooting clues?
Thanks,
Michael
On Sunday, November 20, 2016 07:34:58 PM Andrew Morg
2:01:57 rway-imap-vm saslauthd[1169]: pam_userdb(sieve:auth): user
> > 'proxyadmin' granted access
> > Nov 21 12:01:57 rway-imap-vm sieve[21483]: badlogin: localhost[127.0.0.1]
> > PLAIN no mechanism available
> >
> > the same happens if I use admin user.
> > i al
57 rway-imap-vm sieve[21483]: badlogin: localhost[127.0.0.1]
> > PLAIN no mechanism available
> >
> > the same happens if I use admin user.
> > i also tried to change to sasl_pwcheck_method to 'alwaystrue' to make sure
> > no authentication probl
;t help.
I'm at loss now. Anymore troubleshooting clues?
Thanks,
Michael
On Sunday, November 20, 2016 07:34:58 PM Andrew Morgan wrote:
This works for me under v2.4.18. I'm able to run sieveshell against a
frontend or backend authenticating as a cyrus "admins" user or a
"pro
loss now. Anymore troubleshooting clues?
Thanks,
Michael
On Sunday, November 20, 2016 07:34:58 PM Andrew Morgan wrote:
> This works for me under v2.4.18. I'm able to run sieveshell against a
> frontend or backend authenticating as a cyrus "admins" user or a
> "proxys
This works for me under v2.4.18. I'm able to run sieveshell against a
frontend or backend authenticating as a cyrus "admins" user or a
"proxyservers" user (on the backend).
Against a frontend:
# sieveshell -u morgan -a cyrus imap.onid.oregonstate.edu
connecting to
ay, November 17, 2016 06:30:18 PM Michael Ulitskiy via Info-cyrus
wrote:
> Hello,
>
> I'm playing with cyrus-imap 2.5.10 and cyrus-sasl 2.1.26.
> i'm trying to use sieveshell to setup users sieve scripts, but since
> i don't know users passwords i want to use a special u
Hello,
I'm playing with cyrus-imap 2.5.10 and cyrus-sasl 2.1.26.
i'm trying to use sieveshell to setup users sieve scripts, but since
i don't know users passwords i want to use a special user for authentication
and authorize as the target user.
Here's what I have.
imapd.con
OK, hearing no response to my query on the bug status of:
"Error in Cyrus::SIEVE::managesieve package in the cyrus 2.4.11 and
later code. The "better response codes for timsieved" lead to
problems in the perl package if you try to "get" an nonexistent
script.managesieve and perl exits with
t;get" an nonexistent
> script:
>
> sieveshell ...
> >/ get nonexistant
> /Bad protocol from MANAGESIEVE server: expected RPARAN
>
> The perl package expects quoted strings inside the parantheses and
> these quotes are missing.
>
> There are two possible solutions: f
access the mailboxes.
However, cyradmin and sieveshell give me an authentication error.
Authentication runs with sasl and DIGEST-MD5
Thanks in advance
Harry
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https
Hello,
I've some difficulties with my installation, specially with sieveshell.
O.K., just have a look on my site:
intranet : 10.0.10.0/24
DMZ : 10.0.0.0/24
My IMAP-server is based on DMZ-site on my host vml70 (10.0.0.70):
# netstat -penlut
Active Internet connections (only se
On Fri, Dec 10, 2010 at 03:45:55PM +, Kenneth Marshall wrote:
> On Fri, Dec 10, 2010 at 04:33:43PM +0100, Stefan Jurisch wrote:
> > Hi there,
> >
> > On Fri, Dec 10, 2010 at 03:00:31PM +, Dan White wrote:
> > > It sounds like you are authenticating or proxying as an admin, which
> > > wou
On Fri, Dec 10, 2010 at 04:33:43PM +0100, Stefan Jurisch wrote:
> Hi there,
>
> On Fri, Dec 10, 2010 at 03:00:31PM +, Dan White wrote:
> > It sounds like you are authenticating or proxying as an admin, which
> > would
> >
Hi there,
On Fri, Dec 10, 2010 at 03:00:31PM +, Dan White wrote:
> It sounds like you are authenticating or proxying as an admin, which
> would
>
> explain what you're seeing.
> [...]
nge Appliance Edition (OXAE).
> >First, everything was ok, but suddenly that problem appeared and I don't
> >know, how to fix it:
> >
> >Whenever I use sieveshell to upload a script for a user without knowing
> >his creds, I do as follows:
> >
> > sie
eared and I don't
>know, how to fix it:
>
>Whenever I use sieveshell to upload a script for a user without knowing
>his creds, I do as follows:
>
> sieveshell --user u...@domain.net --authname cyrus localhost
>
>The normal behaviour, which I know, is that I upload
Hello,
I've got a weird problem with the timsieved of above mentioned version of cyrus.
This cyrus is part of a so called Open-Xchange Appliance Edition (OXAE).
First, everything was ok, but suddenly that problem appeared and I don't
know, how to fix it:
Whenever I use sieveshell t
sieveshell seems to be broken ... ?
# sieveshell --user=scra...@hub.org localhost
connecting to localhost
Please enter your password:
Bad protocol from MANAGESIEVE server: lost connection
But everything seems to be responding fine:
# telnet localhost sieve
Trying ::1...
Trying 127.0.0.1
OBATA Akio wrote, at 12/24/2008 09:19 AM:
> Hi,
>
> On Wed, 24 Dec 2008 23:09:27 +0900, Jorey Bump wrote:
>
>> This is the first time I've used sieveshell since upgrading to Cyrus
>> IMAPd 2.3.13. It will prompt me for my password, but once I log in, it
>> s
Hi,
On Wed, 24 Dec 2008 23:09:27 +0900, Jorey Bump wrote:
> This is the first time I've used sieveshell since upgrading to Cyrus
> IMAPd 2.3.13. It will prompt me for my password, but once I log in, it
> simply hangs without any feedback or providing a '>' command pro
This is the first time I've used sieveshell since upgrading to Cyrus
IMAPd 2.3.13. It will prompt me for my password, but once I log in, it
simply hangs without any feedback or providing a '>' command prompt.
According to the log, login was successful:
sieve[29093]: login: l
I recently moved my Cyrus imapd from RHEL 4 Update 6 to RHEL 5.2
The only problem found so far after the move is with sieveshell, the "-a"
option does not work any more. This used to work as expected:
sieveshell -a cyrusadmin -u user localhost
On the new server this seems to wor
Mohacsi Janos wrote:
> Dear All,
> I have strange sieveshell error after upgrading to cyrus imapd
> 2.3.9:
> I no longer can use sieveshell to upgrade the sieve rules. I got the
> following error:
>
>
> [EMAIL PROTECTED]> sieveshell mail.domain.hu:2000
> con
On Wed, 26 Sep 2007, Mohacsi Janos wrote:
> Dear All,
> I have strange sieveshell error after upgrading to cyrus imapd
> 2.3.9:
> I no longer can use sieveshell to upgrade the sieve rules. I got the
> following error:
>
>
> [EMAIL PROTECTED]> sieveshell mail.
Dear All,
I have strange sieveshell error after upgrading to cyrus imapd
2.3.9:
I no longer can use sieveshell to upgrade the sieve rules. I got the
following error:
[EMAIL PROTECTED]> sieveshell mail.domain.hu:2000
connecting to mail.domain.hu:2000
unable to connect to server at /
Hi!
I'm using cyrus 2.2.12 on my academic server and evrything is working great.
:-)
My only little problem is the following:
I can use correctly the sieveshell command with ALL users
except ONE user for which I got:
# sieveshell --user=someuser --auth=cyrus localhost
connecti
elational comparator-i;ascii-numeric regex"
>> S: "STARTTLS"
>> S: OK
>> Please enter your password:
>> C: AUTHENTICATE "PLAIN" {20+}
>> AGN5cnVzAG1haGFkZXY=
>> S: NO "Authentication Error"
>> Authentication failed. generic f
imapflags notify
subaddress relational comparator-i;ascii-numeric regex"
S: "STARTTLS"
S: OK
Please enter your password:
C: AUTHENTICATE "PLAIN" {20+}
AGN5cnVzAG1haGFkZXY=
S: NO "Authentication Error"
Authentication failed. generic failure
Security strength factor
baddress relational comparator-i;ascii-numeric regex"
S: "STARTTLS"
S: OK
Please enter your password:
C: AUTHENTICATE "PLAIN" {20+}
AGN5cnVzAG1haGFkZXY=
S: NO "Authentication Error"
Authentication failed. generic failure
Security strength factor: 0
--
Rudy Gevaert wrote:
I don't have any windows machine(s) but can't you just configure the
windows machine to use PLAIN+tls?
I've checked this with one of our helpdesk people and you can't select
tls in outlook. So you are stuck with enabling LOGIN if you want to use
the normal imap port
Am Monday 11 September 2006 21:14 schrieb Andrew Morgan:
> > i have the same problem than u
> > but when i remove the LOGIN mechanism windows users can't logged anymore
> > :( is there a way to remove the LOGIN mechanism only for sieve
> > connection?
>
> The Cyrus-SASL docs state:
>
>The LOGI
On Mon, 11 Sep 2006, Eric Doutreleau wrote:
Rudy Gevaert a écrit :
Andreas Winkelmann wrote:
Ok, please remove the "LOGIN" Mechanism from sasl_mech_list.
# Authentication configuration
sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAIN LOGIN "LOGIN" is not able to do authorization (-a
cyr
Eric Doutreleau wrote:
i have the same problem than u
but when i remove the LOGIN mechanism windows users can't logged anymore :(
is there a way to remove the LOGIN mechanism only for sieve connection?
I don't have any windows machine(s) but can't you just configure the
windows machine to u
Am Monday 11 September 2006 16:19 schrieb Eric Doutreleau:
> >> Ok, please remove the "LOGIN" Mechanism from sasl_mech_list.
> >>
> >> # Authentication configuration
> >> sasl_pwcheck_method: saslauthd
> >> sasl_mech_list: PLAIN LOGIN
> >> "LOGIN" is not able to do authorization (-a cyrus -u user)
Eric Doutreleau schrieb:
Rudy Gevaert a écrit :
Andreas Winkelmann wrote:
Ok, please remove the "LOGIN" Mechanism from sasl_mech_list.
# Authentication configuration
sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAIN LOGIN "LOGIN" is not able to do authorization
(-a cyrus -u user). Only
Rudy Gevaert a écrit :
Andreas Winkelmann wrote:
Ok, please remove the "LOGIN" Mechanism from sasl_mech_list.
# Authentication configuration
sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAIN LOGIN
"LOGIN" is not able to do authorization (-a cyrus -u user). Only
PLAIN and DIGEST-MD5 can do
Andreas Winkelmann wrote:
Ok, please remove the "LOGIN" Mechanism from sasl_mech_list.
# Authentication configuration
sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAIN LOGIN
"LOGIN" is not able to do authorization (-a cyrus -u user). Only PLAIN and
DIGEST-MD5 can do that. Because you use
Am Saturday 09 September 2006 11:37 schrieb Rudy Gevaert:
> Andreas Winkelmann wrote:
> > Am Friday 08 September 2006 14:51 schrieb Rudy Gevaert:
> >> I have this strange problem with sieveshell. (I'm using virtual
> >> domains, and unix seperator.) I can a
Andreas Winkelmann wrote:
Am Friday 08 September 2006 14:51 schrieb Rudy Gevaert:
I have this strange problem with sieveshell. (I'm using virtual
domains, and unix seperator.) I can authenticate as an admin user and
authorize as a normal user with cyradm.
However with sieveshell this d
Am Friday 08 September 2006 14:51 schrieb Rudy Gevaert:
> I have this strange problem with sieveshell. (I'm using virtual
> domains, and unix seperator.) I can authenticate as an admin user and
> authorize as a normal user with cyradm.
>
> However with sieveshell this do
Hello,
I have this strange problem with sieveshell. (I'm using virtual
domains, and unix seperator.) I can authenticate as an admin user and
authorize as a normal user with cyradm.
However with sieveshell this doesnt work the way it should:
Here I log in and first give the wrong pass
Op zaterdag 18 maart 2006 14:50, schreef Andreas Hasenack:
> Em Sáb 18 Mar 2006 04:53, Johan Barelds escreveu:
> > Hi Andreas,
> >
> > Thanks for that tip!
> > Any idea where i can remove the other mechanisms not wanted?
> > Is this on the cyrus side or the pam etc. side?
>
> The mechanisms are ins
Em Sáb 18 Mar 2006 04:53, Johan Barelds escreveu:
> Hi Andreas,
>
> Thanks for that tip!
> Any idea where i can remove the other mechanisms not wanted?
> Is this on the cyrus side or the pam etc. side?
The mechanisms are installed usually under /usr/lib/sasl2. Another option
would be to use mech_
Op zaterdag 18 maart 2006 02:05, schreef Andreas Hasenack:
> Em Sex 17 Mar 2006 20:15, Johan Barelds escreveu:
> > Hi All,
> >
> > When i login with sieveshell i have to give my password three times..?!
> > After then i am succesfully logged in.
> >
Em Sex 17 Mar 2006 20:15, Johan Barelds escreveu:
> Hi All,
>
> When i login with sieveshell i have to give my password three times..?!
> After then i am succesfully logged in.
> Anyone any clues?
>
> Thanks!
> ----
> al
Hi All,
When i login with sieveshell i have to give my password three times..?!
After then i am succesfully logged in.
Anyone any clues?
Thanks!
alcatraz:/tmp # sieveshell -u jbarelds -a jbarelds localhost
connecting to localhost
Please enter
>
> I figure that there's a problem with my configuration of sieve
> somewhere. I attempt to use sieveshell using the cyrus user that
> successfully works as described above.
>
> cressida:/var/lib/cyrus# sieveshell -u cyrus localhost
>
> It prompts me for m
and imtest. So far so good.
I entered the details into my GOsa configuration put it complains with
an error:
Can't log into SIEVE server. Server says ".
I figure that there's a problem with my configuration of sieve
somewhere. I attempt to use sieveshell using the cyrus user that
suc
h "--authname" I can use sieveshell/sivtest unix account
independently.]
With "--authname=aname" after the proxyauth with the ldapdb-saslid
proxyauth switches to this "aname", but then no switch to
"--user=username" is done.
If I want to switch to "us
On Fri, 12 Aug 2005 14:06 , Hans Moser <[EMAIL PROTECTED]:
Hi!
I use IMAPd with SASL ldapdb.
Why could I (only) connect to the server by sieveshell with
# sieveshell --authname=username hostname
?
# sieveshell --user=username hostname
ends up in
"unable to connect to server at
Hi!
I use IMAPd with SASL ldapdb.
Why could I (only) connect to the server by sieveshell with
# sieveshell --authname=username hostname
?
# sieveshell --user=username hostname
ends up in
"unable to connect to server at /usr/bin/sieveshell line 169,
line 1."
[ #cyradm --use
27;
scripts through timsieved.
Our mailserver is running Cyrus imap 2.2.8 on linux, and the
administrative user is 'cyrus'. I was thinking that:
sieveshell -u -a cyrus localhost
(on the mailserver, using the password of cyrus) would give me access to
the scripts of , but it gives acces
Is there any eta (weeks, months, oo) on making sieveshell be able to use
START TLS?
Does somebody know of another text-mode tool to manage sieve scripts
which does have start tls support?
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List
On Wed, 2005-03-16 at 18:25 +, Cameron Murdoch wrote:
> >
>
> Not sure if it will solve this problem, (not even sure what the problem
> is :) but specifying both -a and -u has solved some issues for me in the
> past:
>
> sieveshell -a Alec -u Alec
>
> They
Craig White wrote:
On Tue, 2005-03-15 at 19:41 -0600, Dave McCracken wrote:
--On Tuesday, March 15, 2005 17:48:32 -0700 Craig White
<[EMAIL PROTECTED]> wrote:
I want to insert sieve scripts for users via sieveshell but I can't seem
to get that done...
sieveshell -u Alec loc
I am having similar problems, and found out by stracing the timsieved
that the sieveshell connects to, that sieveshell doesn't respect ( at
least in my case) what I pass as -a. If I run as root, it will try to
authenticate as root, if I run as user, then it works fine. -a
apparently h
On Tue, 2005-03-15 at 19:41 -0600, Dave McCracken wrote:
> --On Tuesday, March 15, 2005 17:48:32 -0700 Craig White
> <[EMAIL PROTECTED]> wrote:
>
> > I want to insert sieve scripts for users via sieveshell but I can't seem
> > to get that done...
> >
> &g
On Tue, 2005-03-15 at 19:41 -0600, Dave McCracken wrote:
> --On Tuesday, March 15, 2005 17:48:32 -0700 Craig White
> <[EMAIL PROTECTED]> wrote:
>
> > I want to insert sieve scripts for users via sieveshell but I can't seem
> > to get that done...
> >
> &g
On Tue, 2005-03-15 at 19:41 -0600, Dave McCracken wrote:
> --On Tuesday, March 15, 2005 17:48:32 -0700 Craig White
> <[EMAIL PROTECTED]> wrote:
>
> > I want to insert sieve scripts for users via sieveshell but I can't seem
> > to get that done...
> >
> &g
--On Tuesday, March 15, 2005 17:48:32 -0700 Craig White
<[EMAIL PROTECTED]> wrote:
I want to insert sieve scripts for users via sieveshell but I can't seem
to get that done...
sieveshell -u Alec localhost
will try to authenticate as root, not as Alec and I can't su to Alec
since
Users have /bin/false for shells
I want to insert sieve scripts for users via sieveshell but I can't seem
to get that done...
sieveshell -u Alec localhost
will try to authenticate as root, not as Alec and I can't su to Alec
since he doesn't have a usable shell. Is there any ot
Hi Robert,
you're right. I think I have overseen version 5.8.5 or the download
was to long ago. But your hint regarding the perl version was helpful
because with the self compiled perl version 5.8.6 sieveshell is now
working fine.
Thank you, Thomas
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
I I have perl 5.8.5. I don't know about 5.8.3 and when I looked around
I couldn't find it on Sunfreeware any more, but under 5.8.5 it states:
Important Note - Solaris 9 comes with a slightly earlier version of perl
in /usr/bin. You may wish to use this version rather than the version on
sunfre
Robert Scussel wrote:
This might be a shot in the dark, but having recently battled through
some quirks on Solaris 9, make sure that your perl binary is one that
was compiled on the Solaris box with gcc ( unless of course you actually
have the sun compiler and compiled cyrus with it ). The one f
is used to compile cyrus with some gcc versions, and if perl is
compiled with cc it will not include libgcc (where __eprintf comes from)
In this case I would expect your perl module to not load at all, though,
in sieveshell.
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http
re. I use saslauthd with method pam
for authentication. The "user accounts" for pam
are from a Windows 2003 Server via Samba/Winbind.
I'm running Cyrus-2.2.12 on Solaris 9 as well and we use a different
authentication method (namely ldap) and just wanted to let you know
that sie
d.
I'm running Cyrus-2.2.12 on Solaris 9 as well and we use a different
authentication method (namely ldap) and just wanted to let you know that
sieveshell itself works fine on Solaris 9.
Regards, Paul Boven.
Hi Paul,
thank you for your reply. When your sieveshell works on
Solaris 9 then the
Hello all,
I'm running Cyrus-Imapd 2.2.12 on Solaris 9.
I compiled it from source with gcc 3.2.2 from
Sunfreeware. I use saslauthd with method pam
for authentication. The "user accounts" for pam
are from a Windows 2003 Server via Samba/Winbind.
Everything works so far except siev
Hi,
--On Samstag, 16. Oktober 2004 17:59:45 Uhr MESZ +0200 Tarjei Huse
<[EMAIL PROTECTED]> wrote:
tor, 07,.10.2004 kl. 16.40 +0200, skrev Sebastian Hagedorn:
Hi,
Hi, this is a very nice script. Would you mind uploading it to the Cyrus
WIKI? Tarjei
sorry for not replying earlier. You see, it's not
tor, 07,.10.2004 kl. 16.40 +0200, skrev Sebastian Hagedorn:
> Hi,
Hi, this is a very nice script. Would you mind uploading it to the Cyrus WIKI?
Tarjei
> --On Mittwoch, 6. Oktober 2004 15:25 Uhr -0700 Rob Tanner
> <[EMAIL PROTECTED]> wrote:
>
> > My other thought was to write my own, using the C
Hi,
What is the easiest way to install only sieveshell and the perl
libraries on a user system?
I don't need the complete cyrus package of course (and ./configure won't
even finish because sasl2 is not installed either so there is no
makefile...) but I want my users to have sieveshel
Sebastian,
Thanks! Between the code you sent and the sieveshell code, I was able to
figure out I need and write a perl script to upload sieve scripts for all the
affected users.
-- Rob
--On Thursday, October 07, 2004 04:40:39 PM +0200 Sebastian Hagedorn
<[EMAIL PROTECTED]> wrote:
Hi,
--On Mittwoch, 6. Oktober 2004 15:25 Uhr -0700 Rob Tanner
<[EMAIL PROTECTED]> wrote:
My other thought was to write my own, using the Cyrus::SIEVE::managesieve
package, but there's no helpful documentation that I could find.
Has anyone resolved this problem?
well, we have a script that does us
s are
concerned.
My problem is, how do I use sieveshell in batch mode. While I can certainly
upload scripts one at a time, there appears to be no way to feed sieveshell
the authentication password on the command line and thus no way to repeatedly
invoke sieveshell from a script (unless I'
On Tue, 10 Aug 2004, Rob Tanner wrote:
Unfortunately, it doesn't look like sieveshell does what I was hoping for.
I'm looking for some tool that will allow me, as the administrator, to manage
other users' sieve space (add/modify scripts, etc). Do you have any
suggestions?
Sadly
On Tue, 2004-08-10 at 10:41, Rob Tanner wrote:
> --On Tuesday, August 10, 2004 10:23:16 AM -0700 Joakim Ryden
> <[EMAIL PROTECTED]> wrote:
>
> >
> > What do your logs say when you try it?
> >
> > --Jo
>
> Duh! I didn't even think to check th
st 10, 2004 10:23:16 AM -0700 Joakim Ryden
>>>
>>> <[EMAIL PROTECTED]> wrote:
>>> > What do your logs say when you try it?
>>> >
>>> > --Jo
>>>
>>> Duh! I didn't even think to check there. Here are two examples,
> What do your logs say when you try it?
>> >
>> > --Jo
>>
>> Duh! I didn't even think to check there. Here are two examples, the
>> sieveshell that fails followed by a smartsieve login that worked. In
>> bothe cases I logged in (or tried to login in) as the
On Tuesday 10 August 2004 10:41 am, Rob Tanner wrote:
> --On Tuesday, August 10, 2004 10:23:16 AM -0700 Joakim Ryden
>
> <[EMAIL PROTECTED]> wrote:
> > What do your logs say when you try it?
> >
> > --Jo
>
> Duh! I didn't even think to check there.
--On Tuesday, August 10, 2004 10:23:16 AM -0700 Joakim Ryden
<[EMAIL PROTECTED]> wrote:
>
> What do your logs say when you try it?
>
> --Jo
Duh! I didn't even think to check there. Here are two examples, the
sieveshell that fails followed by a smartsieve login that wo
ing (cyrus-imap v2.2.3) and a php application to
> >> allow users some limited access for setting up forwarding and vacation
> >> scripts. I am looking at sieveshell as a possible tool to do
> >> administrative maintenance, but whenever I try to invoke it, it fails.
>
ess for setting up forwarding and vacation
>> scripts. I am looking at sieveshell as a possible tool to do
>> administrative maintenance, but whenever I try to invoke it, it fails.
>>
[...]
>
> Do you have an entry for sieve in /etc/services?
>
> --Jo
Yes. O
On Tuesday 10 August 2004 09:31 am, Rob Tanner wrote:
> Hi,
>
> I have sieve up and running (cyrus-imap v2.2.3) and a php application to
> allow users some limited access for setting up forwarding and vacation
> scripts. I am looking at sieveshell as a possible tool to do
&
Hi,
I have sieve up and running (cyrus-imap v2.2.3) and a php application to
allow users some limited access for setting up forwarding and vacation
scripts. I am looking at sieveshell as a possible tool to do administrative
maintenance, but whenever I try to invoke it, it fails.
I have tried
don't know how to login the server.
The manpage told me i should use 'sieveshell'.
But what is the admin's name of the server.
And how to configure the password.
I am blind now.
Thanks in advance!
Penghui Wang
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http:/
I've read through the archives and I see a lot of discussion similar
to my problem, but I haven't found anything that works yet. My Cyrus
V2.2.3 installation works fine. I can run cyradm with no problem and
imap logins work fine, but I can't get sieveshell or sivtest t
y use plain authentification as mech - sieveshell shows the
error from line 174 (couldn't connect to a server) and
the auth.log has an error entry from perl: no possible mech.
Thanks for your help,
Sascha
localhost:~# cyradm --user cyrus localhost
IMAP Password:
loca
Hi,
I'm writing a web-based sieve administration tool, and for that, I
wanted to use sieveshell to list/install/activate/etc.. sievescripts on
a per user basis.
After some debug I figured out, that sieveshell doesn't support properly
the --exec option. I've straced it, and fou
fully understand what it does). I had tried the other method (setting
ac_cv_func_getnameinfo=no) before but to no avail.
Sieveshell and sivtest now give satisfactory results.
I thank you all.
/markus
ps: Strange thing though, that the above thread didn't show up in either
google's or cmu.edu's search.
te as expected (it took some time to find out about
> > > the new bytecode format of sieve scripts, though).
> > >
> > > The only thing that keeps failing is sieve access via the sieve socket.
> > >
> > > # sivtest -u user localhost (with or without further op
code format of sieve scripts, though).
> >
> > The only thing that keeps failing is sieve access via the sieve socket.
> >
> > # sivtest -u user localhost (with or without further options)
> > always results in:
> > # failure: SASL initialization
> >
> >
.
# sivtest -u user localhost (with or without further options)
always results in:
# failure: SASL initialization
# sieveshell -u user localhost
has sieveshell die with:
# unable to connect to server at /usr/local/bin/sieveshell line 174
When I enter a "print $!" in sieveshell after t
(with or without further options)
always results in:
# failure: SASL initialization
# sieveshell -u user localhost
has sieveshell die with:
# unable to connect to server at /usr/local/bin/sieveshell line 174
When I enter a "print $!" in sieveshell after the call to
sieve_get_handle I
Hi,
when I start sieveshell it asks me for the password, but alas I can't
login. it asks me a couple of times for the password.
what I can see in the auth.log is:
Dec 18 12:11:24 vwclub sieve[20809]: Password verification failed
Dec 18 12:11:26 vwclub sieve[20809]: no secret in database
D
Hi i got nearly the same problem.I can auth against POP and IMAP but not
against sieveshell when i try i allways get:
Dec 10 11:55:42 mail timsieved[6167]: cross-realm login
[EMAIL PROTECTED] denied
Dec 10 11:55:42 mail perl: No worthy mechs found
in my auth.log
and:
Dec 10 11:58:34 mail
On Tue, 9 Dec 2003, Marc G. Fournier wrote:
> On Tue, 9 Dec 2003, Ken Murchison wrote:
>
> > Marc G. Fournier wrote:
> >
> > > When trying to connect to sieve using sieveshell, using the same
> > > userid/passwd that I've verified does work with IMAP, I
1 - 100 of 187 matches
Mail list logo
