Re: [courier-users] Pythonfilter attachments

On 07/25/2017 09:53 AM, Alessandro Vesely wrote: I've published my alternative version here: https://www.tana.it/sw/pythonfilter_attachments/ I'll take a look at that shortly. Thanks. -- Check out the vibrant tech

Re: [courier-users] sendmail removes bcc header unconditionally

Just tested my sentfolder filter, and the new Bcc: support works nicely. Thanks for your help, Sam. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org!

Re: [courier-users] sendmail removes bcc header unconditionally

On 07/06/2017 05:09 PM, Sam Varshavchik wrote: Yeah, github was a couple of commits behind. Just pushed everything out, and it's up to date now. Thanks, again. Is this an accurate update to the sendmail document? diff --git a/courier/courier/doc/sendmail.sgml

Re: [courier-users] sendmail removes bcc header unconditionally

On 07/06/2017 01:58 PM, Sam Varshavchik wrote: This is a reasonable position to make, so I'll change this. Thanks very much, Sam. If you push a patch into git (github looks a bit out of date?) I'll test it. Or, if you'd rather, I can modify sendmail and send a patch.

Re: [courier-users] sendmail removes bcc header unconditionally

On 07/06/2017 03:54 AM, Sam Varshavchik wrote: Would it work to simply use a custom header name instead of "Bcc:". Most email clients won't show it by default, but it's going to be there and can be looked at, in some way; and the email clients will also ignore it if the message is replied to.

[courier-users] sendmail removes bcc header unconditionally

I'm working on improving my "sentfolder" mail filter. This filter works like GMail's SMTP system, copying messages that a user sends into their sent folder, so that messages only need to traverse the network once. Courier IMAP has a better option, but no client support to speak of. I've

Re: [courier-users] setuid/setgid problem, mail from website not sent

On 07/05/2017 11:33 AM, Bernd Plagge wrote: What can I do to solve this problem? First, "setenforce permissive" and send a message, or examine /var/log/audit/audit.log to see if this is an SELinux denial. Next, in permissive mode, use "tail -f /var/log/audit/audit.log | grep AVC" to watch

Re: [courier-users] szmlink counts as quota

On 05/18/2017 06:31 PM, SZÉPE Viktor wrote: Could it be that that Courier counts Sent folder size three time while calculating quota? Can you test this patch? diff --git a/maildir/maildirquota.c b/maildir/maildirquota.c index 3f3e0bd..3ff78f1 100644 --- a/maildir/maildirquota.c +++

Re: [courier-users] Loading / reloading Pythonfilter

On 06/07/2017 04:32 AM, Alessandro Vesely wrote: Last time I issued courierfilter stop, and then start. However, that way I have to reload also clamav databases, which takes a long time. Is there any better way to upgrade the running Python process? That should only be the case if you were

Re: [courier-users] 456 Address temporarily unavailable

On 05/13/2017 12:53 AM, Lucio Crusca wrote: > Now for the problem. Out of 6 accounts. 5 do work correctly. For one of > them Courier replies "456 Address temporarily unavailable". > "courier clear" on maxwell does not change the reply I get afterwards. In case it helps: you probably want to look

Re: [courier-users] Latest Courier+Amavisd-new+clamav install guide

On 03/27/2017 12:14 AM, Vytautas Kasparavičius wrote: > Is somwhere guide to integrate latest versions amavisd-new and clamav > into courier? The README included in the amavisd distribution looks like it's still relevant. Your other options for Clamav integration are Courier::Filter and

Re: [courier-users] monitoring prgram times out

On 03/26/2017 09:44 AM, SZÉPE Viktor wrote: Running bind is too expensive for me. I'll note that Red Hat's bind package installs with an ideal configuration for a localhost-only caching DNS server. There's virtually no administrative cost, there. I usually use the caching DNS resolver in

Re: [courier-users] journald logging

On 03/22/2017 01:32 AM, Bernd Plagge wrote: > It seems that you're running journal without syslog, rsyslog or syslog-ng. Is > this correct? The default configuration for CentOS 7 runs journald as the primary log recipient ("lsof /dev/log" will show systemd and systemd-journal), and rsyslogd

Re: [courier-users] Spam filtering on SMTP level

On 03/21/2017 09:27 AM, Bernd Wurst wrote: > I pushed my changes to the greylist filter in my github-repo > https://github.com/bwurst/courier-pythonfilter > > Gordon has received a pull request. I see the PR, yes, but the pythonfilter repo is on bitbucket:

Re: [courier-users] journald logging

On 03/21/2017 02:12 AM, Bernd Plagge wrote: > Now I find imap and pop messages in the log but no delivery result or > messages about incoming mails. It seems that half of the Courier messages > does not make it into the journal. I'm seeing all of the expected logs, including courierd entries,

Re: [courier-users] Build 20170309 of Courier packages

No problems seen yet, on a test host. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___

Re: [courier-users] Build 20170309 of Courier packages

On 03/15/2017 06:17 PM, Sam Varshavchik wrote: > Ok, this actually turned out to be a small typo. Fixed in the > just-uploaded 20170315, and it builds for me. courier-unicode does build. However, I'm unable to build the new courier package with it installed (also under mock).

Re: [courier-users] Build 20170309 of Courier packages

On 03/11/2017 11:20 AM, Sam Varshavchik wrote: > • A few more tweaks to the courier-unicode configuration script. Building in mock fails on CentOS 7: https://paste.fedoraproject.org/paste/knoYv8gNHfxhfF3flIz6EF5M1UNdIGYhyRLivL9gydE=

Re: [courier-users] RBL answers

On 03/10/2017 11:00 AM, SZÉPE Viktor wrote: > CloudFlare is also retiring ANY queries. > > https://blog.cloudflare.com/deprecating-dns-any-meta-query-type/ "We aware of only two programs that issue ANY queries: Un-patched versions qmaild..." I laughed at that one. :)

[courier-users] RBL answers

I was checking the RBL queries and answers on a server this morning, when I noticed this in the responses: Please stop asking for ANY.See draft-ietf-dnsop-refuse-any Both spamhaus and abuseat provide this text in their replies to Courier's RBL lookups. Is it worth considering A and TXT

Re: [courier-users] Spam filtering on SMTP level

On 03/02/2017 09:58 PM, Bernd Wurst wrote: > But I'd still like to know where to submit patches when We extend something. You can email them to me directly, or you can fork the code on bitbucket and send a pull request: https://bitbucket.org/gordonmessmer/courier-pythonfilter

Re: [courier-users] Spam filtering on SMTP level

On 02/28/2017 08:27 AM, Lindsay Haisley wrote: > Gordon Messmer has done an excellent job with this package, its API, and with > the documentation for it. That's very kind. I'll note that as much as possible, the pythonfilter API is simply a direct reflection of the mechanisms used in C

Re: [courier-users] Future of Courier MTA

On 02/18/2017 04:45 PM, Mark Constable wrote: Is Ondřej still the package maintainer? Not really, this explains Ondřej's position... I'd seen that, but I'm not intimately familiar with the Debian maintenance process. I'm not sure if, to adopt the package, we should contact Ondřej, or if

Re: [courier-users] Future of Courier MTA

On 02/16/2017 03:36 PM, SZÉPE Viktor wrote: > Is anyone willing to cooperate with me on fixing Debian-related errors? > https://github.com/szepeviktor/courier Well, I just sent some more patches to the FreeBSD maintainer to bring the package up to date. I think I can put in some effort to help

Re: [courier-users] Pythonfilter attachments

On 02/08/2017 10:24 AM, Alessandro Vesely wrote: > I revamped attachments.py in order to catch Javascript Trojans inside > a zip, which were driving me crazy. The current version supports libarchive, which should allow you to blacklist file types inside zip files, as well.

Re: [courier-users] Error message from Remote Server

On 01/27/2017 11:33 PM, Michelle Konzack wrote: > On 2017-01-27 15:13:39 Gordon Messmer hacked into the keyboard: >> What TLS settings have you specified in /etc/courier/courierd? > [ c 'grep TLS /etc/courier/courierd' ]-- > >

Re: [courier-users] Error message from Remote Server

On 01/27/2017 02:59 PM, Michelle Konzack wrote: > <<< 500 couriertls: connect: error:14094410:SSL > routines:SSL3_READ_BYTES:sslv3 alert handshake failure What TLS settings have you specified in /etc/courier/courierd?

[courier-users] Patches from FreeBSD

While working on updating the FreeBSD port, I noticed a few patches that may be appropriate for merging. First, the test for -lcourier-unicode seems to be slightly deficient. All of the AC_CHECK_LIB checks successfully locate libs in /usr/local/lib, but AC_LINK_IFELSE doesn't seem to.I

Re: [courier-users] Configure Scripts Not Finding Resources Installed on FreeBSD

On 12/26/2016 08:57 PM, Michael S. Scaramella, Esq. wrote: My project to install and configure Courier on our DigitalOcean hosted FreeBSD 11.0 based VPS is now substantially further along. It's a little late to be of help, but I've sent patches for the courier-authlib and courier "ports" to

Re: [courier-users] Disable adding own hostname to sender's address

On 01/23/2017 08:08 AM, Michelle Konzack wrote: The documentation for this is buried in the submit(8) man page. ...but not in my manpage! What version are you running? -- Check out the vibrant tech community on one

Re: [courier-users] Best practize for $USER -> EMail

On 01/20/2017 04:22 AM, Michelle Konzack wrote: > All the users where created on as "normal" UNIX users and > there login name is also there email address. So, now you can imagine, > that this give problems if is responsable for different domains, > where maybe two users have the same

Re: [courier-users] DNS, was lo is down

On 12/29/2016 02:16 AM, Alessandro Vesely wrote: From that, I derive that production mail servers should run a caching[*] DNS server/locally/. That's also necessary for DNSxL, SPF, DKIM, and the like. Do you agree? I think that a caching DNS server should be as near as possible to the

Re: [courier-users] lo is down

On 12/28/2016 02:07 PM, Lindsay Haisley wrote: > This generally removes any dependency on DNS for resolving "localhost". Courier uses DNS for everything that comes to mind. Modifying /etc/hosts won't resolve the problem in question.

Re: [courier-users] lo is down

On 12/28/2016 01:38 PM, SZÉPE Viktor wrote: > Thank you Gordon! > > After a quick tcpdump. > Monit sends: > > EHLO localhost > QUIT What is the value for TCPDOPTS in /etc/courier/esmtpd? That test should work if you have -nodnslookup set (though I don't recommend that). If it's not set, as in

Re: [courier-users] lo is down

On 12/28/2016 11:02 AM, SZÉPE Viktor wrote: > Could it be that Courier unbinds from localhost when eth0 is down? If Monit is testing SMTP on localhost, there are a bunch of possible causes of failure. The most likely, I would think, is that DNS is not available so one of the SMTP commands

Re: [courier-users] maildrop: Timeout quota exceeded

On 12/11/2016 10:47 AM, Mike - st257 wrote: > The user's mailbox is large enough (my opinion, at a few Gigabytes) > that crawling the entire maildir will take an extremely long time. If you want to measure this (approximately), wait for an off-peak time of day, flush the caches, and measure

Re: [courier-users] maildrop: Timeout quota exceeded

On 12/09/2016 07:55 AM, Mike - st257 wrote: > I don't yet have an answer why that file was present (doesn't exist in > my mailbox on that system), but moving it aside resolves the present > mail delivery problem. That file's presence indicates that a Maildir++ has a quota, and is used to

Re: [courier-users] Release quarantine messages - pythonfilter

On 12/07/2016 01:12 AM, Bernd Plagge wrote: > However, I always got a message saying that the message was not found > So, I wrote a small program to list the keys in the database: > > /var/lib/pythonfilter/quarantine# ./dbmtest.pl msgs.db > 203720L Seems you've hit a bug in pythonfilter. I

Re: [courier-users] How to test imap idle

On 11/16/2016 05:05 PM, David Niklas wrote: > There is a read, write and execute bit what is the t bit? As explained in the chmod(1) man page, the t bit is the restricted deletion flag. More information is available in the man page.

Re: [courier-users] catch all for one domain only

On 11/02/2016 11:36 AM, Lucio Crusca wrote: > Could you please help me understand what's wrong with my configuration? You probably want to start with the "VIRTUAL DOMAINS" section of the "makealiases" man page. In general, though, catch-all addresses are going to receive so much spam that

Re: [courier-users] A pythonfilter module for recent gibberish spam

On 09/22/2016 02:11 PM, Lindsay Haisley wrote: > Gordon, take a look at this code and if you have any suggestions please > post them. Do you have a sample of the messages this targets? --

Re: [courier-users] Verify sender email only for hosted domains

On 09/06/2016 08:04 AM, Lucio Crusca wrote: > Is it possibile to block messages apparently coming from one of the > hosted domains that use a non existing address as sender? courier-pythonfilter includes a filter named "localsenders" which does exactly that.

Re: [courier-users] Management of maildir structures

On 07/23/2016 12:05 PM, Lindsay Haisley wrote: the Wikipedia article at on maildirs which state that the internal management of files in the new, tmp and cur directories is the responsibility of the client's MUA ("When the mail user agent (MUA) In this

Re: [courier-users] Blocking Brute Force Auth Attacks

On 07/08/2016 03:04 PM, Alexei Batyr' wrote: > > Unfortunately spamers/fishers et al. already mastered SSL and STARTTLS and > successfully use them in brute force and other attacks. I'd expect so. I didn't recommend TLS as a measure against brute-force attacks, I recommended it to protect

Re: [courier-users] Blocking Brute Force Auth Attacks

On 07/08/2016 09:54 AM, Nathan Harris wrote: > Gordon, first let me start with a big thank you for pythonfilter which I > have used for years. Cool. Glad to hear it! > As far as rejecting/disabling smtp authentication, I was not aware there was > a setting for this. Authentication over

Re: [courier-users] Blocking Brute Force Auth Attacks

On 07/08/2016 06:49 AM, Nathan Harris wrote: > Is there anything more > sophisticated or a better approach to solving this problem? I'd recommend that you not allow authentication on any non-encrypted protocols, and that'll only leave log analysis tools like fail2ban as options.

Re: [courier-users] Disable SSL for esmtpd on port 25

On 05/27/2016 05:39 AM, Matus UHLAR - fantomas wrote: > Aha... doesn't couriertls produce an error when too low tls version is tried > by the client? It should, but the "SSL23" message that Mark originally mentioned don't really indicate that the clients are using SSL2 or SSL3 (as best I can

Re: [courier-users] Disable SSL for esmtpd on port 25

On 05/27/2016 11:02 AM, Alessandro Vesely wrote: > but wait, why do I miss the STARTTLS=server part? Logs will look slightly different for builds on OpenSSL and those on gnutls. That'd be my guess. -- What NetFlow

Re: [courier-users] handle spam

On 04/09/2016 02:53 AM, SZÉPE Viktor wrote: > I've just read onhttp://psky.me/ > ... > How is it possible to implement deferring with Courier MTA? Before I remove this from my todo list, I wanted to note that I attempted to contact the site for clarification on their recommended use. In

Re: [courier-users] vacation notices

On 05/19/2016 04:14 AM, Harry Duncan wrote: > I have just deployed courier 0.76 and tested this feature, but it > doesn't seem to work. Am I testing right or this was taken back out of > the server? That feature (which I was previously unaware of) requires some setup, which you haven't

Re: [courier-users] DNS lookup problem

On 05/11/2016 12:31 PM, Bowie Bailey wrote: > $ testmxlookup westportyachtsales.com > westportyachtsales.com: soft error. Have you checked for errors in your DNS server's logs? -- Mobile security can be enabling, not

Re: [courier-users] pythonfilter

On 05/11/2016 02:28 AM, Jérôme Blion wrote: > eg: > attachments > auto_whitelist whitelist_auth whitelist relayclients greylist > clamav > spamassassin > > What will happen when whitelist_auth will send a 2xx code ? Multiple words on a single line are only used if the second word is "for". In

Re: [courier-users] Migrating old messages

On 05/11/2016 03:46 AM, MK wrote: > What are my options here? The one I'd recommend is: Set up the IMAP account on each client. Create a folder structure on the IMAP server that matches the client. Copy the content of each folder from the old, local folders into the new IMAP folders.

[courier-users] pythonfilter

https://bitbucket.org/gordonmessmer/courier-pythonfilter A new release of pythonfilter is available with two new features. A new "sentfolder" module allows a site to copy messages sent by authenticated users to those users' Sent maildir, and whitelist modules can now bypass specific filters,

Re: [courier-users] Manipulating outgoing messages

On 05/06/2016 09:44 AM, SZÉPE Viktor wrote: > Thank you! > > How will the message land in the Sent folder? https://bitbucket.org/gordonmessmer/courier-pythonfilter/src/3ac9d9109e808bfe1f3df7582cff30e139397795/README?at=default=file-view-default The documentation includes a section on

Re: [courier-users] Manipulating outgoing messages

On 05/04/2016 07:09 PM, Gordon Messmer wrote: > Seems reasonably straightforward. I'll give it a shot. https://bitbucket.org/gordonmessmer/courier-pythonfilter/ A "sentfolder" module has been added for anyone else who

Re: [courier-users] Manipulating outgoing messages

On 05/04/2016 06:27 PM, Mark Constable wrote: > We can do almost anything with incoming mail using maildrop but is > there anything we can do to manipulate outgoing mail, per user? That's an interesting idea. Courier implements send-by-IMAP, but I don't know of any clients that support it.

Re: [courier-users] ./configure option to install sendmail in /usr/sbin

On 04/14/2016 02:38 AM, cour...@rcdrun.com wrote: > only that does not install sendmail in /usr/sbin where most other > software expects it to be. On rpm based systems, the "alternatives" tool will be used to put several links where they're expected: /usr/sbin/alternatives --install

Re: [courier-users] to much error DNS lookup failed, but testsmxloookup show good

On 04/13/2016 03:06 PM, PICCORO McKAY Lenz wrote: > a question, why before was working and then now not? the only change > was a ip change, due are dhcp! I don't know, but I might guess that the IP address that was previously assigned to your host had a PTR record in DNS that contained a fully

Re: [courier-users] to much error DNS lookup failed, but testsmxloookup show good

On 04/13/2016 03:23 PM, PICCORO McKAY Lenz wrote: > hi again, setup hostname to localhost.localdomian Clearly, I should have been more specific. You must use a fully qualified hostname that resolves in DNS. /etc/hosts is not used. localhost.localdomain is not valid.

Re: [courier-users] to much error DNS lookup failed, but testsmxloookup show good

On 04/13/2016 02:14 PM, PICCORO McKAY Lenz wrote: > vnxpos00:/home/lavka# cat /etc/courier/defaultdomain > vnxpos00 > > this its correct? Nope, it requires a fully-qualified hostname. -- Find and fix application

Re: [courier-users] to much error DNS lookup failed, but testsmxloookup show good

On 04/13/2016 12:23 PM, PICCORO McKAY Lenz wrote: > Apr 13 14:01:36 vnxpos00 courieresmtp: > id=4109.570E8E30.68BC,from=,addr= > >: DNS lookup failed. > > i got ERROR DNS lookup failed, but i'm browsing web with

Re: [courier-users] Best practice for SMTP level spam filter

On 04/11/2016 03:56 PM, Sam Varshavchik wrote: > maildrop's embedded mode runs for RCPT TO, and DATA commands. > Additionally, when using the embedded in the default configuration, > Courier will defer, using 4xx, recipients that do not have the > embedded mode filter activated. Thanks for

Re: [courier-users] handle spam

On 04/09/2016 09:25 AM, SZÉPE Viktor wrote: > Looking at Gordon's greylist.py that would be the "remember" part, and > combining it with DNSBL lookup from whitelist_dnswl.py ... > but:( I am not a python developer. Sounds like another use case for making individual filters conditional. It's on

Re: [courier-users] Best practice for SMTP level spam filter

On 04/11/2016 12:22 PM, Jeff Potter wrote: > Gordon, could one potentially change the replies after the first RCPT TO to > 4xx responses, to ensure the incoming message is being delivered to exactly > one user? Not exactly. Courier's mail filtering API only issues one call, after the body is

Re: [courier-users] Best practice for SMTP level spam filter

On 04/09/2016 09:19 PM, Bernd Wurst wrote: > We use delivery by .courier files for both, local user accounts / > aliases and virtualdomains. Spam filtering happens with some custom > scripts inside the .courier files and therefore only deletion, sorting > or bouncing is available. Bouncing mail,

Re: [courier-users] How to disable ipv6

On 03/30/2016 05:02 PM, Sam Varshavchik wrote: > As such, in order for IPv6 reverse DNS to work, your internet provider > has to delegate reverse DNS to you. They could, but I'm not sure why they would have to. Most of the ISPs and hosting providers that I've worked with (Integra, Qwest,

Re: [courier-users] error setting STARTTLS when send, unable to set security mode

On 03/17/2016 09:44 AM, PICCORO McKAY Lenz wrote: > 2016-03-17 11:49 GMT-04:30 Gordon Messmer <gordon.mess...@gmail.com > <mailto:gordon.mess...@gmail.com>>: > > Is it executable by the user that esmtpd is running as? Use "ps aux | > grep esmtpd.pid

Re: [courier-users] error setting STARTTLS when send, unable to set security mode

On 03/17/2016 01:37 PM, PICCORO McKAY Lenz wrote: > i researching, whell i used the 0.62 version, seems here startls are > not the default Looks like it's on by default in http://packages.ubuntu.com/wily/amd64/courier-mta/download

Re: [courier-users] error setting STARTTLS when send, unable to set security mode

On 03/17/2016 07:10 AM, PICCORO McKAY Lenz wrote: > > but either /usr/lib/courier/bin/couriertls (specified in COURIERTLS in > the esmtpd file) is not executable, > > verified and its executable! works perfectly i read manual about if > this program are not present in installation will

Re: [courier-users] error setting STARTTLS when send, unable to set security mode

On 03/17/2016 11:34 AM, PICCORO McKAY Lenz wrote: > > ESMTP_USE_STARTTLS=1 > > That's was the solution, setting that solved the problem! Perfect. Note that this *is* the default configuration. Did you change it previously, or is the Ubuntu maintainer turning that off for some reason?

Re: [courier-users] error setting STARTTLS when send, unable to set security mode

On 03/16/2016 06:16 AM, PICCORO McKAY Lenz wrote: > Mar 10 07:35:40 vnxpos00 courieresmtp: > id=00094183.56E08E51.488D,from= . > ve>,addr= >: 400

Re: [courier-users] error setting STARTTLS when send, unable to set security mode

On 03/15/2016 02:29 PM, PICCORO McKAY Lenz wrote: > i intall as i mention as standar with all features, when i send a mail > without the -S parameter, got also and error that said starttls its > required! Please include the complete entry from the log.

Re: [courier-users] error setting STARTTLS when send, unable to set security mode

On 03/15/2016 01:51 PM, PICCORO McKAY Lenz wrote: > i compiled with all supported featured then install and then try7 to > send and got the error that i mention in my firts mail I wish I knew hot to be more clear about this. Your first email documents a failure that happened because you used

Re: [courier-users] error setting STARTTLS when send, unable to set security mode

On 03/14/2016 06:34 PM, PICCORO McKAY Lenz wrote: > i mean, i > need to send a mail to a mail domain that requires message must be > encrypted .. ashttps://en.wikipedia.org/wiki/STARTTLS ? If the remote domain is capable of STARTTLS, it will be used. You don't have to take any special steps.

Re: [courier-users] error setting STARTTLS when send, unable to set security mode

On 03/11/2016 05:23 PM, PICCORO McKAY Lenz wrote: > my remote dain has startls, so from other server cannot send to that domain.. I'm sorry, I don't know what you mean. > and in my documentation does not said that! > was always propietary? The man page for sendmail, where I assume you find "-S

Re: [courier-users] error setting STARTTLS when send, unable to set security mode

On 03/10/2016 07:21 AM, PICCORO McKAY Lenz wrote: > How can i send main with courier wrapper sendmail due i cannot send > using starttls mails to servers that need this!!! > echo "Subject: tests" | /usr/sbin/sendmail -S starttlsreceivedm...@gmail.com As described in the documentation, that is a

Re: [courier-users] [courier-pythonfilter] comeagain proposed patch

On 03/08/2016 05:21 PM, Jérôme Blion wrote: > What do you think about that? I'd like to do something more general to make filters conditional on the results of others, but I haven't given it the time... Maybe something like: whitelist_auth conditional comeagain if not whitelist_auth

Re: [courier-users] blacklist for courier how?

On 03/03/2016 06:32 PM, PICCORO McKAY Lenz wrote: 2016-03-02 21:38 GMT-04:30 Gordon Messmer <gordon.mess...@gmail.com <mailto:gordon.mess...@gmail.com>>: my courier used the OS pam authentication ... my port 25 its authenticated by default... and also the ssl port too I'm not s

Re: [courier-users] blacklist for courier how?

On 03/01/2016 05:35 PM, PICCORO McKAY Lenz wrote: > 2016-03-01 14:05 GMT-04:30 Gordon Messmer <gordon.mess...@gmail.com > <mailto:gordon.mess...@gmail.com>>: > > Any user that authenticates is allowed to relay, so I'd think > that's the > part you nee

Re: [courier-users] How do I make BLOCK2 available to maildrop in delivery mode?

On 03/01/2016 05:01 AM, Christopher Rüprich wrote: > I'd like to make > the result available to a maildrop-script in delivery mode, so I can > deliver junk-mails directly to the users junk-folder. No such feature exists, AFAIK. While it's slightly ugly, the least amount of work will probably be

Re: [courier-users] blacklist for courier how?

On 03/01/2016 07:51 AM, PICCORO McKAY Lenz wrote: > i mean, user"pepet...@dominio.co" can send mails to externals but > rest of users does not able to send outside domain ... Any user that authenticates is allowed to relay, so I'd think that's the part you need to protect. One option would be

Re: [courier-users] Re-processing dropped mail (in /var/mail/$USER) through Courier/procmail

On 02/29/2016 03:56 AM, Greg Earle wrote: > (Forgive the Senior Moment - I know I was able to do this once before, > but I've forgotten how.) I believe you were looking for "formail -s" which is also part of the procmail package. You could use Courier's sendmail to re-inject the messages in

Re: [courier-users] problem with authentication modules

On 02/18/2016 09:49 AM, György Kövesdi wrote: > An error occurred while sending mail. The mail server responded: > Mailbox unavailable . Sounds like a delivery failed to that mailbox. Check your logs for messages that were accepted and then failed to deliver to the

Re: [courier-users] using .mailfilters

On 02/09/2016 10:55 AM, André Rothe wrote: > The .mailfilter calls a Bash script, which builds a current list of > ruleset files, which the .mailfilter includes again. And if you have two simultaneous deliveries, there is some risk that mailfilters/list will be empty when one of the maildrop

Re: [courier-users] using .mailfilters

On 02/09/2016 07:19 AM, André Rothe wrote: > My first idea was to include the files witin .mailfilter: > include "/path/to/my/home/.mailfilters/*" .mailfilters is used by maildrop's embedded mode. Those files should not be mixed with delivery mode instructions (the .mailfilter file), AFAIK. As

Re: [courier-users] What config option controls -access=

On 01/01/2016 07:48 PM, Mark Constable wrote: > I'm actually helping the guy putting some 0.75 > *buntu packages together ... while we're talking about it, why is he re-writing the init script, anyway? It seems to me that most of the problems that Debian and Ubuntu users have with Courier are

Re: [courier-users] What config option controls -access=

On 01/01/2016 07:48 PM, Mark Constable wrote: > These new 0.75 deb packages for "wily" (15.10) are proving ornery > because the packager has changed uid:gid from the previous "daemon" > user that Debian has used for a decade to the more common "courier" > user (in line with Archlinux and maybe

Re: [courier-users] setgid(1) and setuid(1)

On 01/02/2016 01:22 AM, Mark Constable wrote: > My question; does that setgid(1) and setuid(1) mean to change to the > uid:gid of 1:1? Yes. > Which probably means the packages I am testing are built with some kind > of internal daemon:daemon permissions whereas all external files are > given

Re: [courier-users] What config option controls -access=

On 12/31/2015 10:01 PM, Mark Constable wrote: > My /etc/courier/imapd file has ACCESSFILE=/etc/courier/smtpaccess and yet > these 2 daemon instance below show -access=.dat. > > Where do I set whatever affects the -access argument? /usr/lib/courier/sbin/imapd references $IMAPACCESSFILE

Re: [courier-users] Storing the original recipient

On 12/21/2015 04:31 PM, Ángel González wrote: > The Received line would be an unobstrusive place to put it (written in > submit.C:getrcpts(), where it's available), at least for single- > recipient mails. But just a line at mail.log would work, too. pythonfilter has a filter that does exactly

Re: [courier-users] too few deliveries

On 12/11/2015 05:15 AM, Szépe Viktor wrote: > I've set MAXDELS to 100 and I expect Courier to deliver to 100 servers > simultaneously. > But I cannot reach it. Try "courier flush" The "MAX" setting is just that: a cap. It doesn't mean that courier will always attempt 100 deliveries

Re: [courier-users] performance question

On 11/12/2015 04:45 AM, Jan Müller wrote: > 13gb email in user inboxes (6 users) ... > Also, we are having problems with Thunderbird, our current imap > client. It's slow. It's global index, which should speed up searching, > has many UX problems and does not find every message. Any suggestions

Re: [courier-users] Pythonfilter - Variation in spammer NS behavior

On 09/24/2015 08:00 AM, Lindsay Haisley wrote: > Gordon, your thoughts? The one thing that consistently seems to be missing from your analyses is a review of legitimate mail. name-services.com appears to be used by eNom, Name Cheap, and Rackspace. I'm sure that it's used by a lot of spammers,

Re: [courier-users] Messages to a non-existing address

On 09/18/2015 01:23 PM, Alexey Mishustin wrote: > But why is it being delivered to /var/spool/mail? Because you have a user named "mail" and that is its home directory: $ getent passwd mail mail:x:8:12:mail:/var/spool/mail:/sbin/nologin As a standard practice, you should make that address a

Re: [courier-users] courier-pythonfilter with Python3

On 07/25/2015 01:12 AM, Szépe Viktor wrote: Does anyone have experience with courier-pythonfilter in Python3? Modern OS-es have Python3 as a standard package. Sorry about no answer earlier. I've been very busy lately, and just returned home from my honeymoon. pythonfilter hasn't been ported

Re: [courier-users] fetchmail + maildrop to virtual user

On 07/12/2015 10:37 AM, Lucio Crusca wrote: mda '/usr/bin/maildrop -dlu...@sulweb.org' ... How do I configure fetchmail and maildrop with virtual users? '-d' might be restricted? Try running fetchmail without the mda specified at all. Fetchmail will deliver through SMTP, where we

Re: [courier-users] Icedove + Roundcube don't get along anymore with Courier

On 07/08/2015 08:40 AM, Julien Patriarca wrote: It's now working except for RoundCube. What does your roundcube configuration look like? Specifically, post all of the ssl/tls related options. Are you using a client certificate?

Re: [courier-users] Icedove + Roundcube don't get along anymore with Courier

On 07/08/2015 09:32 AM, Julien Patriarca wrote: // -- // IMAP // -- $rcmail_config['default_host'] = 'ssl://localhost'; That's not going to work unless localhost is in the certificate SubjectAltName or CN. Use the hostname that

Re: [courier-users] 0.75

On 07/06/2015 04:14 AM, Sam Varshavchik wrote: Looks to me like someone added these SELinux entries ages ago, before courier-authlib became a separate package, and nobody has maintained these entries ever since. authlib has contexts defined, too. That's not the problem. I don't know who

  1   2   3   4   5   6   7   8   9   10   >