it is not happening.
Is it a postfix version problem. Expecting your valuable help.
--
Best Regards
Gejo Paul
localmailhost
transportmx_result_filter = relay:%s
transportmx_scope = sub
transportmx_expansion_limit = 0
-
Thanks in advance for any Ideas/Suggestions
Regards
Gejo Paul
Hi,
I guess sharing a same hard disk(using cluster) causes I/O issues
(locking,delay in read write) and in mail messaging the files used for
sending are receiving are of very small size(especially in kb's).
If you looking for sharing the load of the server, as per my view IMAP proxy
like perd
1, $2, $3"`
>
> > ----
> > Discover the new Windows Vista Learn more!
>
> nah, thanks ;-p
>
> > <http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE>
>
>
> seperate i
t;
> >
> > it may be. you can uninstall it and see. the day you feel "confident",
> > you can reinstall it (or install selinux instead). you'll need to
> > understand how it works and how to configure it to allow what you want
> > to allow (I personally don't know!).
> >
> > >>
> > >> > Also from where do I turn logging on? I do not have the file
> > >> > /etc/maildroprc!
> > >>
> > >> you create it. but the location is system dependent. so you'll have to
> > >> fins out whether your maildrop uses this file. this is easy: just put
> > >> random stuff there and see maildrop barking for syntax errors...
> > >
> > > I created the maildroprc in '/etc/courier/' I put a single line (again)
> > > which is as follows 'logfile = "/var/log/maildrop.log" '. When I run
> the
> > > above mentioned commands I do not get anything written in the log file
> > > (I pre-created and gave all type of rights on it). Where should I see
> > > maildrop complain about the syntax?
> > >
> >
> > well, you're not making it easy. maildrop won't be allowed to write to
> > /var/log. try /tmp/maildrop.log instead.
> >
> > or use the logger command instead:
> >
> > `/usr/bin/logger -i -p mail.info -t "maildrop args: $1, $2, $3"`
> >
> > >
>
> > > Discover the new Windows Vista Learn more!
> >
> > nah, thanks ;-p
> >
> > > <
> http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE>
> >
>
>
> --
> Discover the new Windows Vista Learn
> more!<http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE>
>
--
Best Regards
Gejo Paul
rop complain about the syntax?
> >
>
> well, you're not making it easy. maildrop won't be allowed to write to
> /var/log. try /tmp/maildrop.log instead.
>
> or use the logger command instead:
>
> `/usr/bin/logger -i -p mail.info -t "maildrop args: $1, $2, $3
ta: 204857S
Encrypted Password: (none)
Cleartext Password: (none)
Options: (none)
The other option is to enable debugging for maildrop and enable logging on
/etc/maildroprc
--
Best Regards
Gejo Paul
second server and
to deliver the mails from second one.
--
Best Regards
Gejo Paul
argv=/usr/bin/maildrop -w 90 -d
> ${us...@${nexthop} ${extension} ${recipient} ${user} ${nexthop}
>
> Can someone help me?
>
> Best regards,
>
> Tôba.
>
--
Best Regards
Gejo Paul
maildirsize newtmp
.. courierimapkeywords courierimapuiddb cur
.INBOX.Trash maildirsize_old .Sent .Trash
Any suggestions or ideas are most welcome
Best Regards
Gejo Paul
Dear All,
I am using postfix + perdition + courier + ldap+ maildir (mail quota) on my
mail servers.
All the functions are working fine on the server except one small issue on
my backend servers.
I configured mail quota on the mail servers, suppose if the user quota
becomes full
condition 1 (worki
11 matches
Mail list logo
