Il 19/07/2017 19:22, Alessandro Vesely ha scritto:
Did you actually check it? I mean
certtool -i --infile /etc/courier/esmtpd.pem
or
openssl x509 -text -in /etc/courier/esmtpd.pem
Both tools read the file without errors and display the certificate
informations, the modulus, the
Il 19/07/2017 17:06, Matus UHLAR - fantomas ha scritto:
Il 19/07/2017 15:46, PICCORO McKAY Lenz ha scritto:
you sould recreate and then test it!
On 19.07.17 15:57, Lucio Crusca wrote:
Forgot to mention, but I did remove the courier packages, the
/etc/courier folder, the APT package cache
Il 19/07/2017 16:00, PICCORO McKAY Lenz ha scritto:
do you reported again debian bug tracker? using reporbug ?
Well no, but before reporting I'd like to be sure it's not my fault.
--
Check out the vibrant tech
Il 19/07/2017 15:46, PICCORO McKAY Lenz ha scritto:
you sould recreate and then test it!
Forgot to mention, but I did remove the courier packages, the
/etc/courier folder, the APT package cache and reinstalled.
During reinstallation the system created the self signed certificate
again,
Il 19/07/2017 12:56, Sam Varshavchik ha scritto:
Check the server's certificate, esmtpd.pem. That's the only certificate
in play here. The file is probably corrupted.
At first glance it seems ok, the structure is the same as another file
in another Courier server I run that works correctly
Hello,
I've just installed a new Courier instance in a new Debian GNU/Linux 9
amd64 server from distro packages.
This Courier should act as smart relay for another server and nothing else.
So far I've enabled courier-mta and courier-msa systemd services,
changed the ports they listed on and
Hello,
I've just edited my .mailfilter. Is it possible to run it once again for
every already delivered message in my INBOX root maildir only, so that
maildrop moves my messages in the respective new subfolders, according
to the new .mailfilter rules?
It now works: Markus kindly sent me his patch and his custom maildrop
2.8.4 deb package, because he's currently short of time to keep up with
the conversation here.
I tried to apply his patch to maildrop 2.8.5 sources. The patch gets
applied, but configuration fails afterwards for some reason
I wrote:
> Is it enough to edit that line, make it look like
> #ifndef HAVE_COURIER
>#define HAVE_COURIER
> #endif
>
> and configure/make/install?
I answer myself: no it isn't, because I've tried and that leads to a
compile error. Then I've also tried just commenting out the #undef,
I wrote:
> What does exactly mean to compile maildrop with HAVE_COURIER? I coulnd't find
> any
> such option in ./configure and the generated Makefile does not include
> it either.
I've had a look at the current maildrop stable sources (2.8.5). In the
file libs/maildrop/config.h.in I see:
Markus Wanner writes:
> Is this the Debian stretch installation mentioned?
>
Yes it is.
> I'm successfully running a courier installation on Debian stretch with
> maildrop compiled manually, ATM.
Thanks for sharing, I'm afraid that's what I need to do too. What does
exactly mean to compile
Sam Varshavchik writes:
> From the logs, you've configured spamd to be responsible for delivering
> mail
>
> You have to take smaller steps, and get one thing working, at a time.
I've now moved spamd out of the way. My previous DEFAULTDELIVERY was
Hello,
I'm still configuring the new server. The 456 error is resolved, thanks,
but now I have a new problem.
Looking at log files, it seems local delivery is ok. Here is an example
of my logs for a test message from GMail to i...@usosalix.com:
May 14 01:05:57 maxwell courieresmtpd:
Hello,
I'm trying to configure a new Courier-MTA server at
maxwell.virtualbit.it. It's a Debian 9 Stretch system behind a NAT (kvm
virtualization) and the installed Courier is the Debian packaged version
(0.76.3).
I already have another Courier-MTA working at nmx.sulweb.org. This is a
Il 28/11/2016 23:53, Sam Varshavchik ha scritto:
>
> Make dlinguistico's account's group id and user id match the ones used
> for those mailman lists.
>
Now I really feel like an idiot.
It works, thanks.
--
Il 28/11/2016 18:33, Lucio Crusca ha scritto:
> In the former case I have no
> aliases, but virtual users in userdb [...] In the latter
> case (dlinguistico2002@lists...) instead I have one single account
That's not the problem. I've tried creating one account for each alias
l
Hello,
I have mailman 2.1.18 and courier 0.73 as packaged by Debian on a Debian
Jessie GNU/Linux server.
They correctly run a few mailing lists, but now I've tried adding a new
one and it does not work, with mailman reporting the "Group mismatch
error" to the Courier MTA mail server, with
Il 03/11/2016 00:02, Sam Varshavchik ha scritto:
>
> No, as the manual page explains, the address is "alias", not
> "catchall". It should be "al...@usosalix.org".
>
As a feedback, I might suggest that the manpage is not that clear (at
least to me) in explaining the fact that the address name
Il 02/11/2016 23:23, Sam Varshavchik ha scritto:
> Based on this description, you must be listing your virtual domains in
> the hosteddomains file, and using "makehostedomains".
Yes, I'm doing just that.
> This is documented in the makehosteddomains manual page: the address
>
Il 02/11/2016 21:13, Gordon Messmer ha scritto:
> You probably want to start with the "VIRTUAL DOMAINS" section of the
> "makealiases" man page.
Thanks, now I've read it. I assume you are referring to the this part:
"The following special syntax implements a virtual domain. A virtual
domain
My Courier server hosts several virtual domains, and I'm trying to
configure a catch all address only for a few of the hosted domains. All
the mail accounts are listed in /etc/courier/userdb.
I've read dot-courier manpage, but I almost certainly got it wrong. To
my understanding, when the
Hello,
I receive several spam emails from forged email addresses and so do my
customers. Most of the forged addresses are from one of the hosted
domains to a real user of the same hosted domain (scan...@sulweb.org and
the like).
Is it possibile to block messages apparently coming from one of
Hello,
I'm trying to add DKIM signatures to outgoing messages. I've followed this
guide [1], but my feeling is that nothing is happening, as far as DKIM is
concerned.
How do I test my setup? Are there any logs that tell me what zdkimfilter is
doing?
1.
Hello,
I have a Courier mail server with virtual users (authuserdb) and a
number of hosted domains. Every virtual user has its Maildir, but all of
them are owned by a single real system user id 5000 (username is
mailboxes).
I want to configure fetchmail so that the messages it fetches from a
Hello all,
here are the first four lines of my .mailfilter file
(lucio_at_sulweb_dot_org account):
if (/^X-Spam-Flag: Yes/)
{
to Maildir/.spam/
}
The system wide DEFAULTDELIVERY includes SpamAssassin:
# cat /etc/courier/courierd | grep ^DEFAULTDELIVERY
Il 03/07/2015 11:01, Matus UHLAR - fantomas ha scritto:
On 03.07.15 02:25, Lucio Crusca wrote:
I've tried to dig some random domains and it turns out that my local
Bind fails most of the time...
fails how?
SERVFAIL. E.g.
$ dig @localhost -t mx kernel.org
; DiG 9.9.5-9-Debian
Hello everybody,
mxtoolbox says that my SMTP is slow: http://mxtoolbox.com/domain/sulweb.org/
It's a Debian GNU/Linux 8.1 64bit kvm guest, 6 vCPUs, 2GB of RAM and a
load average that is almost always below 0.5.
iptables blocks OUTPUT to 113/tcp with REJECT.
courier show all shows only one domain
Sam Varshavchik wrote:
• Added AUTH_MKHOMEDIR_SKEL to several config files, an optional
setting. The first login or mail to an account creates the account's
home directory.
Wow that's great news, thanks a lot! But, out of curiosity, what changed
since 2011 in that regard?
Sam Varshavchik writes:
Given what you posted, the only possibilities are slow DNS lookups.
Each incoming IP address is resolved, forwards and backwards, via DNS.
Additional, the domain of the sender's address is also looked up in DNS.
If you have poor network connectivity, your DNS
Hello,
I have a courier-mta server that relays mail for authenticated clients and a
few websites with contact forms. Mail coming from the websites is also
authenticated (I've created a userid and password in Courier userdb database
and configured nullmailer on the websites server to use my
Hello,
I've just moved two lists from a old mailman installation to a new mailman on
a new server (old server is Debian 6, new server is Debian 8).
Both the old and the new server run Courier and correctly relay SMTP messages
for authenticated users and for localhost. However the new server is
In data giovedì 19 marzo 2015 14:04:58, Matus UHLAR - fantomas ha scritto:
Do you _need_ to move to new hardware?
Yes I do, but, more importantly, I'm forced to move to a new IP address.
If you need to upgraqde your hardware, you can set up the new server, copy
user settings and data, and
Sam Varshavchik writes:
BOFHBADMIME was removed in 0.66.0
What's the behaviour of newer courier versions in case of bad mime messages?
--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy
In data martedì 9 ottobre 2012 01:55:49, Sam Varshavchik ha scritto:
Lucio Crusca writes:
Aruba mail services here are considered to be standard and working also
when they do not work, because many people use them. You can look at it
as if it were a de-facto standard.
If you're going
Sam Varshavchik writes:
Lucio Crusca writes:
I ask that because I already have opt BOFHBADMIME=accept in place, I
know that it implies opt MIME=none and I don't feel like changing it
if it hasn't
No, the two are independent settings. The first one controls what gets
accepted
I resume this old thread because I think now I have found a possible
workaround.
In data sabato 14 luglio 2012 05:11:51, Sam Varshavchik ha scritto:
Correct. This is an error message from the remote mail server.
and not Courier itself, I suspect
In data lunedì 8 ottobre 2012 14:30:33, Sam Varshavchik ha scritto:
Well, since mail delivery for them is such a low priority, I see no reason
why anyone else has to be concerned, either.
Sure. However it happens I have two customers. The first buys email service
from me. The second buys
Hello *,
Courier 0.65/Debian, for a particular message, says:
---
UNDELIVERABLE MAIL
Your message to the following recipients cannot be delivered:
i...@domain.com:
mx.domain.com
Hello *,
I'd like to add antispam features to my courier-mta setup. Historically I've
been using spamassassin at other sites (postfix), and going further back in
history, some DSN blacklists with an ancient version of courier (back in 2005
or so).
Now I wish to use both things, a false
Thanks for all the replies about RFC 1035.
Now I have a related problem. I set up /etc/courier/esmtproutes this way:
domain.com: [mx.host.ip.address]
and restarted courier. Now messages relayed through my courier to that domain
pass ok, but messages from that domain to one of the courier
In data venerdì 29 giugno 2012 12:46:45, Sam Varshavchik ha scritto:
No, esmtproutes is used when sending mail only.
Ok, the problem in this case has been solved anyway, I mailed the tech contact
for the domain and they fixed their DNS. And they lived happily ever after.
However, in order to
Hello *,
courier-0.65 here (Debian). For a particular domain, courier refuses to
deliver messages because it violates RFC 1035. Correct, it actually does and I
added it to esmtproutes for the time being. However the same domain has two MX
records configured. One violates RFC since it's in the
Alessandro Vesely wrote:
For example, Lucio's server could have matched the bad MX 20
of domain.com, unable to recognize its own IP address because it sits
behind a NAT, and unable to recognize its own name since the DNS hid
it. If it had used the good MX record by default, it would have
Hello,
is it possible to have messages subject logged in /var/log/mail.log?
The problem is I need to distinguish, in the logs, between messages sent by a
web-app from other messages, but the same sender address must be set both in
the web-app and in the the web-app owner's email client, so I
Hello all,
I'm trying to put into production my brand new courier setup.
I use authuserdb for the time being. I have one hosteddomain and the same
domain is listed in esmtpacceptmailfor, let's call it mydomain.com.
I have virtual accounts along with a system user with uid=5000 and a system
In data mercoledì 14 dicembre 2011 15:33:00, Lucio Crusca ha scritto:
Dec 14 15:13:09 myserver courieresmtpd:
error,relay=:::81.174.67.47,from=info@virtual-
bit.com,to=i...@mydomain.com: 450 Service temporarily unavailable.
Dec 14 15:13:09 myserver courieresmtpd:
error,relay=::
In data martedì 6 dicembre 2011 14:18:30, Mark Constable ha scritto:
I've been know to cd /var/lib/courier and grep for the message IDs in
the actual queue and manually rm them, then restarted courier.
It worked like a charm!
Here is the pipeline I used (I wanted to delete all messages in queue
Hello,
one of my server has been infested by a botnet. Now I've cleaned it up, but I
still have a mailq that shows 299 messages on queue (spam). However if I try
to cancel any of those messages I get
Message not found.
from cancelmsg. Does that mean the message has aldreay been
In data sabato 12 novembre 2011 01:38:36, Sam Varshavchik ha scritto:
If you want maildirs, this is what you're going to get.
Ok.
with shared mail folders in terms of metadata. But I'm sure that there has
to be at least a few other IMAP servers that you can look at.
Got a link by any chance?
Hello *,
I have a Courier ESMTP server and I like to configure the HELO string it hands
off remote SMTP servers when it sends outgoing mail.
The problem is that many remote servers refuse the mail coming from my server
because:
« Helo command rejected: need fully-qualified hostname »
How do
In data martedì 27 settembre 2011 23:49:25, Sam Varshavchik ha scritto:
Lucio Crusca writes:
7. some users share a common mailbox (info@). They SHOULD see unread
messages as unread, even when another user has already read that same
messages
Although that's possible when using
In data giovedì 29 settembre 2011 20:14:12, Alessandro Vesely ha scritto:
You seem to conflate having clear text passwords on the DB with
accepting clear text passwords on the wire. They are two different
issues.
I know that, but I suspect there's a misunderstanding here. When Sam
In data mercoledì 28 settembre 2011 17:35:18, Alessandro Vesely ha scritto:
I mean: ok I can't have hash-based auth, If I want to store encrypted
passwrods I'm forced to plain text. That has only one downside AFAIK,
i.e. the password goes on air in plain text, but I can solve this
problem
In data martedì 27 settembre 2011 23:49:25, Sam Varshavchik ha scritto:
Passwords can be changed via webmail, with some additional setup. They can
be stored encrypted, however you must realize that fundamental laws of this
universe will not allow you to use hash-based authentication via IMAP
In data mercoledì 28 settembre 2011 12:55:47, Sam Varshavchik ha scritto:
Ok, I assume however I can use plain text password over SSL/TLS, right?
Yes, but that's a separate configuration issue. Whether you're going to
allow non-encrypted IMAP, POP3, or HTTP connections is separate from
Hello *,
I'm new here but I've been using courier for 10 years. Mostly courier-imap,
but a few years ago I've also used courier-mta. Then I moved to a mixed setup
with Postfix+courier-imap+MySQL.
Now I have a new server to configure (Ubuntu 10.04 server) and I'm quite
annoyed by the postfix
Hello everybody,
I'm trying to switch my courier-(esmtpd+pop+imap) server
from authuserdb to authmysql.
I'm using sarge packages (I know many people here don't
like them, but that's the way things are, sorry).
Authmysql seems to work correctly, because I can login into
accounts defined only
Martin Schuster wrote:
http://www.backports.org/
_please_ :)
No. I badly want only official sarge packages on that server. Muhahahaha.
Maybe try with an absolute path instead of a relative one.
I've tried putting /home/posta/domain.com/prova directly into
home field and commenting
Hello everybody,
I have a courier-esmpt server where I want to create a mailing list with
mailman. Courier uses virtual accounts only, and every virtual account maps
to a single UID (1004) and GID (1004) on the host machine.
So far I've created the necessary accounts ([EMAIL PROTECTED], [EMAIL
I wrote:
Is there a way to tell courier that, for those accounts, it should run the
dotcourier instructions with GID=daemon? Maybe right into each dotcourier
file?
Sorry for the silly question. It obviously can be done in the userdb file...
Lucio.
Chuck Williams wrote:
have been wondering why the official debian packages are so old
Is there a reason that these are not in
the main debian respository?
Yes, there is. But, first of all, I guess what you are talking about is not
the main debian repository (which does include newer
Hello *,
I have courier-esmtp, imap and pop 0.47 up and running on a Debian GNU/Linux
Sarge x86 server. Authdaemon uses authuserdb.
Can I alias a whole domain such that messages to [EMAIL PROTECTED] are
automatically delivered to [EMAIL PROTECTED] (I don't want
to alias every single address
Stefan Hornburg wrote:
The Debian maintainer (myself) doesn't like them either and points you
to up-to-date packages for sarge:
http://debian.linuxia.de courier-test main
Do those packages have something more than sarge ones that is useful to solve
my problem (domain alias)? Otherwise I
I replied only to Pawel Tecza by mistake, here is the copy of my message for
the list.
-- Forwarded message --
Subject: Re: [courier-users] domain alias
Date: 09:52, giovedì 6 luglio 2006
From: Lucio Crusca [EMAIL PROTECTED]
To: Pawel Tecza [EMAIL PROTECTED]
Pawel Tecza wrote
Hello *,
I have a Courier ESMTP server (0.47 on Debian GNU/Linux i386) configured to
block mail coming from blacklisted addresses:
BLACKLISTS=-block=blackholes.mail-abuse.org,BLOCK
Now I need to whitelist a particular MX, but I've not found how to do that.
Can you help me please?
Using
65 matches
Mail list logo
