On Friday 03 February 2006 13:10, Alexander Dalloz wrote:
> Am Fr, den 03.02.2006 schrieb Flash Love um 14:47:
> > I am running FC4+SASL+TLS+Postfix+Cyrus-imap+Cyrus-sasl+web-cyradm on two
> > hosts. HostA allows the creation of vitrual domain users as
> > user/[EMAIL PROT
I am running FC4+SASL+TLS+Postfix+Cyrus-imap+Cyrus-sasl+web-cyradm on two
hosts. HostA allows the creation of vitrual domain users as
user/[EMAIL PROTECTED], however, when using the same cm syntax for a user on
HostB cryadm complains "createmailbox: Invalid mailbox name" . HostB will
accept cm
On Monday 19 September 2005 05:18 pm, Wil Cooley wrote:
[...]
> Sorry, I think I took your subject line too literally; are you using the
> 'cyrus' service from master.cf or LMTP for mailbox delivery, or are you
> using maildrop, local or other direct-delivery service service?
> The '/b/' directory
On Saturday 17 September 2005 08:10 pm, Wil Cooley wrote:
> On Sat, 2005-09-17 at 12:21 -0500, Flash Love wrote:
> > I am using postfix+cyrus+sasl+webcryadm. When logging to imap accounts
> > the following complaint appears in maillog:
> >
> > pop3: login: [192.168.2.1
After four grueling weeks, I believe that I may have a stable
postfix+cyrus+sasl+webcyr system. Please provide me a sanity check.
My configuration is:
A firewalled postfix environment with:
(1) intranet domain = home.lan
(2) three FQDNs = example.com example2.com example3.com
If I need to provi
I am using postfix+cyrus+sasl+webcryadm. When logging to imap accounts the
following complaint appears in maillog:
pop3: login: [192.168.2.154] benu0001 plaintext User logged in
pop3: IOERROR: opening /var/spool/imap/b/user/benu0001/cyrus.header: No such
file or directory
pop3: Unable to open ma
On Thursday 15 September 2005 05:19 pm, Joshua Schmidlkofer wrote:
> Fedora Core 4
>
> look and see if you have a /etc/sasl2 directory.
ls -l /etc/sasl*
lrwxrwxrwx 1 root root12 Sep 11 11:20 /etc/sasldb -> /etc/sasldb2
-rw-r- 1 cyrus mail 12288 Sep 7 19:25 /etc/sasldb2
> However,
>
I am running saslauthd 2.1.20 with authentication mechanisms: getpwent
kerberos5 pam rimap shadow ldap
When I telnet to example.com on port 25 this is what the session looks like:
telnet mail.example.com 25
Connected to mail.example.com (x.xxx.xxx.x).
Escape character is '^]'.
220 mail.example.c
