Hi.
I got a strange problem today:
I have a server machine that has several additional IP-addresses, mostly for
webserver-SSL-certificates.
Now I tried to set up a second esmtp server on a different IP-address for some
testing purposes.
To get messages there, I set up a domain that has the se
Bernd Wurst writes:
To get messages there, I set up a domain that has the second ip-address listed
as primary MX (via intermediate Hostname, not IP as MX).
What happens is that the primary courier-server says "configuration error:
mail loops back to myself (MX problem)." when I send a message
Hi.
On Thursday 24 April 2008, Sam Varshavchik wrote:
> Define "primary MX". The MX record for the other machine must have a
> numerically lower priority (higher order priority) than the MX record for
> this machine.
Well, I think I did this step correctly.
To be precise, this is my setup:
#
On Thu, 24 Apr 2008 Sam Varshavchik wrote :
>suresh p writes:
>
>>On Wed, 16 Apr 2008 Sam Varshavchik wrote :
>> >suresh p writes:
>> >
>> >>ÃÂ On Tue, 15 Apr 2008 Sam Varshavchik wrote :
>> >> >suresh p writes:
>> >> >
>> >> >>On Tue, 15 Apr 2008 Sam Varshavchik wrote :
>> >> >> >suresh p writ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Arturo 'Buanzo' Busleiman wrote:
[...]
| Please, PLEASE, can you make this setting configurable? I mean the HARD
| limit, not the already
| configurable one.
[...]
Ok Sam, I see you are really not interested. I've been promoting Courier-MTA
since 2
I'm still working on getting everything migrated from an old Courier
server to a new one (I posted further details a week or so ago with a
different question, but the short of it is that I'm migrating from a
CentOS 4.1 x86 server running Courier 0.58.0 to a new one running Cent
5.1 x64 and
Matt Miller wrote:
> the short of it is that I'm migrating from a CentOS 4.1 x86 server
> running Courier 0.58.0 to a new one running Cent 5.1 x64 and
> Courier 0.59.0 and am running into some minor problems.)
...
>
>> [EMAIL PROTECTED]:/
>> $ cmlm sub /home/vmail/lists/itfreedom.com/cust
Joe Laffey wrote:
I just wanted to say thanks. This worked out quite well. The only
thing it lacks is a way to scan outgoing messages. I am not as
concerned about this because most of my users send mail through other
servers. But is there some easy way to scan the outgoing as well?
I used to
Heh, sorry, I meant to include a link to the trace...
http://www.itfreedom.com/temp/mlm.trace
Also, we are using gdbm as the storage format for files in /etc/
courier- rebuilding them resolved the problem that I posted about
previously. Is there a similar way to rebuild whatever additional
Hello all,
I have a interesting situation here with my mail server. I use Debian Etch,
Postfix, Courier Authlib (Authpam), Courier Maildrop, PAM_LDAP and NSS.
I created manually the maildrop of each user, and here the quota is 100 MB. I
created with maildirmake -q 1S ./Maildir. Well,
for
Bernd Wurst writes:
Hi.
On Thursday 24 April 2008, Sam Varshavchik wrote:
Define "primary MX". The MX record for the other machine must have a
numerically lower priority (higher order priority) than the MX record for
this machine.
Well, I think I did this step correctly.
To be precise, thi
suresh p writes:
ok.
who owns the authlib config files authdaemonrc, authldaprc ? Do we need a
seperate user for that or root will do ?
The userid that courier-authlib is configured with. 'make install' puts all
the configuration files and gives them the correct ownership and
permissions.
Sam Varshavchik writes:
Bernd Wurst writes:
Hi.
On Thursday 24 April 2008, Sam Varshavchik wrote:
Define "primary MX". The MX record for the other machine must have a
numerically lower priority (higher order priority) than the MX record for
this machine.
Well, I think I did this step corr
Sam wrote
>>
>> I bought a certificate that is already working with apache22.
>>
>> Additional I want to get rid of the warning message in emailsclients that
>> the ssl cert is not good ...
>>
>> is it possible to use the same ssl certs as i use with apache?
>>
>> the dir with the ssl look like th
Jay Lee wrote:
> I used to use ClamCour:
> http://www.becrux.com/index.php?page=projects&name=clamcour but found
> that it stopped working with ClamAV around ClamAV 0.90 or so.
Pythonfilter includes a clamav module that can utilize pyclamav or
pyclamd for virus scanning:
http://phantom.dragonsd
Matt Miller wrote:
> Also, we are using gdbm as the storage format for files in /etc/courier-
What were you using before? The "file" tool can probably tell you what
format the dat files are.
> rebuilding them resolved the problem that I posted about previously.
> Is there a similar way to reb
Marco Kammerer wrote:
> Sam wrote
>
>> ...
>> Then, take the resulting three .pem files, and concatenate them together. I
>> do not recall offhand the correct order, but I believe it should be: your
>> key, your pem, the intermediate pem. Take the resulting single file, and
>> specify it as TLS_
After an upgrade to the latest Courier version (4.3.1,2 in the FreeBSD
ports tree), I started getting this message in Thunderbird whenever I
check mail with TLS enabled:
The current command did not succeed. The mail server responded: error
in IMAP command received by the server.
Checking via
I'll look into the file tool; I'm unfamiliar with it.
I tried doing the export + import routine, but got the same Invalid
Argument error on the import.
Was there anything meaningful in the strace I posted?
Gordon Messmer wrote:
Matt Miller wrote:
Also, we are using gdbm as the storage fo
Jay Chandler wrote:
> After an upgrade to the latest Courier version (4.3.1,2 in the FreeBSD
> ports tree), I started getting this message in Thunderbird whenever I
> check mail with TLS enabled:
> The current command did not succeed. The mail server responded: error
> in IMAP command received
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jay Lee <[EMAIL PROTECTED]> wrote on 2008-Apr-24:
>> I just wanted to say thanks. This worked out quite well. The only
>> thing it lacks is a way to scan outgoing messages. I am not as
>> concerned about this because most of my users send mail through
Matt Miller wrote:
> I'll look into the file tool; I'm unfamiliar with it.
It's pretty simple, and frequently useful:
$ file /etc/courier/aliases.dat
/etc/courier/aliases.dat: GNU dbm 1.x or ndbm database, little endian
> I tried doing the export + import routine, but got the same Invalid
> Arg
On Fri, 25 Apr 2008, Jeff Jansen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jay Lee <[EMAIL PROTECTED]> wrote on 2008-Apr-24:
>>> I just wanted to say thanks. This worked out quite well. The only
>>> thing it lacks is a way to scan outgoing messages. I am not as
>>> concerned abo
Hello,
We are using courier imap in our mail server. Unfortunately, these days we
are getting frequent 'connection timed out' messeges due to increase of
load. We tried to increase the MAXDAEMONS setting, but that has not helped.
When we kill some of the many imap processes, everything goes back
Hi.
On Friday 25 April 2008, Sam Varshavchik wrote:
> >> But:
> >> 78.46.69.2 and 85.10.228.82 are configured on the same device:
> > There you go. Courier obtains a list of all locally-configured IP
> > addresses. It sees 85.10.228.82, and sees that it's the highest priority
> > MX, so it concl
25 matches
Mail list logo
