"Well, then you have another problem unrelated to the advertising of
PLAIN and LOGIN SASL mechanisms, I suspect. "
I think so ;)
On Mon, 24 May 2004 [EMAIL PROTECTED] wrote:
What do you mean by "normal IMAP LOGIN command" ?
Uh, the LOGIN command as defined by RFC3501, RFC2060, and so on. As
o
What do you mean by "normal IMAP LOGIN command" ?
If you want to talk about someting like using outlook express or eudora
by default, it does not work :-/
I think I will require email clients like Mozilla or Thunderbird, with a
secured authentification, the others way are definitively impossible
Yes, I think I have turned on imaps in my cyrus.conf...
# UNIX sockets start with a slash and are put into /var/imap/socket
SERVICES {
# add or remove based on preferences
imap cmd="imapd" listen="imap" prefork=0
imaps cmd="imapd -s" listen="imaps" prefork=0
pop3
of
which scripts (or mailboxes) it's already visited.
The real bikeshed question is what it should do when a loop is
detected? And should that action be at all user configurable?
-Pat
---
Home Page: http://asg.web.cmu.edu/cyrus
Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
is can't be done with Exim ? (http://www.exim.org/)
-Pat
---
Home Page: http://asg.web.cmu.edu/cyrus
Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
to the null device. ]
Another advantage of Exim is that if using LMTPd over TCP/IP for
Cyrus delivery, you can use a 'verify recipient/callout' ACL to
both test for the existance of virtual users and also to detect
Over Quota situations and issue a temporary failure code at SMTP
RCPT time instead of accepting the message and leaving it in the
MTA queue or trying to bounce it.
-Pat
anything that is actually addressed to postmaster.
(One of the things I like about Exim is that it doesn't use Mailer-
Daemon; and the default handling of undeliverable bounce messages
is much more sane.)
-Pat
ages with no Subject: at all; but
that's another rant...)
-Pat
er
that handles these mailboxes. See the Exim docs for details of
that flag and side-effects of removing it.
You can test your config change with 'exim -bt [EMAIL PROTECTED]'.
-Pat
wind up mixed in with mail that was actually from the
list.
Having the List Id would be nice.
Yes, it would.
-Pat
rsions available via the ports. I'm currently
using 2.2. It is officially still Beta; but seems to be solid enough
for a producton environment.
-Pat
--On Thursday, October 23, 2003 15:35:08 -0400 [EMAIL PROTECTED] wrote:
On Thu, 23 Oct 2003, Pat Lashley wrote:
--On Thursday, October 23, 2003 14:53:38 -0400 [EMAIL PROTECTED]
wrote:
I'm not sure how the vacation functionality is implemented; but if it
goes through your normal MTA inste
quot;.
I'm not sure how the vacation functionality is implemented; but if it
goes through your normal MTA instead of attempting a direct SMTP connection;
then you should be able to have your MTA rewrite the From address on the
way out. This is fairly trivial with exim; I'm not sure how hard it would
be with other MTAs.
-Pat
tribution. Just manually add an explicit
'anyone p' ACL to every existing mailbox and every new INBOX you
create. It will be inherited automatically by any new sub-mailboxes.
(INBOXes have an implicit 'anyone p' which is not inherited. Making
it explicit will enable the in
ery. I believe
that 'mail store' is the more accurate term.
-Pat
(Horde filtering interface.
To be integrated into the next major version of IMP.)
I'll also be checking out Websieve, Smartsieve, and "damn, none of
these do what I want so I'll have to roll my own".
-Pat
the spam score is over
some site-specified limit. (But lower than the automatic rejection limit.)
(I also include the SA spam report as a header; which could be used by
more sophisticated filters based on particular tests matched by SA.)
-Pat
x27;s automatic conversion effectively hides the
charset identifier. But I do have an Exim ACL rule to reject a couple of
asian charsets on a domain where I know that nobody can read them. (Gets
rid of a lot of apparent spam.) Filtering for '=?euc-kr?' and a small
number of similar values ('=?big5?', '=?gb2312', etc.) should get rid
of them.
-Pat
Are there any tools for the mail admin to use to edit, or at least
view, annotations on messages and mailboxes/folders?
Thanks,
-Pat
#x27;t plan on using sieve; this will provide an indication
of whether the detail part is surviving the sendmail->lmtpd transition.
Once you've got the problem ironed out, you can remove the sieve script
again.
-Pat
' to change
the acl. Once you've changed the acl, use lam to show the permissions
on user.rjs3.foo to make sure it was actually set. Then try another
delivery.
There is one other thing that may or may not be an issue. Do you
have a sieve script activated for your INBOX ?
-Pat
ver an encrypted connection. What
happens if you remove the "/notls" ?
-Pat
cally.
-Pat
wing an MTA to remove a header that should never have been sent
is not the same as allowing the header to be sent in the first place.
So, no, it is not correct to include the Return-Path header when
forwarding or bouncing the message.
-Pat
--On Wednesday, September 24, 2003 09:30:52 -0400 Rob Siemborski
<[EMAIL PROTECTED]> wrote:
On Wed, 24 Sep 2003, Pat Lashley wrote:
I thought you said above that sieve runs before the 200 result. So
arguably, the message hasn't been -completely- recieved by lmtp until
sieve is fi
--On Tuesday, September 23, 2003 21:58:03 -0700 Chris Stromsoe
<[EMAIL PROTECTED]> wrote:
On Tue, 23 Sep 2003, Pat Lashley wrote:
Just because lmtp is linked to sieve is no reason to assume that they are
(or should be) functionally intertwined.
I never claimed that they should be. I
liminate
the possibility or make it needlessly comples.)
There are certainly -worse- models than procmail; but that doesn't
make procmail a particularly good model. And certainly the argument
"but procmail does it like this" doesn't hold much water.
-Pat
envelope values. This is possible because it -is- a
well-integrated filtering system; much like sieve integrated with
lmtpd. Sieve and Exim filters are both well-designed solutions
that fit smoothly into the mail processing environment. Procmail
basicly sits outside the primary mail processing environment.
(Please don't take any of this as denigration of the utility of
procmail. And it does have the major advantage of being usable
without any special support from the MTA.)
-Pat
--On Tuesday, September 23, 2003 13:36:18 -0700 Chris Stromsoe
<[EMAIL PROTECTED]> wrote:
On Tue, 23 Sep 2003, Pat Lashley wrote:
--On Tuesday, September 23, 2003 02:18:50 -0700 Chris Stromsoe
<[EMAIL PROTECTED]> wrote:
> out of ~40,000 messages I've got handy, betwee
--On Tuesday, September 23, 2003 02:18:50 -0700 Chris Stromsoe
<[EMAIL PROTECTED]> wrote:
On Tue, 23 Sep 2003, Pat Lashley wrote:
--On Monday, September 22, 2003 22:40:00 -0700 Chris Stromsoe
<[EMAIL PROTECTED]> wrote:
I keep mentioning Envelope-To because 30+ years of Software
--On Monday, September 22, 2003 22:40:00 -0700 Chris Stromsoe
<[EMAIL PROTECTED]> wrote:
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)
ot only of that value but of the envelope recipient
as well.
-Pat
fairly easy to
implement. That doesn't make it the right one.
The envelope extension exists to provide the functionality you need.
-Pat
--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. Rel
"owner-cyrus-sasl" {
fileinto "INBOX.cyrus.sasl" ;
}
else {
# INBOX.cyrus isn't a mailbox; so if we can't figure out
# which sub-mailbox to file it in, send it to my main inbox
# where I'll be annoyed enough to fix the script...
fileinto "INBOX.DEBUG" ;
}
}
-Pat
tead of local folders. Exactly how to tell it to do that varies
with the MUA.
-Pat
nknown
ACL condition/modifier" error message.
Thanks,
-Pat
se I'm doing /callout
recipient checking and that isn't supported by the lmtp driver.
If you aren't doing that, you can use the lmtp driver and a unix-
domain socket.)
-Pat
spam. And that
will lead to different scores for the same message.
I know this is fairly easy to do in Exim. (Using SA from a router
rather than an ACL.) I suspect it's not too difficult for other
MTAs. (It does prevent the use of Cyrus' single store option though.)
-Pat
the right path in
your /usr/local/etc/cyrus.conf The master is normally started
by a script in /usr/local/etc/rc.d. (All scripts in that dir
are automatically run when the system boots to multi-user.)
-Pat
sasl. Run 'ldd /usr/local/cyrus/bin/imapd'
It should use libsasl.so.3.
-Pat
How-To's on the various sites mentioned above
that should make it easy to get everything set up and working
together. (If you happen to be running FreeBSD, you can install
all of them through the ports. The Exim port uses ExiScan-ACL
by default.)
-Pat
--On Sunday, July 13, 2003 11:11:09 -0400 Rob Siemborski
<[EMAIL PROTECTED]> wrote:
On Sat, 12 Jul 2003, Pat Lashley wrote:
In particular, is there any clean method for an MTA like exim to
determine whether a given local part is deliverable via the Cyrus
lmtpd? (Or, more accurately, wo
ced when I finished converting the routers from the
old config and started on the ACLs, exiscan, and other stuff that
wasn't in 3.22. The documentation has gotten too big to just read
all the way through before trying anything. At least for updates...)
Thanks,
-Pat
xim has a way to do it internally.
(Or at least not directly. I might be able to do something with the
built-in perl lib...)
-Pat
d to do that would need to know the same
Cyrus implementation details and be kept in sync with any Cyrus changes.
Nothing says that _cyrus_ has to be queried on every "RCPT TO:"..
Nothing except the principal of implementation opacity that the Cyrus
architecture implements so well for basic delivery and mailbox access.
-Pat
--On Saturday, July 12, 2003 08:12:55 -0400 Ken Murchison <[EMAIL PROTECTED]>
wrote:
Pat Lashley wrote:
What does lmtpd do when presented with an address which includes detail
notation for a sub-mailbox that doesn't exist?
Assume that there are mailboxs 'user.mumble.inbox&#x
cyrus.users'; it would return success
and the string 'patl+cyrus'.)
It might also be useful to have an option that would make the printed
output be the translated mailbox name. (E.g., Instead of 'patl+cyrus'
it would return 'users.patl.cyrus' or 'users/patl/cyrus' depending
on the heirarchy separator.)
Thanks,
-Pat
pgp0.pgp
Description: PGP signature
to do so." (Or, "this is what it does now,
but when somebody has the time to implement it, we'd really like it
to do that instead.")
Thanks,
-Pat
pgp0.pgp
Description: PGP signature
mailbox. (Offering this extension would
imply that the old rename does not affect subscriptions at all
on this server.)
-Pat
msg04760/pgp0.pgp
Description: PGP signature
. Eventually
>> the old db would be completely shadowed and could be removed.
>
> Hmm. I'll defer to Rob on this, but I don't think we want legacy
> setpass() code floating around in the v2 library (each plugin used to
> set its own password, but now its handled global
ke the switchover much easier.
Easier yet would be if the v2 library would support using the old
v1 sasldb as a fallback if it doesn't find an entry in the new db.
New entries and password updates would go into the new one. Eventually
the old db would be completely shadowed and could be removed.
-Pat
msg04554/pgp0.pgp
Description: PGP signature
but not ready to shift to v2.
How much can be done to ease the transition? Is there a tool to
extract PLAIN passwords from the v1 sasldb and store them in the
new format? (That would at least handle the common case where all
of the mechanisms actually used the same password for a given user.)
-Pat
msg04547/pgp0.pgp
Description: PGP signature
deployed... Or are you saying that it's just
too early in the development cycle?
Or is there some other reason why clients aren't likely to
support it?
-Pat
msg04409/pgp0.pgp
Description: PGP signature
arball. ]
And the download web page still refers (and links) to 1.6a2.
And on a mostly unrelated note, what is the current state of the
ACAP daemon? Is it sufficiently featureful and stable to be
deployed in a small production environment? If I want to test
it out, should I go with the latest ta
ing but the 'imsp starting' message.) Running
imspd with '-d' doesn't help at all - there are no additional messages.
Thanks,
-Pat
msg04390/pgp0.pgp
Description: PGP signature
out there tell me how many users can a single server support
from a single box (a high end Compaq). I know this is depends on email
usage but any ideas on how many Netscape Messenger users could be
supported.
Regards
Pat
there any other known issues using Cyrus with NFS.
Regards
Pat Fenton
58 matches
Mail list logo
