On 06/03/2016 04:44 AM, Sam Varshavchik wrote:
> But one thing's bugging me, according to that, Sourceforge's malware
> scanner has been tossing its cookies for well over a month now, and this
> is the first time someone noticed it.
> That could mean only one of two things. 1) Courier project
Apocalypse has happened: the sun rose from the west and Sam
is now peddling malware. Proof:
http://qdh.nl/tmp/courier-is-malware.png .)
Sam, will you have a word with them?
Z
--
What NetFlow Analyzer can do for you?
> • Added BuildRequires: perl-generators to the Fedora rpm spec file.
It breaks RHEL7 and its clones. There's no perl-generators there,
and if you grab it from Fedora and compile it, when you try to
install it you run into
Transaction check error:
file /usr/lib/rpm/perl.prov from install of
Hi all
I've been using the same courier/authlib/LDAP configuration for
more than a decade. authldaprc says
LDAP_HOMEDIR homeDirectory
LDAP_MAILDIR mailbox
LDAP_DEFAULTDELIVERY mailbox
and I have some Mailman lists in LDAP that look like
uid: list
objectClass: top
objectClass: account
I had courier-0.73.1 running happily on an SL 6.5 box until the
other day when the box broke down. Motherboard, the whole machine
had to be replaced, completely different hardware, hence I couldn't
restore the entire system from backup. So I took the opportunity to
upgrade to Centos 7. Compiled
On 10/26/2014 02:07 PM, Sam Varshavchik wrote:
Sure, but your real problem is that you copied the config from
the old system verbatim.
Of course I did. Configuring a full system from scratch (courierd,
esmtpd, imapd, pop3d + ssl etc as well as authlib) takes ages. And,
unlike some others,
An iphone that was working flawlessly with courier imap, suddenly
can't connect any more. The user did nothing, so the problem likely
stems from some automatic update on the phone.
The maillog shows a correct authentication and login, immediately
followed by DISCONNECTED. Having enabled the imap
I have system users in LDAP who need a full account with
homeDirectory, userPassword etc. They all have an internal
address user@mydomain, but would prefer to have their mail
forwarded elsewhere, to external addresses.
The problem is, if I create them as CourierMailAccount,
I can't use maildrop.
I wrote:
The problem is, if I create them as CourierMailAccount,
I can't use maildrop. And if I create them as CourierMailAlias,
I can't use any of the other attributes I need.
Duh. Both object classes can be used at the same time.
Z
On 04/24/2013 01:00 PM, Sam Varshavchik wrote:
The users are in LDAP, they all have different uidNumber:gidNumber
and imapd spawns an instance under each user's uidNumber. Gamin
however requires the LDAP users to be visible to the system, and
mine were not.
Ok, so basically the IMAP server
Classic problem, it gave me a lot of grief and it's not the first
time it did. Posting the solution so that I know where to find it
next time and it might help others in the meanwhile.
IMAP_USELOCKS=1
IMAP_ENHANCEDIDLE=1
Apr 23 18:32:04 node01 imapd-ssl: Failed to connect to socket /tmp/fam--
On 06/15/2011 04:34 AM, Sam Varshavchik wrote:
My smtpaccess file says
:::::::0001taballow,RELAYCLIENT
You're one nybble short there:
::::::::0001allow,RELAYCLIENT
Duh.
Thanks Sam. I could have kept staring at it for a week and I
Hello all
Mail from localhost is being rejected with
courieresmtpd: error,relay=::1,from=user@domain,to=user@domain: 513
Relaying denied.
My smtpaccess file says
:::::::0001taballow,RELAYCLIENT
I also tried
:::1taballow,RELAYCLIENT
localhost6taballow,RELAYCLIENT
to
Carlos Lopez wrote:
You all can also use http://www.infire.com/2.0/?l=end=0t=perlfilter_dkim
I've been using it since last year and it worked nice.
I installed it today and I would not recommend it.
It simply looks at the From: header of the mail and compares it to
a list of a domains in its
Gordon Messmer wrote:
I'll risk earning myself an RTFM reply and ask: is there a way to
configure tarpit=off?
No, not without modifying the source code, but the resources each
connection use on your system are very minimal. Increase the number of
connections that you allow.
I did so
For weeks on end now I am being subjected to what I could call a reverse
spam DDoS attack for lack of better term. Some asshole is sending out
zillions of messages to non-existent users at legitimate domains, using
clearly non-existent sender addresses @myhosteddomain. It seems he is
specifically
Leigh S. Jones wrote:
This is happenning to us all. It's not a DDoS attack, just a spammer
spoofing addresses at your domain.
Aha, thanks, that's good to know. Still, being a random target isn't any
better than being a selected one. The problem remains: courier shouldn't
choke, but does.
Gordon Messmer wrote:
... when mail servers connect to courier's
smtpd and send RCPT commands with invalid users (or any other error),
smtpd starts tarpitting them -- after each failed command, it waits for
an increasingly long period of time before it replies and reads more
commands.
# rpm -Uhv courier-ldap-0.56.0.20070902-1.i386.rpm
Preparing...### [100%]
package courier-0.56.0.20070902-1 is already installed
Huh? Name mismatch.
# rpm -qp --queryformat '%{name}-%{version}\n'
Sam Varshavchik wrote:
Is the TLS_PROTOCOL=SSL23 setting available with version 0.56, or
do I need a patch or svn version?
http://courier.cvs.sourceforge.net/*checkout*/courier/courier/courier/Change
In that case, when is the next release expected? I don't want to put a
development
Hi all
Is there any way to tell one instance of esmtpd to have multiple
personalities on different IP addresses? E.g. to bind to 1.2.3.4
and report itself as mail.domain.com and to also bind to 11.22.33.44
and there report itself as mail.otherdomain.com?
It would be very useful for serving
This is the Courier Mail Server 0.48 on $hostname.
I received the following message for delivery to your address. This message
contains several internal formatting errors. This is often caused by viruses
that attempt to infect remote systems. Instead of blocking this message, it
has
Sam Varshavchik wrote (ages ago):
RPM build errors:
File not found by glob:
/var/tmp/courier-0.47-1.2-buildroot/usr/local/bin/*
This turns out to be a change in FC2's glibc that ended up breaking rpm.
Bad news: after the latest updates (U4), this has now propagated to RHEL.
Good
Compiling the courier rpms straight from the tarball, configure
outputs
--with-mailuser=courier --with-mailgroup=courier
--with-mailuid=101 --with-mailgid=103
Is it necessary to hard-code both mailuser/mailgroup and
mailuid/mailgid at the same time? If only mailuser/mailgroup were
used, then
Sam Varshavchik wrote:
There is no second pass.
I never implemented recursive mail LDAP alias lookups.
This is what I thought you were referring to earlier, and there's no way
this worked before, simply because I never implemented recursive LDAP
mail alias lookups.
I believe you, but I know
Sam Varshavchik wrote:
I just remembered that there's an LDAP_DEREF setting in authldaprc that
blabbers something about aliases. This is something completely different.
I plead guilty, I hadn't checked it. But it's not that. It was set
'never' before the upgrade and it was still 'never' after.
Sam Varshavchik wrote:
Another thing is that if interbaun.com is defined as a local domain, the
actual domain you need to specify in the alias is the 'me' domain. All
local domains are mapped to the 'me' domain, when doing alias lookups.
Is this new in courier-authlib, or has it been so before?
Sam Varshavchik wrote:
I can't reopen that bug. Something in Bugzilla prevents me from
correctly reopening it against RHEL.
Uhm, by bug owner I meant the RH person, but you should indeed have been
allowed to reopen it.
You can just file a new bug against RHEL, and reference this one.
#144587.
Z
When courier encapsulates a message because of missing 8bit heders
etc and the message happens to be spam, the result is a message
that appears to have originated from the machine running courier
and is still spam. Spamcop and similar RBLs are not smart enough to
see the obvious, so they end up
Sam Varshavchik wrote (back in November):
RPM build errors:
File not found by glob:
/var/tmp/courier-0.47-1.2-buildroot/usr/local/bin/*
This turns out to be a change in FC2's glibc that ended up breaking rpm.
Bad news: after the latest updates (U4), this has now propagated to RHEL.
I didn't
# rpm -hiv courier-r-0.48.1-1.3AS.i386.rpm
Preparing...### [100%]
file /usr/share/man/man1/sendmail.1.gz from install of courier-0.48.1-1.3AS
conflicts with file from package postfix-2.0.16-14.RHEL3
Since courier does not conflict with
Sam Varshavchik wrote:
This turns out to be a change in FC2's glibc that ended up breaking rpm.
Bad news: after the latest updates (U4), this has now propagated to RHEL.
Good news: they released an errata rpm for FC2 that fixes this, so
eventually RHEL should also get it, eventually.
Good to
Gordon:
I'll clarify... I based that diagnosis on these lines:
16904 execve(/usr/lib/courier/bin/sendmail, [sendmail, -t], [env
snipped]) = 0
snip
16904 setgid32(102) = -1 EPERM (Operation not
permitted)
16904 getuid32()= 500
16904 setuid32(500)
Gordon Messmer wrote:
Given your trace, it looks like /usr/lib/courier/bin/sendmail is no
longer SUID root.
# ls -l /usr/lib/courier/bin/sendmail
-r-s--x--x1 root courier 67952 Aug 20 15:07 /usr/lib/courier/bin/sendmail
Hasn't been touched since I installed it. And the one other thing
A couple of weeks ago I installed 0.46 from rpm on a freshly installed
RHEL 3 AS. Everything worked fine for a while, but then suddenly only
root could send mail from localhost; all other users get a
sendmail: ERR: Permission denied
432 Service temporarily unavailable.
I can't remember doing
Julian Mehnle wrote:
Why do you think that a 0.x version reflects immaturity? I guess this
paradigm comes from the commercial software world...
Not really. Commercial software never starts at anything below 1.0
anyway. But the 1.0 version is a way of marking that the basic goals
of the software
I was reading the changelog again and came to think: isn't time now,
even long overdue, to make the leap to v 1.0? Courier is not perfect
(what software is?), but it has been mature for a very long time and
it looks at the competition with a very proud nose up in the air.
Moving up the minors and
http://bugzilla.mozilla.org/show_bug.cgi?id=248828
Summary: Mozilla might be using the deprecated ip6.int name resolution method
My mail client and mail server machines are, again since recently, both
ipv6-enabled. Since then, I open mozilla mail, get the message conncted to
[server], watch a long
Sam Varshavchik wrote:
couriertcpd does reverse DNS lookups in the ip6.int domain.
In that case, and taking as a premise that ip6.int is
deprecated, courier and mozilla have both contributed
to the problem.
By the smell of it, mozilla's reverse lookups are going
to go away anyway. Courier can't do
There are, basically, three kinds of spammers: those using
their own IP space and ISPs specialised in spam, those using
open proxies and those using throwaway accounts with normal,
respectable ISPs.
The spam and open relay blacklists that have developed in
the past years are offering some remedy
authlib/authldap.schema contains the virtualdomainuser attribute
definition twice, causing ldap to refuse to start with the error
Duplicate attributeType: 1.3.6.1.4.1.10018.1.1.7. It looks more
like a copy-pasto than like a typo though ;)
Z
Eduardo Roldan wrote:
May 28 19:58:14 spare imapd: couriertls: accept: error:14094418:SSL
routines:SSL3_READ_BYTES:tlsv1 alert unknown ca
Take a look at the thread ESMTP STARTTLS w/ 0.38.2 ? .
I have the same problem in a different context and no
solution yet, but parts of that discussion
Sam Varshavchik wrote:
Err. With SECURITY=STARTTLS, you need to set TLS_TRUSTSECURITYCERTS.
You missed the big fat comment there :-)
Oops. Indeed, thanks. However, fixing that gave new errors.
Sender:
500 couriertls: connect: error:14090086:SSL
I wrote:
...Any tips and hints
will be greatly appreciated; I can already see the big
men in white jackets knocking on my door.
Never mind. It's solved (worked around to be precise) and
I get to keep my sanity.
What I was trying to do was to ensure that communications
from the sender to the
Look, below, please. [The domain] is rejecting emails. It acts as if
the email address is case sensitive. Can you help?
Never noticed this before, but indeed, you are right. It's a probably
never-thought-of side-effect of the way the mail server can manage to
deliver mail to non-existing
I host a number of domains on a machine. It's a Redhat system running
courier-0.39.3 with the stock startup script. I have courier bounce
mail from RBL'ed sources and from a few manually entered ones. This
is done with a BLACKLISTS line in esmptd and a bunch of
IP allow,BLOCK=spammer statements in
Sam Varshavchik wrote:
--with-mailgroup and --with-mailuser take group/usernames.
--with-mailuid and --with-mailgid take numerical ids.
RTFM should read RTFMC, the C for carefully. Thanks.
Z
---
This SF.NET email is sponsored by:
Any ideas what's wrong?
In courier.spec: ./configure [...] --with-mailgroup=11 --with-mailuid=51
checking for mail user id... 51
checking for mail group id... configure: error: Unable to determine mail gid - invalid group 11
configure: error: /bin/sh './configure' failed for courier
error: Bad
Among other things, my /etc/courier/smtpaccess/spammers says
209.1taballow,BLOCK=550 exodus.net supports spammers, get another carrier
So far, so well, but how do I deal with non-block networks
like 209.202.192/18 and 64.39.64/19 etc? Does the syntax
permit x.y.z/n or do I have to enumerate
Brian Candler wrote:
I would like to migrate to a
different way of doing things, which would necessitate a change in the
users login name. I would like to be able to support my old way as
well as the new way. Doing so would require rewriting what the user
passes as his login name
Sam Varshavchik wrote:
... I haven't been able to figure when maildrop thinks that a
From_ line is actually needed or how to tell it so.
Does the message begin with a From_ line? If it does, then there you go.
When delivering to an mbox, if the message didn't have a From_ line, one
The maildrop manual says that
The message may contain an mbox-style From_ line before the
first header line. If the message does not contain a From_ line, maildrop
will create one (if needed).
but I haven't been able to figure when maildrop thinks that a
From_ line
Marcio Merlone wrote:
Is there a way to make courier-imap register last time login on ldap
server and its last IP?
You have this information already in your maillog, entries like
Nov 8 15:50:35 frog imapd-ssl: LOGIN, user=oracle, ip=[194.109.240.22]
For the purposes you want this, you
Ben Rosengart wrote:
I need to move about 150 users from an existing Cyrus installation
to a new Courier installation. I'd like to preserve their existing
configuration as much as possible: IMAP folders, flags on messages,
etc. Has anyone here done such a thing? What software did you use?
R'twick Niceorgaw wrote:
I have so far managed to get courier esmtp and imap working with
authmysql but pop3 is always failing.
Which version? Search the list archives for \r and you might find
what you're looking for.
Z
---
This sf.net
Sam Varshavchik wrote:
libtool: link: only absolute run-paths are allowed
libexecdir is defined as an absolute path by autoconf, you'll need to
figure out how the relative path ends up getting stuck in there.
I tried and failed. Would you be interested in a URL to a strace log?
Z
Sam Varshavchik wrote:
What does 'pg_config --includedir' show you?
You mean like this?
# pg_config --includedir
bash: pg_config: command not found
No, you can't mean that. But then I'm at a loss.
Z
---
This sf.net email is sponsored
David Busby wrote:
If you can't find pg_config on your box you should try this:
# locate pg_config
Done that already, found pg_config.h, but no binary. It makes sense;
I had installed postgresql-dev (debian box), but not postgresql itself.
Now I'm trying to remember why I did that
[EMAIL PROTECTED] wrote:
...Most probably was postgresql-dev
a build dependency for courier, but postgresql itself was not.
postgresql-dev is a build dependency for courier-ssl source.
Then that's where it came from. pg_config is part of the main
postgresql package and it's obviously
Next:
/bin/sh ./libtool --mode=link gcc -I./../.. -I../.. -I./../../courier -I../../courier -I./../../courier/libs -Wall -g -O2 -o librewrite.la -rpath lib/courier/courier/modules/uucp uucpstub.lo
libtool: link: only absolute run-paths are allowed
make[4]: *** [librewrite.la] Error 1
gcc -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -Wall -I.. -I./.. -c `test -f
'authpgsql.c' || echo './'`authpgsql.cIn file included from authpgsql.c:19:
authpgsql.h:8: libpq-fe.h: No such file or directory
make[2]: *** [authpgsql.o] Error 1
The problem is in authlib/authpgsql.h and
Chris Cameron wrote:
I've got IMAP working with a self-signed X.509 cert which is great, but
I'm looking to have mail clients stop complaining about the self signed
certificate.
So how do I go about getting one? I've got vague ideas from VPNs way
back when, but I'm not having much luck
cesar bielich wrote:
I am trying to find documentation on this but no luck.
Recently I printed the courier documentation because I belong
to the old school that finds it easier to leaf papers than to
scroll screens. The printer run out of paper. Few software
packages have as extensive (and
Bill Williamson wrote:
I used mkimapdcert, both with an untouched imapd.cnf, and with my changing
localhost to my ip address.
Both times give me this in the log when I try to connect (oe 6):
Oct 9 09:34:20 (none) imapd-ssl: Connection, ip=[:::63.103.217.132]
Oct 9 09:34:20 (none)
Anders Widman wrote:
am stuck at creating user accounts and virtual domains. I have got
the webadmin CFI working, and added the virtual domains to Locally
hosted domains.
Check whether these domains appear in /etc/courier/locals . If they do,
you need system accounts for the
David Humphrey wrote:
But I can't figure out what! What is it about courieresmtp that needs
to be configured to send mail *out* of the server?!?
Are you sure it's courier? Take one of the destination addresses from
the mail in your spool. Do
host -t mx domain
where domain is the part
bertus keyser wrote:
I know it tries to resolve my dns but we use private ip addresses on the
internal network.
How can I get the delay to decrease?
If you have more problems of this kind and you are using
BIND, you might want to look at the views function. It
allows you to use
Laurent Hausermann wrote:
I am sorry for a so silly question, but I can't find log file for courier imap
daemon. I am running the courier-imap package for Debian 3.0 and I can't see
where log are for both authmdaemon or imap one...
/var/log/maillog ?
Z
Gordon Messmer wrote:
... I want [EMAIL PROTECTED] to go to john, [EMAIL PROTECTED]
to go to pete and [EMAIL PROTECTED] to go to jim.
... The result
was that mail for [EMAIL PROTECTED] got delivered to pete and mail
for [EMAIL PROTECTED] got delivered to john.
Isn't that what you wanted?
bertus keyser wrote:
I have a firewall between my courier mail server and the internal network
clients.
I know it tries to resolve my dns but we use private ip addresses on the
internal network.
How can I get the delay to decrease?
If you have more problems of this kind and you are
Marc wrote:
telnet localhost 110
user schabelm
pass secret
I get -ERR Login failed
Check what happens if you bind as LDAP-root. Put
LDAP_BINDDN cn=administrator,dc=mydomain,dc=com
LDAP_BINDPW secret
in your authldaprc (substituting the real rootdn and rootpw just
as
Zenon Panoussis wrote:
What I need - I don't know if it's possible - is delivery
of *any* @domain mail to a certain user, including mail
for invented addresses. The .courier-address system
can only handle addresses that have been pre-configured
by the user, but does not provide a catch
Keith Pettit wrote:
If domain.com is in locals, then you should only have
asdf:tabfoo
in aliases.
But i need the ability to say:
[EMAIL PROTECTED]: foo
[EMAIL PROTECTED]: otheraccount
etc. Will this work??
As I had the dubious pleasure to find out in the hard way,
it will, but
Hello
Can anyone see what I'm doing wrong?
Redhat 7.3, courier-0.39.3.20020928-1.7.3 with base, imapd,
maildrop-wrapper, smtpauth, maildrop and pop3d instaled.
On a machine called myhost.mydomain.dom I have system accounts
john, pete and jim and I host the domains one.com, two.com and
74 matches
Mail list logo
