AJ wrote:
Thanks. I have reviewed the sendmail page numerous times, but my
question is what is the difference between the way I have things set up
now, i.e just using cyrus as a local mailer, as opposed to ldap_routing.
I am not sure why one would go one way or the other, just trying to
Ken Murchison -- info-cyrus (2004-07-07 20:45:54 -0400):
This is a bug in Cyrus. Getting it to accept these messages is trivial,
getting the rest of the code to treat the message correctly (missing
body rather than empty body) is not.
I'll bugzilla this and take a look.
Thanks.
Fair enough ;)
So what would it cost to have this feature implemented?
Specifically adding the application level redundancy patch
that was submitted.
I think it is certainly worth discussion if nothing else
to see if it is something we, people interested, might
collectively be able to pay for.
I con't login.
Syslog message:
Jul 8 10:46:03 mail68 imap[24978]: badlogin: localhost [127.0.0.1]
plaintext root SASL(-1): generic failure: checkpass failed
Jul 8 10:47:31 mail68 master[24916]: process 24978 exited, status 0
Jul 8 03:50:00 mail68 CROND[25009]: (root) CMD (
Hi,
I am trying in vain to get libwrap activated in Cyrus
IMAPd. I am using Cyrus IMAPd 2.2.6, Cyrus SASL 2.1.18
on OpenBSD 3.5. And here is my configure command:
./configure --prefix=/usr/local/cyrus-imapd
--with-cyrus-prefix=/usr/local/cyrus-imapd
--with-openssl --with-sasl=/usr/local/sasl2
I con't login.
Syslog message:
Jul 8 10:46:03 mail68 imap[24978]: badlogin: localhost [127.0.0.1]
plaintext root SASL(-1): generic failure: checkpass failed
Jul 8 10:47:31 mail68 master[24916]: process 24978 exited, status 0
Jul 8 03:50:00 mail68 CROND[25009]: (root) CMD (
I have corrected the problem and restarted cyrus but is still not working.
I have the same error.
Jul 8 10:46:03 mail68 imap[24978]: cannot connect to saslauthd server:
No such file or directory
imapd.conf contains a line : saslauthd_path:/var/state/saslauthd
Saslauthd is running.
And I have the
I try to detail the problem(I have some more information):
The error:
Jul 8 10:46:03 mail68 imap[24978]: cannot connect to saslauthd server:
No such file or directory
What I have tryed to debug the problem:
1) imapd.conf contains a line : saslauthd_path:/var/state/saslauthd
2) Saslauthd is
Hi everyone,
For a new customer, I'm setting up a Cyrus server that will have to
authenticate against an Active Directory server.
So far, I've gotten Kerberos, TSL, SASL all working together from the
command-line with ldapsearch, so what remains is to build an imapd.conf
and have Cyrus play
On Thu, 8 Jul 2004, victor wrote:
I have corrected the problem and restarted cyrus but is still not working.
I have the same error.
Jul 8 10:46:03 mail68 imap[24978]: cannot connect to saslauthd server:
No such file or directory
imapd.conf contains a line :
Kevin Baker wrote:
Fair enough ;)
So what would it cost to have this feature implemented?
Specifically adding the application level redundancy patch
that was submitted.
I think it is certainly worth discussion if nothing else
to see if it is something we, people interested, might
collectively be
L.S.,
While trying to build the latest Cyrus, I ran into a small problem with
configure.
From configure (line 6346 and onwards)
---
# Check whether --with-dbdir or --without-dbdir was given.
if test ${with_dbdir+set} = set; then
withval=$with_dbdir
On Thu, 8 Jul 2004, Paul Boven wrote:
The last statement (with_bdb_inc=$with_bdbval/include) does not work
because $with_bdbval does not exist. Changing it to $with_bdb fixes
things. I've attached a patch for configure.in (trivial but untested
because I don't have the whole automake/autoconf
On Thu, 8 Jul 2004, Ken Murchison wrote:
Its not unheard of, in fact its been done for Cyrus before. I was paid
a rather large sum by a semiconductor company to implement the
altnamespace feature, and Fastmail.fm has contracted me for several
features, most recently almost all of the new
On Thu, 8 Jul 2004, Rob Siemborski wrote:
On Thu, 8 Jul 2004, Paul Boven wrote:
The last statement (with_bdb_inc=$with_bdbval/include) does not work
because $with_bdbval does not exist. Changing it to $with_bdb fixes
things. I've attached a patch for configure.in (trivial but untested
Hi Folks,
a few months ago I set up a new server with Cyrus SASL and IMAPD 2.1.16.
Everything runs perfectly fine, but now I want to enable sieve on that
host. So I set up a line in cyrus.conf like
sieve cmd=timsieved listen=sieve prefork=0
and now I can telnet like telnet localhost sieve
and
On Thu, 8 Jul 2004 [EMAIL PROTECTED] wrote:
I hate to ask, but what's on the table for things that need to be
done before a 2.2.7 release?
There isn't a specific table, I'm just extraordinaraly busy right now.
We will almost certainly see a 2.2.7 before the end of the month.
-Rob
On Thu, 8 Jul 2004, Paul Boven wrote:
Hi everyone,
For a new customer, I'm setting up a Cyrus server that will have to
authenticate against an Active Directory server.
So far, I've gotten Kerberos, TSL, SASL all working together from the
command-line with ldapsearch, so what remains is to
I think this was discussed before, but googling didn't reveal much (to me)..
I posted a note to someone who has a vacation message. Part of the message
returned is here:
===
Received: from cyrus by imap.newn.cam.ac.uk with local (Exim 4.20)
id
Ok, so I recompiled sendmail w/ LDAP support..
Here are the relavent parts of my mc file:
define(`confLOCAL_MAILER', `cyrusv2')
define(`CYRUSV2_MAILER_ARGS', `FILE /var/cyrus/imap/socket/lmtp')
# LDAP Related
FEATURE(`ldap_routing')
LDAPROUTE_DOMAIN(`panther.mydomain.com')
Hello,
I am currently setting up a MURDER environement with one frontend server and one backend server to start with. The MTA (Sendmail) for incoming mails (MX) will be running on the frontend server. Now my question: where should the MTA send the incoming mails ? Should the MTA send it to the
You will want to have something similar to this for ldap_routing.
FEATURE(`ldap_routing', `ldap -1 -TTMPF -v mailHost -k
(mailLocalAddress=%0)', `ldap -1 -TTMPF -v mailRoutingAddress -k
(mailRoutingAddress=%0)', `bounce', `preserve')dnl
http://www.sendmail.org/m4/ldap_routing.html
# LDAP
On Thu, 8 Jul 2004, ML mail wrote:
I am currently setting up a MURDER environement with one frontend server
and one backend server to start with. The MTA (Sendmail) for incoming
mails (MX) will be running on the frontend server. Now my question:
where should the MTA send the incoming mails ?
AJ wrote:
Ok, so I recompiled sendmail w/ LDAP support..
Here are the relavent parts of my mc file:
define(`confLOCAL_MAILER', `cyrusv2')
define(`CYRUSV2_MAILER_ARGS', `FILE /var/cyrus/imap/socket/lmtp')
# LDAP Related
FEATURE(`ldap_routing')
LDAPROUTE_DOMAIN(`panther.mydomain.com')
John,
Thanks, everything is up and running now, but I have one final question...
Is it possible for sendmail to check the alias file or virtusertable before
doing an ldap lookup. I am not ready to move these into ldap and I want to
preserve them.
Thanks again for all of your help.
AJ
Quoting
On Thu, 8 Jul 2004, AJ wrote:
John,
Thanks, everything is up and running now, but I have one final question...
Is it possible for sendmail to check the alias file or virtusertable before
doing an ldap lookup. I am not ready to move these into ldap and I want to
preserve them.
If you are
On Thu, 8 Jul 2004, ML mail wrote:
Well actually in our case we will start with one
frontend and one backend server where the mupdate
server and the MTA will both run on the frontend
server.
So for this case I guess it makes sense to have our
MTA on the frontend server send mails via LMTP (unix
On Thu, 8 Jul 2004, AJ wrote:
John,
Thanks, everything is up and running now, but I have one final question...
Is it possible for sendmail to check the alias file or virtusertable before
doing an ldap lookup. I am not ready to move these into ldap and I want to
preserve them.
If you are
--- Rob Siemborski [EMAIL PROTECTED] wrote:
You need to send it to an lmtpproxyd, but there's no
reason to put that on
a frontend -- we run our lmtpproxyd's on the same
hosts as our MTAs (via
unix socket).
Well actually in our case we will start with one
frontend and one backend server
Well, because I read on various lists that if you don't use ldap_routing then
the cyrus mail server can become cluttered with various bounces and spoofed
sender addresses.. This way, sendmail will verify each user before accepting
delivery. I may try the other alternative via socket map.
What do
On Thu, 8 Jul 2004, AJ wrote:
Well, because I read on various lists that if you don't use ldap_routing then
the cyrus mail server can become cluttered with various bounces and spoofed
sender addresses.. This way, sendmail will verify each user before accepting
delivery. I may try the other
Ok, so I recompiled sendmail w/ LDAP support..
Here are the relavent parts of my mc file:
define(`confLOCAL_MAILER', `cyrusv2')
define(`CYRUSV2_MAILER_ARGS', `FILE /var/cyrus/imap/socket/lmtp')
# LDAP Related
FEATURE(`ldap_routing')
LDAPROUTE_DOMAIN(`panther.mydomain.com')
John,
Thanks again, I wound up just using the socket map option w/ cyrus
and sendmail, which seems to be working well for me.
Apparently, you can't have an aliases file and ldap_routing unless your
aliases are in an ldap map.
AJ
John Arthur wrote:
Ok, so I recompiled sendmail w/ LDAP
Title:
34 matches
Mail list logo
