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

2016-09-06 Thread Lucio Crusca
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 t

[courier-users] catch all for one domain only

2016-11-02 Thread Lucio Crusca
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 recip

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

2016-11-02 Thread Lucio Crusca
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 re

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

2016-11-02 Thread Lucio Crusca
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 > "alias@hosteddoma

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

2016-11-03 Thread Lucio Crusca
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 yo

[courier-users] Mailman "Group mismatch error"

2016-11-28 Thread Lucio Crusca
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 "dae

Re: [courier-users] Mailman "Group mismatch error"

2016-11-28 Thread Lucio Crusca
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

Re: [courier-users] Mailman "Group mismatch error"

2016-11-28 Thread Lucio Crusca
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. -- __

[courier-users] 456 Address temporarily unavailable

2017-05-13 Thread Lucio Crusca
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 product

[courier-users] Message delivered, but no message in INBOX

2017-05-13 Thread Lucio Crusca
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: started,ip

Re: [courier-users] Message delivered, but no message in INBOX

2017-05-14 Thread Lucio Crusca
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 DEFAULTDELIVERY="|/usr/bin/spamc|/usr/bin/maild

Re: [courier-users] Message delivered, but no message in INBOX

2017-05-14 Thread Lucio Crusca
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 mail

Re: [courier-users] Message delivered, but no message in INBOX

2017-05-16 Thread Lucio Crusca
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: #unde

Re: [courier-users] Message delivered, but no message in INBOX

2017-05-16 Thread Lucio Crusca
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, buildin

Re: [courier-users] Message delivered, but no message in INBOX

2017-05-16 Thread Lucio Crusca
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

[courier-users] Rerun .mailfilter?

2017-07-15 Thread Lucio Crusca
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?

[courier-users] courieresmtpd: STARTTLS failed: Certificate is bad

2017-07-19 Thread Lucio Crusca
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

Re: [courier-users] courieresmtpd: STARTTLS failed: Certificate is bad

2017-07-19 Thread Lucio Crusca
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 (

Re: [courier-users] courieresmtpd: STARTTLS failed: Certificate is bad

2017-07-19 Thread Lucio Crusca
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, b

Re: [courier-users] courieresmtpd: STARTTLS failed: Certificate is bad

2017-07-19 Thread Lucio Crusca
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 communit

Re: [courier-users] courieresmtpd: STARTTLS failed: Certificate is bad

2017-07-19 Thread Lucio Crusca
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 and

Re: [courier-users] courieresmtpd: STARTTLS failed: Certificate is bad

2017-07-19 Thread Lucio Crusca
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 signatu

[courier-users] virtual mailboxes

2011-09-27 Thread Lucio Crusca
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 me

Re: [courier-users] virtual mailboxes

2011-09-28 Thread Lucio Crusca
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

Re: [courier-users] virtual mailboxes

2011-09-28 Thread Lucio Crusca
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 >

Re: [courier-users] virtual mailboxes

2011-09-29 Thread Lucio Crusca
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 > > p

Re: [courier-users] virtual mailboxes

2011-09-29 Thread Lucio Crusca
In data mercoledì 28 settembre 2011 14:31:21, Sam Varshavchik ha scritto: > That only works well until the mailboxes get moved to a network mount, and > one day the server gets rebooted and, for whatever reason, can't bring up > the mount. Then, the mail server starts happily delivering mail and >

Re: [courier-users] virtual mailboxes

2011-10-02 Thread Lucio Crusca
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 Varshavc

Re: [courier-users] virtual mailboxes

2011-11-11 Thread Lucio Crusca
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 > > Al

Re: [courier-users] virtual mailboxes

2011-11-15 Thread Lucio Crusca
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 chanc

[courier-users] How to configure HELO?

2011-11-15 Thread Lucio Crusca
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 I

[courier-users] mailq and cancelmsg

2011-12-05 Thread Lucio Crusca
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 cancelled/de

Re: [courier-users] mailq and cancelmsg

2011-12-06 Thread Lucio Crusca
In data lunedì 5 dicembre 2011 13:03:02, Mark Constable ha scritto: > Don't worry it just takes a while for the messages to hit their retry > timeout and really get removed from the mailq. I'm afraid that's not the case. Today my mailq still has 290 messages on queue for delivery (same spam messa

Re: [courier-users] mailq and cancelmsg

2011-12-06 Thread Lucio Crusca
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 queu

[courier-users] 450 Service temporarily unavailable

2011-12-14 Thread Lucio Crusca
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 grou

Re: [courier-users] 450 Service temporarily unavailable [SOLVED]

2011-12-14 Thread Lucio Crusca
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= bit.com>,to=: 450 Service temporarily unavailable. > Dec 14 15:13:09 myserver courieresmtpd: > error,relay=:::81.174.67.47

[courier-users] subject in logs

2012-02-15 Thread Lucio Crusca
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 ca

[courier-users] RFC 1035

2012-06-26 Thread Lucio Crusca
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 f

Re: [courier-users] RFC 1035

2012-06-26 Thread Lucio Crusca
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 >

[courier-users] esmtproutes ignored while receiving

2012-06-29 Thread Lucio Crusca
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 hosted

Re: [courier-users] esmtproutes ignored while receiving

2012-06-29 Thread Lucio Crusca
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 b

[courier-users] what about antispam?

2012-07-06 Thread Lucio Crusca
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 negati

[courier-users] Invalid 7bit data

2012-07-13 Thread Lucio Crusca
Hello *, Courier 0.65/Debian, for a particular message, says: --- UNDELIVERABLE MAIL Your message to the following recipients cannot be delivered: : mx.domain.com [xx.xx.xx.xx]: >>> DATA <<<

Re: [courier-users] Invalid 7bit data

2012-10-08 Thread Lucio Crusca
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 > >

Re: [courier-users] Invalid 7bit data

2012-10-08 Thread Lucio Crusca
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 soft

Re: [courier-users] Invalid 7bit data

2012-10-09 Thread Lucio Crusca
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 sta

Re: [courier-users] Invalid 7bit data

2012-10-09 Thread Lucio Crusca
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 a

Re: [courier-users] Invalid 7bit data

2012-10-11 Thread Lucio Crusca
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

[courier-users] Planning migration

2015-03-19 Thread Lucio Crusca
Hello all, I have a production courier-mta server (along with imap and pop) with a number of domains and mailboxes, authentication through userdb. It's a old Debian GNU/Linux 6.0 server with packaged courier-mta 0.65. I plan to migrate it to a new server with Debian GNU/Linux 8.0 and packaged c

Re: [courier-users] Planning migration

2015-03-20 Thread Lucio Crusca
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 c

[courier-users] relaying denied

2015-05-03 Thread Lucio Crusca
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

Re: [courier-users] relaying denied

2015-05-04 Thread Lucio Crusca
In data domenica 03 maggio 2015 18:08:43, Sam Varshavchik ha scritto: > My guess would be that mailman makes a connection not to localhost, but to > the hosts's public IP address, so you just need to add the host's public IP > address. I've added the host public IP address to smtpaccess, but nothi

[courier-users] gmail, yahoo and esmtpauthclient

2015-05-06 Thread Lucio Crusca
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 Cour

[courier-users] slow transactions

2015-07-02 Thread Lucio Crusca
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 domai

Re: [courier-users] Courier 0.75 released

2015-07-02 Thread Lucio Crusca
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? http://source

Re: [courier-users] slow transactions

2015-07-02 Thread Lucio Crusca
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 l

Re: [courier-users] slow transactions

2015-07-03 Thread Lucio Crusca
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 ;

[courier-users] Double spam filter

2015-07-08 Thread Lucio Crusca
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 DEFAULTDELIVERY="|/usr/bin/spamc|/usr/

[courier-users] fetchmail + maildrop to virtual user

2015-07-12 Thread Lucio Crusca
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

[courier-users] zdkimfilter

2015-10-05 Thread Lucio Crusca
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. http://www.tana.it/sw/zdkimfilter/v-0.5.

[courier-users] authuserdb -> authpam

2006-06-22 Thread Lucio Crusca
Hello everybody I'm new here with a newbie problem, cause google didn't help. I have a courier mail server (esmtp + pop + imap) in production since two years ago: authdaemon has always been using authuserdb, but now I want to switch to authpam. I've created a test pam account ([EMAIL PROTECTED])

[courier-users] whitelisting a blacklisted ip addr

2006-06-29 Thread Lucio Crusca
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 Tomc

[courier-users] domain alias

2006-07-06 Thread Lucio Crusca
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 on

Re: [courier-users] domain alias

2006-07-06 Thread Lucio Crusca
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

Re: [courier-users] domain alias

2006-07-06 Thread Lucio Crusca
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]>

[courier-users] [OT] Debian versions [was: Re: domain alias]

2006-07-07 Thread Lucio Crusca
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 package

[courier-users] Courier-esmpt + Mailman + virtual users

2006-11-21 Thread Lucio Crusca
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

Re: [courier-users] Courier-esmpt + Mailman + virtual users

2006-11-21 Thread Lucio Crusca
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. -

[courier-users] authmysql + esmtp

2006-12-06 Thread Lucio Crusca
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 in

Re: [courier-users] authmysql + esmtp

2006-12-06 Thread Lucio Crusca
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 MYSQL_M

[courier-users] maildropfilter and spamassassin

2006-12-22 Thread Lucio Crusca
Hello list, I need to setup two maildropfilters so that: filter on account1 sends a CC of every message to account2 in the same domain. filter on account2 moves spam to /dev/null and ham to default Maildir. I need this because I'm going to check mail for a while via GPRS, so I need to downlo

Re: [courier-users] maildropfilter and spamassassin

2006-12-22 Thread Lucio Crusca
Flavio Stanchina wrote: > Rather, move suspected spam to a subfolder (named "Spam", maybe) and just > don't look at it when you're on GPRS. I'd like I could, but for other reasons, I have also to move the ham off the mailserver (which is not what I've said before, but now it's what I have to do).