Is there a technical reason that the NNTP engine is limited to shared
folders?
No. It just didn't seem to make much sense at the time.
That's what I figured, thanks for clarifying.
Why not try the replication code in Cyrus 2.3?
Honestly because I didn't know it was there.
I was under
My apologies in advance for not being subscribed to the list but I had a
quick inquiry.
I've read in the docs that the Cyrus NNTP daemon can export shared folders
via NNTP and receive an NNTP feed. Can the same be done for user mailboxes?
I've always wondered if a group of Cyrus Servers could
Sounds like your MTA is stripping the '@domain' part of
the address and so Cyrus is falling back to is defaultdomain
Make sure that your MTA is passing the fully qualified
email address as the userid when it attempts to deliver
the mail.
-- Michael --
Vects [EMAIL PROTECTED] wrote in message
I've never used pam for virtual domains but the general idea
is that the user provides the fully qualified [EMAIL PROTECTED]
as their userid. SASL splits that up into a realm and a
user so in terms of SASL, creating the user looks something
like this:
saslpasswd -c -U domain.dom userid
I really
On Wed, 9 Jul 2003, Michael Fair wrote:
I totally agree that end users should not be allowed to write their
own code. I was thinking that sysadmins could pull from a pool of
well known plugins as well as write their own. These would then
become valid filters for use in the 'filter
But a slightly more complex script might be:
filter :spamtest
if result :value le comparator-i;ascii-numeric -30
{
filter :sms
}
elsif result :value ge comparator-i;ascii-numeric 5
{
fileinto spam;
}
fileinto filter :fileinto;
Maybe:
filter :myfilter {
Yes agreed,
I tried to hint about this while ago (see sieve spamassassin) and Rob
said there was no proper plugin-support, it would need
COMPATIBILITY or SUPPORTED-things from timseved in login if there is not
sa supported or not and such things so it would be pretty complicated or
not.
Hi Michael,
--On Tuesday, July 8, 2003 9:38 PM -0700 Michael Fair
[EMAIL PROTECTED] wrote:
| What do others think about this?
| Would this simple pass through filtering be useful?
| I'm primarily thinking of Spam catchers, Virus Scanners,
| and any other use where shoving the email
Hey all,
I have a general question/suggestion regarding Sieve.
It seems to me that it would be useful to be able
to install filter plugins that could transform
mail messages as they were processed.
This would be a simple command, like:
filter :spamassassin
This command would take the email,
Since so many of us use Postfix I was wondering
if we could solve the Postfix needs userdb entry
before delivery problem by adding a method by
which Postfix could lookup the mailbox in one
of Cyrus' databases.
Originally I was thinking of pointing Postfix at
mailboxes.db and adding a new DB class
Greetings all,
I'm doing some work on how to create a somewhat
reliable geographically redundant mail system.
The idea is that site A would be the primary site.
The MX record would point to a machine at that
site and everything would work as normal.
Then there'd be a site B. The backup site if
/drbd/)
with heartbeat (linux-ha). Basically replicates a all data written to
disc on the primary to the secondary and handles switching from primary
to secondard when it detects that the primary is down.
L
On Tuesday, March 18, 2003, at 06:58 PM, Michael Fair wrote:
On Tue, 18 Mar 2003
Upgrade to Cyrus 2.2 which has builtin support
for domain folders.
There is no way that I can see (without patching the
Cyrus code base) to make these folders act in the
way you are expecting them to. It's not just a matter
of getting the into the new folder hierarchy it's
setting the email
Hi Everyone,
I'm having a little trouble using the Cyrus SASL auxprop
authentication.
It seens that I can't authenticate users that has an AT (@) in their
usernames.
Ex:
If I create a username called jungle using the password 'foobar'
using the saslpasswd2
Remove the gwch.ath.ch anything entry
from your virtual table or add
[EMAIL PROTECTED] [EMAIL PROTECTED]
The gwch.ath.ch anything entry is explicitly
to tell Postfix to reject any address it
doesn't see in this table.
-- Michael --
- Original Message -
From: Roger Grosswiler [EMAIL
I don't know how to get around some kind of
delimiter but you can change the
recipient_delimiter in your main.cf to
be whatever you want.
I normally just set up aliases to redirect
[EMAIL PROTECTED] - [EMAIL PROTECTED]
-- Michael --
- Original Message -
From: Emilio Recio [EMAIL
That's fantastic!
I'm especially looking forward to seeing the creative
ways in which the two technologies can be used together.
Perhaps a separate thread should be opened on the list
that presents possible uses for the collaboration?
I expect that if Ken had some expected uses that any
I use Postfix and SpamAssassin which works quite well.
The examples below are Postfix specific, but I'm sure
Sendmail could be made to do something similar using
the same principles.
I've used two methods of integrating the filter into
the process.
1) Create a new delivery transport called
With Outlok and Outlook Express the easiest thing
to do is just setup the IMAP mail account (which
shows up under its own hierarchy) and drag from
your INBOX (where all the pop mail is stored) to
the INBOX (under the new IMAP server hierarchy).
-- Michael --
- Original Message -
From:
I've unfortunately never been on the admin side
of newsgroups but I've been an avid user of them
and think they are a great way to do mailing lists
and shared folders.
I've done both the binaries music stuff and
discussion groups and found it to be extrmely
effective at sharing information,
First I did:
cvs -d :pserver:[EMAIL PROTECTED]:/cvs co -d cyrus-imapd cyrus
and then I did like this:
cvs -d :pserver:[EMAIL PROTECTED]:/cvs co -d cyrus-imapd-2_2 -r
cyrus-imapd-2_2 cyrus
What is correct ? Which one should I use ? I think without specifiying
any tag or revision I
Having Cyrus setup it's lmtp socket under /var/spool/postfix (but not
/public or /private) is the right thing to do. I say this because
often postfix runs in a chroot env and won't access the lmtp socket if
it's outside of /var/spool/postfix
This isn't true in the slightest and making it
I have testtesttest in the loginrealms and it does not work ! Even
without unixhierarchysep. I cannot login to
user.testtesttest@testtesttest with login testtesttest@testtesttest !
How are you testing authentication?
This is where I start questioning the fact that no messages
(from your
Do typical installations use altnamespace or the hierarchical name
space?
One point I didn't see on the list about this so far
in regards to typical installations and unix hierarchy
separator feature is that without it there is now way to
have a . in the mailbox name which is important in at
your sasl_pwcheck_method set to auxprop
in imapd.conf right?
- Original Message -
From: Christian Schulte [EMAIL PROTECTED]
To: Michael Fair [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, September 17, 2002 5:34 PM
Subject: Re: Cannot get loginrealms to work with 2.0.16
Hey Amos,
Thanks for clearing that up.
If you have any specific questions about getting
your server configured let me know as I'd like to
help. Your posts have been invaluable to me in
the past so I'd like to return like kind so to speak.
Assuming your interested, all the threads on this
Just a shot in the dark, but is Postfix using
Berkeley DB for anything?
LMTP is shared among both applications and if
either needs to access the same DB then one or
the other will surely choke
If master is dying then perhaps it is accessing
a DB from Postfix and Postfix is using an older
On Monday 05 November 2001 12:17 pm, cyrus-mailinglist wrote:
Hello folks!
One question! If I have a mailbox created with cyradm how I can make
aliases 4 this mailbox?
It's handled by your MTA.
And if I want to host multiple domains with cyrus how this works??
Same way it does with
In an attempt to clean up my mail volume to my inbox,
I wanted to start using subfolders to receive logs
from the various machines I watch over.
After so debugging voodoo I realized that:
[EMAIL PROTECTED]
does not work and instead one is forced to use:
[EMAIL PROTECTED]
I believe this will
Assuming you are talking about where SASL gets
its information from, you can use all except
for passwd and shadow backends.
If you are talking about how a client
authenticates to the IMAP server, then you
can use all methods available.
-- Michael --
On Tue, 2001-10-09 at 10:08, Robert
, Kevin M. Myer wrote:
On Thu, 4 Oct 2001, Michael Fair wrote:
You cannot, at this time, have multiple domains and one Cyrus
in the way you want it. There's nothing more to say. Given
the current constraints it cannot be done. You must go to a
multiple Cyrus solution unless you are willing
You cannot, at this time, have multiple domains and one Cyrus
in the way you want it. There's nothing more to say. Given
the current constraints it cannot be done. You must go to a
multiple Cyrus solution unless you are willing to change
login identifiers.
To accomplish this using only one
it, and on WINDOWS, what's taking you so
long!? :P It's been a long, frustrating journey so far, and the help is
very much appreciated.
Cheers
jenn
Michael Fair wrote:
You cannot, at this time, have multiple domains and one Cyrus
in the way you want it. There's nothing more to say. Given
This is clearly something that you will want to add
to Postfix.
If you do it any later then the initial attempt to
send mail into the users inbox you have not gained
anything as the mail has already gone through the
pipeline. If you are truly trying to stop resource
consumption (which it seems
While I can appreciate the feature you are trying
to implement, the proposed implementation is..
well... limited.
For instace how do you give access to sfLocationA
to mbUserG?
I'm envisioning a use for this where Shared Folders
are mailing lists for projects at a company.
You have a set of
Potentially stupid question:
If you truely want isolated domains on one server, why not just setup
one imapd for each domain, listening on a unique IP addresses (via IP
aliasing, etc), and have each imapd use a separate config file? This
would not require any changes to the code, and
It doesn't. Thats the point. Currently the disk structure enforces a
structure like user.username. I am changing this to domain.username
(Not a TLD, just the first part. So andrew.cmu.edu will require
user@andrew to login.)
Please do not drop the .user. portion of the heirarchy unless you
# ---
use Cyrus::IMAP::Admin;
while (1) {
my $client = Cyrus::IMAP::Admin-new(localhost);
my $rc = $client-authenticate(
-mechanism = login,
-service= imap,
-user = foo,
-password = bar,
);
print
Definately agreed.
I didn't realize that the scoping rules
in PERL are per basic block, not per
function. Thanks for the clarification! :)
-- Michael --
# ---
use Cyrus::IMAP::Admin;
for (;;) {
my $obj = Cyrus::IMAP::Admin-new('localhost');
}
# ---
$obj will get destroyed after
Thanks for all the clarifications.
To finish up on a point that you didn't fully understand
and to make a recommendation for your evaluation,
- being more comfortable with the concept of being able to make
subfolders of all mailboxes than I am with any folder except INBOX,
Not sure I
My intent right now is to keep the on-disk structure the same, but CMU
_might_ have different ideas. There has been talk about making '/' the
default and '.' an option, because it would make the code cleaner and
possibly a little faster. But, this may or may not ever happen.
I
Since I haven't seen a response to this yet, I'll
take a shot. Make sure you compiled imspd with the
appropriate options (my assumption would be that you
should use the same as imapd). You might try to
explicitly disable-sasl (not sure if imspd supports
that flag).
You also might try and
Being the generator of the email I at first thought
it might have been a problem with the Evolution
mail client I've been testing on Linux. However,
upon closer examination, what has actually happened
is that china.com has delivered a second copy back
to the info-cyrus mailing list. I can only
I would check to ensure that /etc/sasldb is in the list of files.
That or whatever file it is that holds the accounts for Cyrus
to authenticate against. I'm not an expert, but I thought I'd
give it a shot.
-- Michael --
I have 2 cyrus servers. The first one is on line the second one is for
If you don't need it to be automated just set up
two accounts (one to each server), connect, select all,
move the messages to the new server.
Of course if you need it to be automated, that's
a different story.
-- Michael --
On 25 May 2001 09:53:07 -0700, Jen-Mei Wu wrote:
Is there a freely
This went only to me but I think it
was intended for the list.
-- Michael --
- Original Message -
From: Tarjei Huse [EMAIL PROTECTED]
To: 'Michael Fair' [EMAIL PROTECTED]
Sent: Wednesday, May 23, 2001 6:25 AM
Subject: RE:
Hi, here's my notes during the time when I set up Cyrus. MAKE
I also had envisioned matching that scheme at the
top of the mailstore as well.
/ip.address1.of.host/user/bob
/ip.address2.of.host/user/bob
Since the IP address is something known at connection
time, that could be used to authenticate out of a
different database allowing us to support
Message -
From: Todd Nemanich [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, April 27, 2001 9:11 AM
Subject: Re: How to add virtual domain support
Michael Fair wrote:
Yes, the Cyrus server supports realms though it is largely
unused. Currently SASL just fills the realm info
God I love these guys!
Thanks Larry! Being part of the Cyrus crowd
is great. I was just thinking about the fact
that I hadn't seen any announcements about
2.0.13 just yesterday and was wondering if
the coding was still coming along.
-- Michael --
- Original Message -
From: Lawrence
I then planned that the users log in with their
email address (or a slightly modified version of
it to support older versions of Netscape and a
couple other MUA's that didn't like email addresses
as log in name) and rewrote the mailbox lookup
routines to return the new mailbox instead of
[...]
What about SASL?
SASL has different 'Login realms' - use the domain as realm.
The problem is that email clients don't supply the realm
information when they authenticate. If they log in as
their email address then this isn't a problem because
the login name contains the domain info
The problem is that email clients don't supply the realm
information when they authenticate. If they log in as
their email address then this isn't a problem because
the login name contains the domain info but the holy
grail in my mind's eye would be to allow [EMAIL PROTECTED]
and
The compile problem which is not being able to
link with the Berkeley Database, but before
going into the details of solving that problem,
is there any particular reason you are
starting with the old 1.6.24 instead of the
newer (and better) 2.0.12?
I even believe some guys here on the list
Hi All
I'm pretty happy with my slow progress with Cyrus-IMAP, Postfix, and
fetchamil.
I'm in the same boat in regards to doing the cooler PAM/LDAP/sieve
stuff. I am currently running cyrus on my own box to create a
prototype that I would like to roll out to the ISP I work for.
I'm
I also set up cyrus on a Debian potato system,
though I compiled the DB libs locally.
Your setup looks correct. What do the error messages
in auth.log or messages and syslog say.
If I was to troubleshoot it, I would look into the
following.
Try:
imtest -a test -u test -m login panda
I had
Just have the SMTP server authorize
through the same PAM interface that
your cyrus server does.
If you have SASL in the middle, that's
fine too. I think most SMTP servers
these support PAM directly.
-- Michael --
- Original Message -
From: The Hermit Hacker [EMAIL PROTECTED]
To:
Hey all,
We know there are a number of us that would love
to support virtual domains directly in Cyrus
and with the recent patch to make the separator
character configurable I think we have a good
base to make the virtual domains more of a
native feature. The way I've always envisioned
the
rstand its shortcomings.
-- Michael --
-
- Original Message -
From: "Marc Tardif" [EMAIL PROTECTED]
To: "Michael Fair" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, April 10, 2001 6:19 PM
Subject: Re: How to route mails to mailboxes that are named [EMAIL PROTECTED]
Well, if you want to do it, then do it right and provide a generic
mapping
layer like Postfix has. LDAP is nice and cool, but a simple regexp map
would be a _lot_ faster for transforming "[EMAIL PROTECTED]" to either
"atif_4unet_net" or "uid=atif, dc=4unet, dc=net, ou=Users, ...". And
Still a better (and easyer) solution will be to make the mailbox separator
configurable, not only dot.
This way, you can use dots in users name and users just log with
[EMAIL PROTECTED] and use -say- backslash as a mailbox separator.
Mihai
Once I get that programming itch I plan on
When I installed cyrus on my Debian Potato
system I compiled SASL to use GDBM instead
of Berkeley DB.
The rest of the system used db3.
-- Michael --
- Original Message -
From: "Olaf Zaplinski" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, April 05, 2001 3:54 AM
Subject: Re:
Subject: Re: Enterprise Server Solution
Date: Thu, 22 Feb 2001 01:08:24 -0800
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By
There is a known issue with OE 5.5 and newly
read messages suddenly becoming unread again.
Could this bug be related to the recently fixed
signalling bug in 2.0.9?
I do not understand the IMAP spec enough to
answer who's bug this is, but here is my assertion.
OE opens multiple connections to
erly through that.
Beyond that, I can't say anything more.
Good Luck,
-- Michael --
- Original Message -
From: "Peter Erickson" [EMAIL PROTECTED]
To: "Michael Fair" [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, January 25, 2001 12:47 PM
Subject: Re: Cyrus Imap
Are there any docs on the specifics?
Adding support for this to Cyrus and
SASL would be very cool.
-- Michael --
- Original Message -
From: "Joe Rhett" [EMAIL PROTECTED]
To: "Michael Fair" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, December 13, 2000
Users are signing up for a PHP/MySQL portal that runs on our system, with
the ability to set their own passwords. We also offer IMP-based e-mail
that
uses Cyrus impad. I can cut and paste encrypted password from the
underlying
MySQL database for the portal into /etc/shadow, but don't know
From: "Michael Fair" [EMAIL PROTECTED]
4) Microsoft Outlook Express' "Secure Password
Authentication" doesn't seem to work with cyrus.
It complains about CRAM-MD5 failing and thinks
the server doesn't support any authentication
that my Windows 98 machine has on
: "eric" [EMAIL PROTECTED]
To: "Michael Fair" [EMAIL PROTECTED]
Sent: Friday, December 01, 2000 7:53 PM
Subject: Re: SASL problems
Michael Fair wrote:
Hey all,
So I am trying to install 2.0.7 using sasldb
on a Debian 2.2r1 machine and have been unable
to get it
Try recompiling SASL using gdbm instead
of berkeley. Then regenerate your sasldb
using the new format. You'll also need
to make sure that /etc/sasldb is read/write
for the cyrus user. The easiest way is
just to chown the file to cyrus.
(Note: Other posts say cyrus only needs
to be able to read
Hey all,
I just wanted to celebrate the success
of getting my cyrus 2.0.7 installation
configured using SSL and sasldb. My
next project is to get Postfix (which
I've never used before) to deliver
the incoming mail.
Here are my post-install notes to hopefully
help others trying to get
Hey all,
So I am trying to install 2.0.7 using sasldb
on a Debian 2.2r1 machine and have been unable
to get it to work right.
Everything compiles and installs just fine,
but I can't get the system to do anything
useful for me yet. I am pretty sure the
problem is because I can't seem to
The Cyrus system uses sasl to authenticate.
It can use:
passwd
shadow
kerberos_v4
pam
sasldb
'role your own'
look at the cyrus-sasl sysadmin.html file
for more details.
-- Michael --
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, November 29, 2000
72 matches
Mail list logo
