Re: [courier-users] Backup MX, was Courier::Filter rejecting over-zealously
Ben Kennedy writes: Sam Varshavchik wrote at 7:07 AM (-0400) on 8/10/11: That's an interesting and clever approach. Would this properly pass through ad hoc local-part extensions, e.g. for mail addressed to user- someth...@example.com - user-someth...@mailhost.example.com? No, it wouldn't. Well, that rules out that approach, then. thanks, Well, it depends on how much work you want to do. If there's only a handful of email addresses in that domain, you can set it up as a virtual domain, which simply maps it to a local mailbox, and you set up forwarding addresses via .courier files. With a careful arrangement of .courier-x-default files, and with careful usage of environment variable, you should be able to craft fairly sophisticated forwarding rules. pgpjsFoEJhZ1J.pgp Description: PGP signature -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-dev2dev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] auth=backup ?? error in relaying spam
Andrew C Burnette writes: Hi all, (and thanks Mr. Sam for the awesome MTA software on my server for close to a decade now!) I get examples like this in my log file: Aug 6 11:38:04 localhost courierd: newmsg,id=00B1E707.4E3D5FCE.673E, auth=backup: dns; User ([202.109.133.181]) which invariably turns out to be a successful attempt to relay spam Do you have a system userid named backup? As in your /etc/passwd file. pgpXNUQssGp3z.pgp Description: PGP signature -- BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos much more. Register early save! http://p.sf.net/sfu/rim-blackberry-1___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] link error
Alexei Batyr' writes:
Hello Sam,
I've tried to compile latest development Courier snapshot on FreeBSD 8.2
amd64 (libtool 2.4) and got these errors:
Making all in en-us
/bin/sh ./libtool --tag=CC--mode=link gcc -g -O2 -Wall -I.. -I./..
-static -L/usr/local/lib -o showmsg2html showmsg2html.o libwebmail.la
-lcrypt
libtool: link: gcc -g -O2 -Wall -I.. -I./.. -o showmsg2html showmsg2html.o
-L/usr/local/lib ./.libs/libwebmail.a /usr/local/lib/libidn.so
/usr/local/lib/libintl.so /usr/local/lib/libiconv.so
/usr/local/lib/libgdbm.so -lcrypt -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath
-Wl,/usr/local/lib
./.libs/libwebmail.a(cgi.o)(.text+0x5b8): In function `enomem':
/usr/local/src/courier/courier/cgi/cgi.c:69: undefined reference to `error'
Strange. It's definitely missing, when I work out the linkage manually --
the code in question is not used by this specific binary -- but I must be
resolving the symbol to something; or gcc/binutils must be optimizing out
the unused code, and its undefined reference.
Just append the definition for error() into showmsg2html.c:
void error(const char *p)
{
fprintf(stderr, %s\n, p);
exit(1);
}
pgpxhyNbErVIe.pgp
Description: PGP signature
--
10 Tips for Better Web Security
Learn 10 ways to better secure your business today. Topics covered include:
Web security, SSL, hacker attacks Denial of Service (DoS), private keys,
security Microsoft Exchange, secure Instant Messaging, and much more.
http://www.accelacomm.com/jaw/sfnl/114/51426210/___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] link error
Alexei Batyr' writes: Just FYI, I still have following warnings (gcc version 4.2.1 20070719 [FreeBSD]): config.status: WARNING: 'courier.service.in' seems to ignore the --datarootdir setting gpg: WARNING: unsafe permissions on homedir `conftempdir' unicode.c: In function 'convert_flush_iconv': unicode.c:962: warning: passing argument 2 of 'libiconv' from incompatible pointer type rfc2047.c: In function 'encodeqp': rfc2047.c:325: warning: comparison is always false due to limited range of data type config.status: WARNING: 'mkpop3dcert.html.in' seems to ignore the --datarootdir setting config.status: WARNING: 'mkpop3dcert.8.in' seems to ignore the --datarootdir setting folder.c: In function 'charset_warning': folder.c:1593: warning: comparison is always false due to limited range of data type newmsg.c: In function 'newmsg_init': newmsg.c:539: warning: unused variable 'checkspelling' newmsg.c:538: warning: unused variable 'checkspellingdone' config.status: WARNING: 'courierperlfilter.8.in' seems to ignore the --datarootdir setting config.status: WARNING: 'courierperlfilter.html.in' seems to ignore the --datarootdir setting config.status: WARNING: 'couriermlm.1.in' seems to ignore the --datarootdir setting config.status: WARNING: 'courier.8.in' seems to ignore the --datarootdir setting config.status: WARNING: 'mkesmtpdcert.8.in' seems to ignore the --datarootdir setting config.status: WARNING: 'courier.html.in' seems to ignore the --datarootdir setting config.status: WARNING: 'couriermlm.html.in' seems to ignore the --datarootdir setting config.status: WARNING: 'mkesmtpdcert.html.in' seems to ignore the --datarootdir setting All these warnings are fine. pgp38aTSTp0lM.pgp Description: PGP signature -- 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Aliases for a virtual domain
Mark Constable writes: I thought I understood how this works but apparently not. I want all mail to a virtually hosted domain to go to a single acount. I'm trying out this... ~ grep -r qtmoz.org /etc/courier | sort /etc/courier/aliases/system:@qtmoz.org: ad...@renta.net --- /etc/courier/esmtpacceptmailfor.dir/default:qtmoz.org /etc/courier/hosteddomains/default:qtmoz.org Binary file /etc/courier/aliases.dat matches Binary file /etc/courier/esmtpacceptmailfor.dat matches Binary file /etc/courier/hosteddomains.dat matches but I'm still getting this error below... Jul 17 16:40:10 smtp courieresmtp: id=0001815B.4E2283C4.6E91, from=x...@gmail.com,addr=ad...@renta.net-ma...@smtp.renta.net: configuration error: mail loops back to myself (MX problem). I'm not sure where the loops back to myself comes from or the ad...@renta.net-ma...@smtp.renta.net construction? Virtual @domain addresses get written using 'me' for the domain. If you do not have 'me', the results of gethostname get used instead. That's where smtp.renta.net comes from. From the makealiases page: The following special syntax implements a virtual domain. A virtual domain redirects all mail for an entire domain to one user: @domain: user This special entry results in any recipient address of the form foo@domain to be rewritten as user-foo@me, where me is the hostname of the machine, which we expect to be a local domain. In your case user=ad...@renta.net, me=smtp.renta.net, domain=qtmoz.org, and foo=markc, so user-foo@me becomes ad...@renta.net-ma...@smtp.renta.net ~ cat /etc/courier/me smtp.renta.net ~ cat /etc/courier/locals localhost pgpg3SZLRbULW.pgp Description: PGP signature -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Aliases for a virtual domain
Mark Constable writes: On 2011-07-17 07:04 AM, Sam Varshavchik wrote: /etc/courier/aliases/system:@qtmoz.org: ad...@renta.net --- ... I'm not sure where the loops back to myself comes from or the ad...@renta.net-ma...@smtp.renta.net construction? Virtual @domain addresses get written using 'me' for the domain. If you do not have 'me', the results of gethostname get used instead. That's where smtp.renta.net comes from. From the makealiases page: So to avoid the loops back to myself error I may need to put just renta.net in /etc/courier/me rather than the FQDN of smtp.renta.net. Maybe. To avoid confusion, the following rule of thumb applies: Any domain with an A or an MX record that resolves to any IP address on a machine, should be listed either in locals, hosteddomains, or esmtpacceptmailfor, whatever the case may be. Alternatively, the domain may not be listed in any of these three, but then a list of aliases must be specified for each valid email address in that domain. A virtual domain alias meets this requirement. In your case that's @qtmoz.org But then the second part of the rule of thumb is that one of the domains listed in locals or hosteddomains needs to be identified as the machine's primary domain, and either set as the hostname, or given in the me file. This is the part that you're probably missing. You only have localhost listed in locals. Whatever you put in me, needs to be in locals or hosteddomains, too. Additionally, the virtual domain alias should specify just the name of the local mailbox, admin. Okay I get most of that except the foo=markc bit. Where does this part of courier pick up the markc part? Oh, from the LHS of the incoming mail. So spam to various users @qtmoz.org will go to different destinations. Hmm, I'm definitely confused. Perhaps I should simply ask how do I best redirect all incoming mail for a virtual domain (qtmoz.org in this case) into a single local mailbox? A virtual domain alias is the first step. The second step is to install a .courier-default in admin's account. What it all boils down to is that you're aliasing u...@qtmoz.org to the address admin-user. Install a .courier-default in admin's home directory to put all mail for any user into the same mailbox. That's what webadmin does, when that option is selected for a domain. pgpelvU8ek4fB.pgp Description: PGP signature -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Out of office replies
Harry Duncan writes: Hi Guys, I'm receiving an increasing number of requests for out of office functionality, primarily driven by users who would have come from a microsoft exchange environment in previous jobs. We currently provide sqwebmail as an interface to configure maildrop autoreplies, but users it seems want it easier. Just wondering if anybody has discovered a client side method of configuring maildrop for this purpose from windows clients? The only client side interface is via sqwebmail and maildrop. pgpYgGiumhsms.pgp Description: PGP signature -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Fatal error: Invalid argument using IMAP via Windows Live Mail
Dieter Knopf writes: Hello, i have problems with Courier IMAP (4.9.1-1+b1) and Windows Live Mail as Client. The customer used Windows Live Mail for a long time but sometimes it's suddenly stopped working After opening the connection the client says: Fatal error: Invalid argument and closes the connection. (server not responding) The Live Mail error code is 0x800ccc0f (should be a connection problem, but it isn't) I tested some other accounts and they worked well. After removing some mails from the INBOX it's working again. But why? It seems like a malformed email in the INBOX. Is there a way to fix this? I already searched but found nobody with a similiar problem, but there are many Courier servers out there. Sounds like a bug that was fixed in 4.9.3. pgpNx6G67vi6L.pgp Description: PGP signature -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Fatal error: Invalid argument using IMAP via Windows Live Mail
Dieter Knopf writes: 2011/7/6 Sam Varshavchik mr...@courier-mta.com: Sounds like a bug that was fixed in 4.9.3. Thanks for the info. This bug? imap/msgenvelope.c (msgappends): Fix a fatal error upon encountering 8-bit header content. Heuristically try to interpret it as UTF-8, and just ignore invalid UTF-8 sequences. Thanks, and sorry for the duplicate posting. Correct; and I see no dupes. pgpFQliVTj9mI.pgp Description: PGP signature -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Combining delivery instruction and mailbot instruction
Goutam Baul writes: If the .mailfilter file contain the line to /abcd then the messages are getting delivered to the folder /abcd Unlikely. First of all, the folder name should be quoted. Also, this would deliver to whatever /abcd is on your filesystem. If we simply combine both the commands in a single file as different lines then we are getting syntax error. This indicated that you made a typo. pgpoEv91qXuRF.pgp Description: PGP signature -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Certificate authority invalid
Mark Constable writes: Courier 0.66.1 x86_64 and I just got a new RapidSSL certificate and restarted the esmtpd-ssl and imapd-ssl daemons and now I can't connect via SSL, with a client side error of... Trusted: NO, there were errors. The certificate authority's certificate is invalid and not trusted for this purpose... the certificate cannot be verified for internal reasons. Some googling indicated that the email address in the cert must be available for local authentication so I added it. The pems are not world readable and comprise a concatenated *.key and *.crt provided by the cert authority. RapidSSL chained from GeoTrust (I guess). Do I have to provide the CA file to courier? Yes, if you're using a certificate signed by a CA that your client does not have in its built-in list of trusted CAs, and your CA's certificate includes a signature from a trusted CA, then you need to combine your CA's cert with your own cert. For Courier, convert your intermediate CA cert to a PEM format, if it's not already provided in PEM format, and concatenate it with your own cert file. I never remember if the intermediate cert must be before or after your cert in the certificate file. I believe after, so just append your CA cert file in PEM format to your own cert. pgpGPc1HTjc7P.pgp Description: PGP signature -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Problem with aliases
Wagner Pereira writes: Hi, folks. I'm facing a aliases problem with my Courier-mta 0.53. I have aliases like this: m...@pop-sp.rnp.br: user1, user2 (according to the documentation) ...and it was working OK, but suddenly stopped to work! I already created a new .dat file (makealiases -alias=newfile.dat) but didn't back to run. This is a legacy system for me and in the /var/log all the logs are zero lenght! So where can I start to troubleshooting that? You need to get your mail logs working. pgpqE92PEjS9w.pgp Description: PGP signature -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] New development builds of Courier packages
Download: http://www.courier-mta.org/download.php Builds dated 20110619 of the following packages: _courier_, _courier-imap_, _sqwebmail_, _courier-authlib_, and _courier-sox_. === Changes * Fixed several gcc 4.6 warning messages * Updated rpm packages for Fedora 15 will now use systemd for service startup. When updating to rpm packages created from these builds, some of the rpm updates will blurt out an error message that can be ignored. pgp879M3s8aoI.pgp Description: PGP signature -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] v6 localhost smtpaccess
Zenon Panoussis writes: 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 You're one nybble short there: ::::::::0001allow,RELAYCLIENT This should be in smtpaccess/default. I'm going to add it. pgpMhtbIKMdFC.pgp Description: PGP signature -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Sending FAX using T.38
Michelle Konzack writes: Hello *, currently I use courier-faxmail and it works perfectly using an old and payed USR Sportster Vi 14400 connected to an Vodafone EasyBox 803 A, but this makes not realy sense, because the EasyBox supoort T.38 FAX So my questions are: 1) Does someone has already build scripts with courier-faxmail using T.38? 2) Which commandline tools exist, to send PS and PDF using T.38? (In case, I have to write my own scripts with some maildrop and or /procmail rules) Courier hands off all the stuff to sendfax, for faxing. The support, if any needs to be in sendfax. pgp3DkxNAyfoM.pgp Description: PGP signature -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Backup MX, was Courier::Filter rejecting over-zealously
Ben Kennedy writes: Hey folks, Some of you may recall this discussion from last fall. I've got a problem, one that I guess my servers have exhibited for years, and I want to fix it. I have two machines, which I'll call primary and secondary. They are both MX for a number of domains; primary has a lower priority number (i.e. is a first choice for delivery), and holds the canonical backing store (maildirs, POP3/IMAP service, etc). Secondary is designed to also accept mail for these domains, and shunt any it happens to receive (by virtue of esmtproutes) to primary. Both have mailbox configuration provided by authmysql from a local replicated MySQL database. In case primary goes down, secondary will continue to queue mail and, at my option, may be quickly switched into primary behvaiour (to deliver locally and provide POP3/IMAP service) in the event that the original primary cannot be brought online in a timely fashion. I have used this pattern for several years now, with general success. The gaping hole, of course, is that the secondary will accept any mail for any mailbox on any of the domains. For domains with alias@... style catch-alls, this is fine. For the rest, it induces the primary into spewing out backscatter for any undliverable addresses. As I said, both machines share the mailbox config, and therefore have the capability of knowing what is a legitimate address and what isn't. But on the secondary, which has empty hosteddomains and esmtproutes pointing to the primary, it never bothers to do an account lookup (it only looks at the domain). How do I fix this? Only a machine which has a domain configured as a local/hosted domain can know which address in the domain exists, or not. One thing you can do is redefine a local domain. If you are example.com, rather than defining example.com as a local domain, define instead mailhost.example.com as a hosted domain, and install an alias u...@example.com: u...@mailhost.example.com Mail addressed to u...@example.com gets rewritten to be addressed to u...@mailhost.example.com, which would be a valid local mailbox. Nonexistent addres...@example.com get rejected because example.com is not a local domain. Adresses that exist get rewritten and delivered. It should be a simple matter to write a script to dump your list of mailboxes, generate an alias entry for each valid mailbox, then run makealiases. I believe that if you do that, you can install the same alias table on your secondary, and on the secondary put mailhost.example.com into esmtpacceptmailfor, so that mail for that domain gets accepted and queued. If you've got mail queued up on the secondary, and want to make it a primary, you will need to stop courier, remove mailhost.example.com from esmtpacceptmailfor, and put it into hosteddomain, and start courier, and it should then deliver the queued up mail into local mailboxes. You'll need to do some experimenting to verify this, but I'm fairly certain that it'll work. pgpdoOa65UWPs.pgp Description: PGP signature -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] make: *** [couriertls] Error 1
kibirango moses writes: I got the errors below: usr/local/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_globallookup': dso_dlfcn.c:(.text+0x1a): undefined reference to `dlopen' dso_dlfcn.c:(.text+0x31): undefined reference to `dlsym' dso_dlfcn.c:(.text+0x3b): undefined reference to `dlclose' /usr/local/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_pathbyaddr': dso_dlfcn.c:(.text+0x84): undefined reference to `dladdr' dso_dlfcn.c:(.text+0x111): undefined reference to `dlerror' /usr/local/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_bind_func': dso_dlfcn.c:(.text+0x42e): undefined reference to `dlsym' dso_dlfcn.c:(.text+0x4ae): undefined reference to `dlerror' /usr/local/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_bind_var': dso_dlfcn.c:(.text+0x52e): undefined reference to `dlsym' dso_dlfcn.c:(.text+0x5be): undefined reference to `dlerror' /usr/local/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_unload': dso_dlfcn.c:(.text+0x617): undefined reference to `dlclose' /usr/local/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_load': dso_dlfcn.c:(.text+0x6d7): undefined reference to `dlopen' dso_dlfcn.c:(.text+0x735): undefined reference to `dlclose' dso_dlfcn.c:(.text+0x76c): undefined reference to `dlerror' collect2: ld returned 1 exit status make: *** [couriertls] Error 1 Could anybody out there help on fixing these errors. Why did you build openssl as a static library? You should build it as shared library. When you're linking statically you need to explicitly list all dependencies. Here, it needs to be linked with -ldl. pgpKEbUkozIs8.pgp Description: PGP signature -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Problem with courier-imap and android phone
Bowie Bailey writes: I have an imap mailbox that I can connect to and use just fine with Thunderbird, but my android phone has started giving connection errors. It is successfully logging in, but something is happening after that. I believe this started happening after I went in with Thunderbird and cleaned out a bunch of old messages from the inbox (there are still 650 messages in the inbox). Some Google searches led me to the IMAPDEBUGFILE option. This gave me a bit more information. Everything looks good until I get this: BODYSTRUCTURE ((text plain (charset utf-8) NIL NIL 7bit 2573 61 NIL (inline NIL) NIL)(text html (charset utf-8) NIL NIL 7bit 15219 119 NIL (inline NIL) NIL) alternative (boundary =_bnofmail.buc.com-27944-1306404480-0001-2) NIL NIL)) * 2421 FETCH (UID 38892 FLAGS (\Seen) INTERNALDATE 26-May-2011 15:05:12 -0400 RFC822.SIZE 12906 ENVELOPE (Thu, 26 May 2011 13:04:53 -0600 24 Hours Left for onOne Software Discounts ((onOne Software NIL enews email.ononesoftware.com)) ((onOWRITE: * BYE [ALERT] Fatal error: Invalid argument It consistently fails on the same message every time. If I delete that message, it will start failing on a different one. Any ideas? What version is this? This might be a bug that's been fixed in 4.9.3 pgpjMddFTGNqH.pgp Description: PGP signature -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] New release of courier and courier-imap packages
Download: http://www.courier-mta.org/download.php * this release fixes a fatal error in the IMAP server when a message contains garbage in its headers. pgpawOZBex0Ty.pgp Description: PGP signature -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Minor release of Courier packages
Download: http://www.courier-mta.org/download.php Minor release of ''courier'', ''courier-imap'', ''sqwembail'', ''maildrop'' and ''cone'' packages. === Changes * Fix compilation issues on some platforms * Deal with broken quoted-printable MIME encoding from some clients that generaet lowercase hexadecimal characters, oblivious to the uppercase requirement in RFC 2045. pgpVmkkzoVKs5.pgp Description: PGP signature -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] install vchkpw2userdb
Frederico Madeira writes: Hi guys, I'm tring to setup an installation of vpopmail with courrier-imap. Reading URL:http://www.inter7.com/courierimap/INSTALL.html#vchkpwhttp://www.inter7. com/courierimap/INSTALL.html#vchkpw I see that we use authuserdb to authenticate our users and I need vchkpw2userdb script to generate a /etc/courier/userdb.dat file. Where can I find the installation of this script vchkpw2userdb ? vpopmail has been removed from courier-authlib a long time ago. It could not be reasonably supported. That is an old page that nobody should be using any more. Update your bookmark to http://www.courier-mta.org/imap If you have an existing system based on vpopmail, you can export the list of accounts, and convert it to any supported account management scheme, mysql, postgresql, or ldap. pgpU0p2Q5uGlH.pgp Description: PGP signature -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Backscatter supression
Peter Ford writes: I've been getting the dreaded 556 error occasionally for an address on our server (sa...@justcroft.com), and I can't quite diagnose the problem. The address points to a couriermlm list, and normally goes fine, then every so often the BSS kicks in and customers complain they can't reach the address - it is the main point of contact for most of our customers, so pretty critical for our business. The problem is, I can't see any evidence of an error delivering to that address which might be sparking off the BSS. Given that it's a list, would a failed delivery to one of the list addresses do that? No, that would not be the reason. To try and work around the problem and ensure that delivery still happens, I have set opt BOFHSUPPRESSBACKSCATTER=none in bofh, although I stil have ESMTP_BLOCKBACKSCATTER=smtp/dsn in courierd - is that 'safe' (i.e. it won't get my server blacklisted...) ? And will it switch off the 556 messages? That's how I read the manual, but I might be wrong... Cheers Pete -- Peter Ford, Developer phone: 01580 89 fax: 01580 893399 Justcroft International Ltd. www.justcroft.com Justcroft House, High Street, Staplehurst, Kent TN12 0AH United Kingdom Registered in England and Wales: 2297906 Registered office: Stag Gates House, 63/64 The Avenue, Southampton SO17 1XS -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users pgpSNTKAFAT1t.pgp Description: PGP signature -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Aliasing single user to another server
Bernd Wurst writes: Hi Sam. Am 2011-05-05 12:09 schrieb Sam Varshavchik: Use aliasdir, not the alias file. Tested it, it works as you described. Thanks a lot. Now, I have another, more special question: Is it possible to make courier look at the aliasdir even if the local user exists? For one user, I would like to have a shell login account on the server but local mail shall be forwarded to another server, including extension addresses. I have authpam running and I would like to keep that. If it does not work for this special case, this is not a real problem, I'm just curious if there is an easy way to fake courier that this user does not exist even if it does according to PAM. You can put the .courier files in the user's home directory. pgpspSAZwuvjJ.pgp Description: PGP signature -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Aliasing single user to another server
Bernd Wurst writes: Hi Sam. Am 2011-05-06 06:52 schrieb Sam Varshavchik: You can put the .courier files in the user's home directory. This is my manual workaround, yes. ;-) I have a script to maintain the courier domain and useraccount configurations that is running as mail user and I wondered if this one could handle it. So this script cannot automatically put files in user's homedirs for security reasons. But no matter, this special case can be done manually. Try putting symlinks in the home directory that point somewhere where your mail script can manage. pgpjQ5VDMEcaM.pgp Description: PGP signature -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Aliasing single user to another server
Bernd Wurst writes: Hi. I have sort of a special question. Many of our users use .courier-style-addresses, so that the user can have .courier-foobar to process username-foobar on our global domain. So this domain is in locals file. Now, one user has his homedir on another server. I tried to set up an alias: specialuser: specialuser@otherserver This works, but not for extension-addresses. Is there a way to forward all mail to local specialuser-* to specialuser-*@otherdomain? Use aliasdir, not the alias file. If a local mailbox does not exist and there's no alias, the last lookup is the aliasdir (man dot-courier), so install both .courier-special and .courier-specialuser-default in aliasdir to effect the forward. If you want to preserve the dash extension on the forwarded adderss, you'll have to monkey around in .courier-specialuser-default, something like: | sendmail -f $SENDER specialuser-$EXT@otherdomain pgpwLucS7nkMD.pgp Description: PGP signature -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] [PROBLEM] 500 Unable to set minimum security level.
Michelle Konzack writes: Can someone enlight me please, what this mean? [ '/var/log/mail.log' ]- May 1 20:50:26 michelle1 courierd: Loading STATIC transport module libraries. May 1 20:50:26 michelle1 courierd: Courier 0.60.0 Copyright 1999-2008 Double Precision, Inc. May 1 20:50:26 michelle1 courierd: Installing [0/0] May 1 20:50:26 michelle1 courierd: Installing uucp May 1 20:50:26 michelle1 courierd: Installed: module.uucp - Courier 0.60.0 Copyright 1999-2008 Double Precision, Inc. May 1 20:50:26 michelle1 courierd: Installing local May 1 20:50:26 michelle1 courierd: Installed: module.local - Courier 0.60.0 Copyright 1999-2008 Double Precision, Inc. May 1 20:50:26 michelle1 courierd: Installing fax May 1 20:50:26 michelle1 courierd: Installed: module.fax - Courier 0.60.0 Copyright 1999-2008 Double Precision, Inc. May 1 20:50:26 michelle1 courierd: Installing esmtp May 1 20:50:26 michelle1 courierd: Installed: module.esmtp - Courier 0.60.0 Copyright 1999-2008 Double Precision, Inc. May 1 20:50:26 michelle1 courierd: Installing dsn May 1 20:50:26 michelle1 courierd: Installed: module.dsn - Courier 0.60.0 Copyright 1999-2008 Double Precision, Inc. May 1 20:50:26 michelle1 courierd: Initializing uucp May 1 20:50:26 michelle1 courierd: Initializing local May 1 20:50:26 michelle1 courierd: Initializing fax May 1 20:50:26 michelle1 courierd: Initializing esmtp May 1 20:50:26 michelle1 courierd: Initializing dsn May 1 20:50:26 michelle1 courierd: Started ./courieruucp, pid=26203, maxdels=4, maxhost=4, maxrcpt=16 May 1 20:50:26 michelle1 courierd: Started ./courierlocal, pid=26213, maxdels=10, maxhost=4, maxrcpt=1 May 1 20:50:26 michelle1 courierd: Started ./courierfax, pid=26214, maxdels=1, maxhost=1, maxrcpt=1 May 1 20:50:26 michelle1 courierd: Started ./courieresmtp, pid=26220, maxdels=40, maxhost=4, maxrcpt=100 May 1 20:50:26 michelle1 courierd: Started ./courierdsn, pid=26221, maxdels=4, maxhost=1, maxrcpt=1 May 1 20:50:26 michelle1 courierd: queuelo=200, queuehi=400 May 1 20:50:26 michelle1 courierd: Purging /var/lib/courier/msgq May 1 20:50:26 michelle1 courierd: Purging /var/lib/courier/msgs May 1 20:50:26 michelle1 courierd: Waiting. shutdown time=Sun May 1 21:50:26 2011, wakeup time=Sun May 1 21:50:26 2011, queuedelivering=0, inprogress=0 May 1 20:50:54 michelle1 courierd: newmsg,id=000284DE.4DBDAB8E.669B: dns; localhost (localhost [127.0.0.1]) May 1 20:50:54 michelle1 courierd: started,id=000284DE.4DBDAB8E. 669B,from=linux4miche...@tamspamogan.net,module=esmtp,host=lists.so0rceforge.net,addr=courier- us...@lists.sourceforge.net May 1 20:50:54 michelle1 courierd: Waiting. shutdown time=none, wakeup time=none, queuedelivering=1, inprogress=1 May 1 20:50:54 michelle1 courieresmtp: id=000284DE.4DBDAB8E. 669B,from=linux4miche...@tamspamogan.net,addr=courier- us...@lists.sourceforge.net: 500 Unable to set minimum security level. May 1 20:50:54 michelle1 courieresmtp: id=000284DE.4DBDAB8E. 669B,from=linux4miche...@tamspamogan.net,addr=courier- us...@lists.sourceforge.net,status: failure May 1 20:50:54 michelle1 courierd: completed,id=000284DE.4DBDAB8E.669B May 1 20:50:54 michelle1 courierd: started,id=000284DE.4DBDAB8E. 669B,from=,module=dsn,host=,addr=linux4miche...@tamspamogan.net May 1 20:50:54 michelle1 courierd: Waiting. shutdown time=none, wakeup time=none, queuedelivering=1, inprogress=1 May 1 20:50:54 michelle1 courierd: completed,id=000284DE.4DBDAB8E.669B May 1 20:50:54 michelle1 courierd: newmsg,id=000284E8.4DBDAB8E.669F: dns; localhost (localhost [127.0.0.1]) May 1 20:50:54 michelle1 courierd: started,id=000284E8.4DBDAB8E. 669F,from=,module=esmtp,host=tamSPAMogan.net,addr=linux4miche...@t0mspamogan.net May 1 20:50:54 michelle1 courierd: Waiting. shutdown time=none, wakeup time=none, queuedelivering=1, inprogress=1 May 1 20:50:54 michelle1 courieresmtp: id=000284E8.4DBDAB8E. 669F,from=,addr=linux4miche...@tamspamogan.net: 500 Unable to set minimum security level. May 1 20:50:54 michelle1 courieresmtp: id=000284E8.4DBDAB8E. 669F,from=,addr=linux4miche...@tamspamogan.net,status: failure May 1 20:50:54 michelle1 courierd: completed,id=000284E8.4DBDAB8E.669F May 1 20:50:54 michelle1 courierd: started,id=000284E8.4DBDAB8E. 669F,from=,module=dsn,host=,addr=postmaster May 1 20:50:54 michelle1 courierd: Waiting. shutdown time=none, wakeup time=none, queuedelivering=1, inprogress=1 May 1 20:50:54 michelle1 courierd: completed,id=000284E8.4DBDAB8E.669F May 1 20:50:54 michelle1 courierd: newmsg,id=000284E6.4DBDAB8E.66A3: dns; localhost (localhost [127.0.0.1]) May 1 20:50:54 michelle1 courierd: started,id=000284E6.4DBDAB8E. 66A3,from=#@[],module=esmtp,host=tamSPAMogan.net,addr=michelle.kon0ack- sysmessa...@tamspamogan.net May 1 20:50:54 michelle1 courierd: Waiting. shutdown
Re: [courier-users] [PROBLEM] 500 Unable to set minimum security level.
Michelle Konzack writes: Hello Sam Varshavchik, Am 2011-05-01 15:37:54, hacktest Du folgendes herunter: You have a /SECURITY entry in esmtproutes for this host. Thanks, already seen, This is a Courier-specific feature that requires the destination mail server to present a certificate that's signed by a separate certificate authority. It's used, essentially, to set up a VPN-like SMTP channel over the Internet. See INSTALL. Does it not accept self-signed certificates? No. You need to create your own certificate authority, and sign the certificate using your certificate authority. In courierd, put your certificate authority's signing cert in the TLS_TRUSTSECURITYCERTS. When a hostname has /SECURITY=STARTTLS set in esmtproutes, that host must present a certificate that's signed by the authority given in TLS_TRUSTSECURITYCERTS which overrides, for that connection, the global TLS_TRUSTCERTS. Your global TLS_TRUSTCERTS can still point to your distribution's default list of globally trusted certificate authorities, to validate certificates signed by global authorities on the public Internet, and remains in effect for normal SMTP connections. /SECURITY=STARTTLS creates a different set of trusted authorities that you install and configure for your own private SMTP VPN. You use it to set up a secure SMTP link to another host on the Internet, using your own certificate authority, so even if someone compromises the connection on the network level, as long as your certificate authority isn't compromised, they won't be able to present a certificate that will be accepted by Courier for the SMTP connection to the destination host. Note that in the default configuration Courier does not validate regular TLS certificates, since self-signed SMTP certificates are common on the public Internet. You do not need /SECURITY=STARTTLS for your garden variety TLS- enabled server. /SECURITY=STARTTLS goes beyond that, and requires that the certificate be signed by your own certificate authority. pgpB7yC6IV33i.pgp Description: PGP signature -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] cone build fail
Justin Heesemann writes: Sam Varshavchik mrsam at courier-mta.com writes: Mark Constable writes: Not sure where else to report this, and it's only a FWIW. Archlinux x86_64 with gcc 4.6.0 In file included from cursesobject.C:9:0: ... Ok, added #include cstdio -- that should fix it. same problem with cone 0.88 and libmail/objectmonitor.H solution seems to be the same as well.. #include cstdio Ok, noted. pgpSdt8Fh255l.pgp Description: PGP signature -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] courierfilter - not removing lock file?
Bernd Plagge writes: Hi, I'm running courier version 0.65.0 on Debian. When I stopped courier-mta today I got a courierfilter Alarm message. When restarting courier-mta filters were not restarted. After some searching I found out that courierfilter stop didn't remove the /var/lib/courier/filters/.lock file. Is this a known problem or what might have caused it? An individual filter was stuck in a loop and refused to terminate upon request. You might have a process spinning somewhere. pgpOdHlh92VXc.pgp Description: PGP signature -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Read-only-IMAP / shared folders
Bernd Wurst writes: Hi. My customer asked for a setup where several IMAP accounts use the same mailbox and some have full access and some have read-only access to the mailbox. Is there a way to have this? Is it possible without setting up shared folders? No, that's the very definition of shared folders. pgpYA43KtZPvi.pgp Description: PGP signature -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] error message when couriertcpd reaches MAX* setting
Matus UHLAR - fantomas writes: Hello, when a SMTP client reaches maximum number of connections, I't like to send the temporary error prior to closing connection. It should be something like 421 Service not available, closing transmission channel would you find it useful to add parameter for couriertcpd to provide such info, or probably additional parameters to -maxperip,-maxperc,-maxprocs commands? there are some MTA's that flood our servers with too many parallel connections and I hope at least some would stop if rec eived error message instead of just connection closed... Unlikely. Furthermore, if you're really being flooded, then having to send an error message instead of just dropping the connection is going to generate even more bandwidth. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Read-only-IMAP / shared folders
Bernd Wurst writes: Hi Sam. Am Donnerstag, 14. April 2011, um 13:06:34 schrieb Sam Varshavchik: Is there a way to have this? Is it possible without setting up shared folders? No, that's the very definition of shared folders. It's a little difference if I only have some virtual accounts pointing to the same maildir or if I have to set up shared folder indexing and stuff... Is there a way to set up folders that are only shared with some users and not with everyone? Or is this done by denying access for anyone? This can be done with virtual shared folders and access control lists. The accounts must be different accounts, the server configured for shared folders, and the IMAP client must fully support IMAP public namespaces. If the IMAP client also fully supports IMAP ACLs, the owner of the account will have full control over who has access to which folders, directly from the IMAP client. Otherwise, the permissions will need to be adjusted manually using the maildiracl command. All of this will require some non-trivial amount of setup. Once it's set up, though, additional shared folders and accounts can be trivially added. pgpNICilYd69S.pgp Description: PGP signature -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Send several mails per connection
Jérôme Blion writes: Hello, I'm trying to help a customer. He owns a virtual card website. He sends several thousands mails per day. I already setup MAXDELS and MAXHOST, I modified the queue length too to be able to survive to any new year mail flood. I fixed Debian Lenny's libraries (dbm package bug) An ISP told my customer he should send all mails through one SMTP connection. I didn't find any parameter to do it. Are there some documents I should read? That ISP was probably explaining that all your customer's mail should be smarthosted through the ISP's mail server. In which case, theoretically, a single connection is all that's needed. But if all you're doing, for outbound mail, is using your ISP's smarthost, you don't really need a full- blown mail server, really. You should be using something else. But, aside from that, Courier creates separate connections for different domains, without considering esmtproutes. If the mail queue does contain multiple messages for the same domain, and they're scheduled to be delivered, Courier will reuse an existing connection to the recipient's domain, if it's available. But in any case, only a few thousand messages per day is no more than statistical background noise, and there shouldn't be any need to fine tune anything, even for peak volume that's in tens of thousand of messages per day. pgpEPNYvOQXQA.pgp Description: PGP signature -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Courier, sqwebmail, courier-imap releases
Download: http://www.courier-mta.org/download.php This releases of courier, courier-imap, and sqwebmail packages fixes several bugs. == Changes * Fix the script that generates self-signed SSL certs, for testing purposes, to set 0600 permissions on the PEM file. * Removed the call to the SSL2 driver module, which has been removed from recent OpenSSL builds. * Fixed memory corruption in sqwebmail. pgp9my5hKiqxg.pgp Description: PGP signature -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] relay must authenticate error 550
Karl Dahlke writes: Our local isp suddenly requires every smtp to authenticate. No warning, just suddenly 550 errors. I changed my client, no problem. Thus I am sending this mail out to you. But I can't figure out how to change courier, so at present, all the users that it supports can't send any mail out. I have set esmtpauthclient isp login password The isp matches the isp in esmtproutes, which has been working for ages. I tried setting AUTH_REQUIRED to 0 or 1 in esmtpd. Nothing works. Monitoring traffic shows courier begins with ehlo eklhad not helo eklhad so I thought it was on the right track. It gets back all the 250 messages, including 250-AUTH LOGIN PLAIN But then after 250 ok it jumps right into Mail From That indicates that the hostname in esmtpauthclient is not set correctly. Double check the contents of esmtpauthclient. pgpAfff2ldifm.pgp Description: PGP signature -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Courier GUI replacement for qmailadmin
Vini writes: Hi All, I have been using courier with vpopmail and qmailadmin for a while and although it all works well I would prefer to use some sort of GUI that is made for Courier. Is there any GUI that is available for Courier that could do a similar job to what qmailadmin does? I don't know what qmailadmin does, but Courier does include a web-based tool for setting up most configuration options. pgp954ImrUjq8.pgp Description: PGP signature -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Build failure with recent OpenSSL
Alessandro Vesely writes: On 11/Apr/11 08:48, Stefan Hornburg (Racke) wrote: Hello, apparently SSLv2 support has been removed from recent OpenSSL versions which cause Courier to fail building: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622014 Please suggest a solution. * Eliminate SSLv2 also from Courier, and/or * use GnuTLS. See RFC 6176 Prohibiting Secure Sockets Layer (SSL) Version 2.0 I'll remove the SSLv2 call. pgpxEsriLxTod.pgp Description: PGP signature -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] cone build fail
Mark Constable writes: Not sure where else to report this, and it's only a FWIW. Archlinux x86_64 with gcc 4.6.0 In file included from cursesobject.C:9:0: cursesobject.H: In constructor 'cursesPtrT::cursesPtr(T*)': cursesobject.H:37:29: error: 'NULL' was not declared in this scope cursesobject.H: In copy constructor 'cursesPtrT::cursesPtr(const cursesPtrT)': cursesobject.H:44:38: error: 'NULL' was not declared in this scope cursesobject.H: In member function 'cursesPtrT cursesPtrT::operator=(const cursesPtrT)': cursesobject.H:51:16: error: 'NULL' was not declared in this scope cursesobject.H: In member function 'void cursesPtrT::ptrDestroyed()': cursesobject.H:85:28: error: 'NULL' was not declared in this scope make[3]: *** [cursesobject.o] Error 1 make[3]: *** Waiting for unfinished jobs mv -f .deps/cursesscreen.Tpo .deps/cursesscreen.Po mv -f .deps/cursesstatusbar.Tpo .deps/cursesstatusbar.Po make[3]: Leaving directory `/home/tmp/yaourt-tmp-admin/aur- cone/src/cone-0.84/curses' Ok, added #include cstdio -- that should fix it. pgpbUEy76I6dO.pgp Description: PGP signature -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Courier (+subpackages), Cone released (fwd)
Download: http://www.courier-mta.org/download.php Major release of Courier packages and components, including Cone. Please review the following release notes. Side note: with this release, the source code repository migrated from CVS to subversion. = Major changes, affecting multiple packages * Unicode library replacement. * Implementation of the most recent plain text mail format specification, as per RFC 3676, using the format=flowed and delsp=yes option. * Search function added to '''sqwebmail'''. * Rewritten '''sqwebmail's''' parsing of HTML mail. == Unicode replacement The internal Unicode tables for a few dozen character sets were removed, and replaced by the system ''iconv(3)'' library, which on most platforms knows about a much larger universe of character sets in use. The new ''iconv(3)''-based API is completely different than the previous library API. The only remaining bits of code are mapping function that case- convert character data, as well as compute character width (there's no analogous functionality in ''iconv(3)''). This is augmented by new implementation of unicode grapheme-breaking, word-breaking and line- breaking algorithms. Translating and mapping between different character sets is core functionality; from converting email content, in '''sqwebmail''' and '''cone''', to client's character set, to parsing i18n data from various mail headers (which have several different character set and language encoding formats as well), to searching and sorting messages, by '''sqwebmail''', '''cone''', or the IMAP server. Most the impact from the rewrite should hopefully go unnoticed, aside from the larger character set universe known to '''sqwebmail''', '''cone''', and '''Courier-IMAP'''. As such, '''sqwebmail''' and '''cone''' can now process mail that's coded in any character set that's supported by the system ''iconv(3)'' library. This is true, of course, only if the browser or the terminal display supports UTF-8. Similarly '''Courier-IMAP''' now accepts search queries encoded in any character set known to ''iconv(3)''. = Backwards compatibility and upgrade notes * The format of the autoreplies has changed. Autoreply content must now use flowed-text markup. This affects '''mailbot''' and the equivalent autoreply feature in '''sqwebmail'''. Existing '''mailbot''' autoreply files need to be edited and reformatted as flowed text. Ditto for autoreplies set up in '''sqwebmail'''. They need to be opened, and edited so that the only linebreaks occur between paragraphs. Additionally, the autoreply text in '''sqwebmail''' is now saved in UTF-8; existing autoreplies may need to be transcoded manually. * The '''leaf''' editor, from the '''Cone''' package, can be used to conveniently reformat text files into flowed text format. See the leaf editor's man page for more information. * When using '''sqwebmail''' to generate HTML text, the markup for generating text headings has slightly changed. * Saved message signatures are now also saved in the UTF-8 character set, to get more consistent behavior when switching browser codings. Existing message signatures may have to be recoded. * Site-specific message footer files, in the html/LANG directory, must now be coded in UTF-8, and use the format=flowed, delsp=yes text format, as per RFC 3676. = Package-specific changes See changes specific to some of the packages, below. == Courier * Suppress logging the contents of a failed AUTH command in syslog, in case it includes encoded passwords. * Fix requirements of rpm spec files, to depend on /etc/cron.hourly, rather than a specific cron package. * Adjust indentation to avoid parts of DSNs unintentionally interpreted as quoted content. * Removed some message format compliance checks in Courier. Courier no longer complains about eight-bit content in mail headers. * Explicitly turn off IPV6_V6ONLY socket options. Some kernels have it turned on by default, which breaks IPv4/IPv6 interoperability. == IMAP * No externally-visible functionality changes, but as a result of the unicode library being replaced with ''iconv(3)'', the configure script options that select unicode character sets are moot, and have been removed. The IMAP server supports search string specified in any ''iconv(3)''- supported character set. == sqwebmail * Some changes to the default stylesheet. * Some changes to the wiki-HTML markup tags. * As a result of the unicode library being replaced with ''iconv(3)'', the configure script options that select unicode character sets are moot, and have been removed. The IMAP server supports search string specified in any ''iconv(3)''-supported character set. * Slight semantical difference in processing of signatures and footers. A signature, if present, no longer appears in the editable text area, but gets automatically added to the message, upon submission. The
Re: [courier-users] renaming Received-SPF: to Old-Received-SPF:
Matus UHLAR - fantomas writes: I'm fine with Received-SPF being renamed when mail is received from untrusted host. But for mail received from our (trusted) mail backups: - the SPF check will apparently fail (thus I better turn if off) - I could trust the SPF headers made by them, but they get renamed to Old- I think the SPF check done by courier doesn't care if the mail is received from mail backup of recipient's domain. (This could be problem for multiple recipients). Correct. A mail gets received from some IP address. The IP address does not get to wear a name badge that says I am trusted. The renaming of Received-SPF: only happens when SPF checking is used. If BOFHSPFHELO, BOFHSPFMAILFROM and BOFHSPFFROM are set to off, it should not get renamed. Therefore, if you enable SPF checking on all your incoming mail servers, and if they forward their mail to internal end-delivery hosts which are not configured to use SPF checking, then the Received-SPF: headers inserted by the receiving servers should rename intact. pgppTz7R370Po.pgp Description: PGP signature -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] renaming Received-SPF: to Old-Received-SPF:
Matus UHLAR - fantomas writes: Matus UHLAR - fantomas writes: can I prevent courier from renaming header Received-SPF: to Old-Received- SPF: for mail receiver from trusted sources, e.g. MX backups? Seems that turning SPF checks off does not do that. On 29.03.11 18:38, Sam Varshavchik wrote: No, there is no such option. This way spam filter will have to do SPF check for all mail delivered through backup MX servers, since we don't SPF check on them... BTW, what happens with Old-Received-SPF headers when they exist already? They're left alone. The goal here is to certify that any Received-SPF: headers in the mail were inserted by this host, and not somewhere else. Multiple Received-SPF: headers are allowed. If any existing headers do not get renamed, it would not be possible to reliably determine which ones are authentic. pgp6t6f2SrnLS.pgp Description: PGP signature -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] recalculating quota when maildirsize 5120 B
Matus UHLAR - fantomas writes: Hello, how was the static calue of 5120B for recalculating maildir quota chosen? I guess 4096 would be better, since then would the maildirsize file always fit into 4KB block which is quite common for many filesystems. Are any plans to change it or make it configurable? With this size, it means that the quota will be recalculated about once every two hundred mail deliveries. That seemed to be a reasonable heuristic. I don't see much benefit in making this adjustable. I do not see what's there to be gained from it. pgp8aBnTWcMiE.pgp Description: PGP signature -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] renaming Received-SPF: to Old-Received-SPF:
Matus UHLAR - fantomas writes: Helo, can I prevent courier from renaming header Received-SPF: to Old-Received-SPF: for mail receiver from trusted sources, e.g. MX backups? Seems that turning SPF checks off does not do that. No, there is no such option. -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] sqwebmail 20110326
Download: http://www.courier-mta.org/download.php#sqwebmail Development release of Courier and sqwebmail packages == Changes since the last 20110319 build * Rewritten parser for HTML mail. The new parser is more unicode-aware, and takes the approach of whitelisting HTML elements, rather than a blacklisting approach. Only known safe elements, that can be parsed, are shown. * The most readily visible change is that the target hostname of an HTML link is shown in smaller font before the link. This clearly identifies misleading links in junk mail. The entire link is also repeated in the _title_ attribute, which modern browsers show as a tooltip when the mouse hovers over the link. pgpPZ1KId4FlH.pgp Description: PGP signature -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] WEBMAILDSTART config option
Matus UHLAR - fantomas writes: Hello, shouldn't sqwebmaild config file have same option for starting webmaild as there are for esmtpd(-msa)/pop3d/imapd and their SSL versions? the init script checks for all of those if it should start them, but it starts webmail always... now I find it quite hard quite hard to install and start it without webmail daemon... It's expected that Courier gets installed as pre-built packages, and the webmail server is rolled into a separate subpackage that's optional to install. Therefore, whether or not the webmail server gets started is controlled by installing or uninstalling the webmail subpackage. -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] SNI with OpenSSL
Bernd Wurst writes: Hi. According to the distributed config file examples, Courier can handle hostname-based SSL certificate choosing only with GnuTLS. This technique (name SNI) was first supported by GnuTLS but in the mean time, OpenSSL also has this feature. I did a simple test with our courier (version 0.65.2) compiled with openSSL and it seems like it does not work (while IP-based certificate selection works). Would it be possible to add this feature also with OpenSSL? I'd have to look into how this gets implemented in OpenSSL. This requires specific coding to support it. pgpMy5RtuT3f4.pgp Description: PGP signature -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] [mlm] message looks like an administrative request
Michelle Konzack writes: Hello, since some weeks I get tonnst of errors on my mailinglists like the attached one. Note: I get per day 20-60 messages on that list and arround 1-5 have problems like this. How can I solv this? This error message is sent when the first word in the subject line of a message sent to the list posting address is subscribe, unsubscribe or help, and the mailing list has NOBOZOS=1 flag set. In webmlmd, this is the Try to detect and block misdirected administrative requests setting. pgpN00V8y8cmB.pgp Description: PGP signature -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] [mlm] message looks like an administrative request
Michelle Konzack writes: Hello Sam Varshavchik, Am 2011-03-22 19:51:21, hacktest Du folgendes herunter: This error message is sent when the first word in the subject line of a message sent to the list posting address is subscribe, unsubscribe or help, and the mailing list has NOBOZOS=1 flag set. Can not be, because the Subject line is: Subject: [mc-forum] Issue utilizing multiple timers OK, now I have set NOBOZOS=0 but I have checked the other messages and they do not contain subscribe, unsubscribe or help. Also check the first line of the message. pgpl0i0011Is8.pgp Description: PGP signature -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Problem the mailer-daemon templates
Bowie Bailey writes: On 3/17/2011 8:20 PM, Sam Varshavchik wrote: The only exception would be, perhaps, the aliases/system and the smtpaccess/default files. They get always installed afresh, so all your site settings should go into a different file; but that should be obvious. Are you sure about that? I have custom settings in both of those files and I have not seen them changed with any of the updates. Also, the install documentation on the website has instructions on customizing those files. Manually installing using 'make install', you're right. I was describing the behavior of my RPM packages. pgpodoO0f7RzT.pgp Description: PGP signature -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Problem the mailer-daemon templates
Michelle Konzack writes: Hello Sam and *, since I run Debian/Squeeze on my new mail.tamay-dogan.net I get strage messages where the templates are not correctly parsed and the %s not replaced. See attached message. Is there a possibility to solv this isssue? 8-- Date: Thu, 17 Mar 2011 19:39:28 +0100 Delivered-To: michelle.konzack-linux4miche...@tamaxxxogan.net From: mailer-dae...@mail.tamaxxxogan.net To: linux4miche...@tamaxxxogan.net Subject: NOTICE: mail delivery status. X-TDMailCount: true This is a delivery status notification from %s, running the Courier mail server, version 0.53.3. The original message was received on %s from %s You have stale template files installed from earlier versions of Courier, the /etc/courier/dsn*.txt files. This is how they should look in the current version: [mrsam@octopus module.dsn]$ cat /etc/courier/dsnheader.txt Content-Type: text/plain; charset=us-ascii This is a delivery status notification from [#ME#], running the Courier mail server, version 0.65.3.20110313. The original message was received on [#FROMTIME#] from [#FROMMTA#] pgpdIuKKVppjg.pgp Description: PGP signature -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Problem the mailer-daemon templates
Michelle Konzack writes: Hello Sam Varshavchik, Am 2011-03-17 19:06:36, hacktest Du folgendes herunter: You have stale template files installed from earlier versions of Courier, the /etc/courier/dsn*.txt files. This is how they should look in the current version: Right, I vave copied the old config from my server [mrsam@octopus module.dsn]$ cat /etc/courier/dsnheader.txt Content-Type: text/plain; charset=us-ascii This is a delivery status notification from [#ME#], running the Courier mail server, version 0.65.3.20110313. The original message was received on [#FROMTIME#] from [#FROMMTA#] Ufff I was thinking... You do not need to copy configuration settings from your previous install, unless it's an ancient version. With the current version of Courier, 'make install' does not install new configuration settings, but rather intelligently merges your existing configuration settings, with any configuration settings from the new version. If the existing configuration setting is no longer valid or compatible in the new version, the individual setting gets reset to the stock default; all other custom settings remain untouched. This works well as long as you don't butcher the magical comment markers in the configuration files, of course. Although I try to keep any new stuff backwards-compatible, where possible, I expect that a new version always executes 'make install'. The only exception would be, perhaps, the aliases/system and the smtpaccess/ default files. They get always installed afresh, so all your site settings should go into a different file; but that should be obvious. pgpXqYQe4XscI.pgp Description: PGP signature -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] DNS MX lookup failed.?
Mark Constable writes: On 16/02/11, Sam Varshavchik wrote: Received-SPF: error (DNS MX lookup failed.?) SPF=FROM; sender=po...@pobox.com; remoteip=:::64.74.157.115; remotehost=; helo=support.icgroup.com; receiver=mail.spiderweb.com.au; The above is courier 0.60.0 with this bofh... opt BOFHBADMIME=accept opt BOFHSPFHELO=pass,none,neutral,softfail,unknown,error opt BOFHSPFMAILFROM=pass,none,neutral,softfail,unknown,error opt BOFHSPFFROM=pass,none,neutral,softfail,unknown,error,mailfromok opt BOFHSPFTRUSTME=1 opt BOFHSUPPRESSBACKSCATTER=smtp,authsmtp I just sifted through the code. I believe that when a DNS lookup fails, the resulting status is error, and not softfail, so you really need the following patch. I think I can put together a test scenario in the next day or two -- set up a fake subdomain on one of my domain with an NS record pointing to a bogus IP address. That should reliably result in a DNS lookup error resolving the given domain. Stay tuned… diff -U3 -r1.74 submit.C --- courier/submit.C12 Oct 2010 00:27:55 - 1.74 +++ courier/submit.C16 Feb 2011 02:56:53 - @@ -887,7 +887,8 @@ return 1; } frominfo.receivedspfmailfrom=receivedspfmailfrom; - if (strcmp(result, pass) == 0) + if (strcmp(result, pass) == 0 || + strcmp(result, error) == 0) frominfo.mailfrom_passed_spf=1; } Sorry to bother you Sam but this problem is impacting even more clients than I thought and I'm stuck on older Debian systems which I can't upgrade until I physically get near the server. IOW I can't really test this myself. Any progress or workarounds until an official solution? The above code is the code that's currently in, and will be in the next release. pgpqIxkaGSw9P.pgp Description: PGP signature -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] DNS MX lookup failed.?
Mark Constable writes: On 15/03/11, Sam Varshavchik wrote: Any progress or workarounds until an official solution? The above code is the code that's currently in, and will be in the next release. Ah great, so I could patch 0.65.3 and be good or wait for 0.65.4. Dare I ask how long, rough estimate, before 0.65.4 will be released? Not sure. The major version will bump. There's been a ton of changes under the scene, dealing with mostly webmail, maildrop, and imap. They need a good shaking out. You can certainly patch this in. This is an almost a no-risk patch. pgpYt5ASscufF.pgp Description: PGP signature -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] maildirsize race condition and removal of the maildirsize file
Heiko Schlittermann writes: If I understood the exim implementation, it just removed and that's it. The quota for a later recreation comes from the configuration file. Having no quota for a limited frame of time would be no problem, but loosing the quota at all, definitivly is a problem. Since exim is the one that's removing the file, and exim is the one that's doing the delivery, then after removing the file the next delivery attempt will result in exim recalculate the quota, from scratch. There's nothing wrong with that approach. Ok, if I understand well, Courier always relies on an existing quota file and never ever will exit w/o creating a new one. But if no quota file is found, no quota will apply. The userdb option quota is not used at all, is it? It's there to be used. The standalone build of maildrop, if the courier- authlib hook is used, maildrop should end up retrieving the set quota from courier-authlib. The fallback is to use MAILDIRQUOTA from the environment. Courier itself will use the quota, whether it comes from userdb or from somewhere else. If Courier runs an external mail delivery agent, it sets MAILDIRQUOTA and leaves it up to the external mail delivery agent to use it. pgpAkIkkLQap2.pgp Description: PGP signature -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] maildirsize race condition and removal of the maildirsize file
Heiko Schlittermann writes: Courier itself will use the quota, whether it comes from userdb or from somewhere else. If Courier runs an external mail delivery agent, it sets MAILDIRQUOTA and leaves it up to the external mail delivery agent to use it. It looks as if the imapd/popd never gets passed the quota setting from the userdb. Seems to be the locical conclusion, if we suppose, that Courier will find the current active quota settings in the first line of the maildirsize file. That does look like the issue here. There is code in imapd that reads and uses MAILDIRQUOTA from the environment, if it's set, but there's nothing that explicitly sets it; it predates the current authentication architecture where this was done differently. But I do see that the quota data should be available to imaplogin. This should be fixable, I'll look into it. pgpGjNzq8u4eu.pgp Description: PGP signature -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] (fwd)
This is a development build of _courier_, _courier-imap_, _sqwebmail_, _maildrop_, and _cone_ packages. Download: http://www.courier-mta.org/download.php The custom implementation of unicode-based character set mapping tables has been replaced by an iconv(3)-based implementation. This release also includes a major upgrade to sqwebmail that includes better support for flowed-format text, and a new search function. == Backwards compatibility and upgrade notes * The format of the autoreplies has changed. Autoreply content must now use flowed-text markup. This affects mailbot and the equivalent autoreply feature in sqwebmail. Existing mailbot autoreply files need to be edit and reformatted as flowed text. Ditto for autoreplies set up in sqwebmail. They need to be opened, and edited so that the only linebreaks occur between paragraphs. Additionally, the autoreply text in sqwebmail is now saved in UTF-8; existing autoreplies may need to be transcoded manually. * When using sqwebmail to generate HTML text, the markup for generating text headings has slightly changed. * Saved message signatures are now also saved in the UTF-8 character set, to get more consistent behavior when switching browser codings. Existing message signatures may have to be recoded. * Site-specific message footer files, in the html/LANG directory, must now be coded in UTF-8, and use the format=flowed, delsp=yes text format, as per RFC 3676. * Slight semantical difference in processing of signatures and footers. A signature, if specified, will no longer appear in the editable text area, but get automatically added to the message, upon submission. The signature will also be shown when previewing the message. * A site-specific message footer file, if installed, will also be shown when previewing the message. == Other, general changes: * sqwebmail and Cone can now process mail coded in any character set that's supported by the system iconv(3) library, not just a few dozen character sets that used to be built into the codebase. This is true, of course, only if the browser or the terminal display supports UTF-8. Similarly Courier- IMAP now accepts search queries encoded in any character set known to iconv(3). * This is due to the replacement of the internal character set and unicode library, that predates the standardization of iconv(3). The new iconv(3)- based API is completely different than the previous library API. The only remaining bits of code are mapping function that case-convert character data, as well as compute character width (there's no analogous functionality in iconv(3)). This is augmented by new implementation of unicode grapheme breaking and line breaking algorithms. * Translating and mapping between different character sets is core functionality; from converting email content, in sqwebmail and Cone, to client's character set, to parsing i18n data from various mail headers (which have several different character set and language encoding formats as well), to searching and sorting messages, by sqwebmail, Cone, or the IMAP server. Most the impact from the rewrite should hopefully go unnoticed, aside from the larger character set universe known to sqwebmail, Cone, and Courier-IMAP. * There's a new search box at the bottom of the folder index page. sqwebmail searches the messages in the order of their appearance on the folder index screen. The search starts with the first message on the folder index screen. If the folder index screen does not start with the first message in the folder, the previous messages are not searched, and the search stops when enough messages with the search string are found to fill one folder index screen. In this manner, a poorly chosen search string that finds a hit in a lot of messages will limit itself. If necessary, the search can be repeated after navigating the folder index screen to the starting point for the second search. * Up to four occurrences of the search string in each message are shown on the search results page. * Word wrapping rules in sqwebmail now use unicode line break rules, rather than simple word wrapping on whitespace. This should improve sqwebmail's word wrap with non-Western languages. * Suppress logging the contents of a failed AUTH command in syslog, in case it includes encoded passwords. * Fix requirements of rpm spec files, to depend on /etc/cron.hourly, rather than a specific cron package. * Adjust indentation to avoid parts of DSNs unintentionally interpreted as quoted content. * mailbot now generates flowed text-formatted replies. -- pgpifw22R6efa.pgp Description: PGP signature -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future.
[courier-users] New development builds of Courier packages
This is a development build of _courier_, _courier-imap_, _sqwebmail_, _maildrop_, and _cone_ packages. Download: http://www.courier-mta.org/download.php The custom implementation of unicode-based character set mapping tables has been replaced by an iconv(3)-based implementation. This release also includes a major upgrade to sqwebmail that includes better support for flowed-format text, and a new search function. == Backwards compatibility and upgrade notes * The format of the autoreplies has changed. Autoreply content must now use flowed-text markup. This affects mailbot and the equivalent autoreply feature in sqwebmail. Existing mailbot autoreply files need to be edit and reformatted as flowed text. Ditto for autoreplies set up in sqwebmail. They need to be opened, and edited so that the only linebreaks occur between paragraphs. Additionally, the autoreply text in sqwebmail is now saved in UTF-8; existing autoreplies may need to be transcoded manually. * When using sqwebmail to generate HTML text, the markup for generating text headings has slightly changed. * Saved message signatures are now also saved in the UTF-8 character set, to get more consistent behavior when switching browser codings. Existing message signatures may have to be recoded. * Site-specific message footer files, in the html/LANG directory, must now be coded in UTF-8, and use the format=flowed, delsp=yes text format, as per RFC 3676. * Slight semantical difference in processing of signatures and footers. A signature, if specified, will no longer appear in the editable text area, but get automatically added to the message, upon submission. The signature will also be shown when previewing the message. * A site-specific message footer file, if installed, will also be shown when previewing the message. == Other, general changes: * sqwebmail and Cone can now process mail coded in any character set that's supported by the system iconv(3) library, not just a few dozen character sets that used to be built into the codebase. This is true, of course, only if the browser or the terminal display supports UTF-8. Similarly Courier- IMAP now accepts search queries encoded in any character set known to iconv(3). * This is due to the replacement of the internal character set and unicode library, that predates the standardization of iconv(3). The new iconv(3)- based API is completely different than the previous library API. The only remaining bits of code are mapping function that case-convert character data, as well as compute character width (there's no analogous functionality in iconv(3)). This is augmented by new implementation of unicode grapheme breaking and line breaking algorithms. * Translating and mapping between different character sets is core functionality; from converting email content, in sqwebmail and Cone, to client's character set, to parsing i18n data from various mail headers (which have several different character set and language encoding formats as well), to searching and sorting messages, by sqwebmail, Cone, or the IMAP server. Most the impact from the rewrite should hopefully go unnoticed, aside from the larger character set universe known to sqwebmail, Cone, and Courier-IMAP. * There's a new search box at the bottom of the folder index page. sqwebmail searches the messages in the order of their appearance on the folder index screen. The search starts with the first message on the folder index screen. If the folder index screen does not start with the first message in the folder, the previous messages are not searched, and the search stops when enough messages with the search string are found to fill one folder index screen. In this manner, a poorly chosen search string that finds a hit in a lot of messages will limit itself. If necessary, the search can be repeated after navigating the folder index screen to the starting point for the second search. * Up to four occurrences of the search string in each message are shown on the search results page. * Word wrapping rules in sqwebmail now use unicode line break rules, rather than simple word wrapping on whitespace. This should improve sqwebmail's word wrap with non-Western languages. * Suppress logging the contents of a failed AUTH command in syslog, in case it includes encoded passwords. * Fix requirements of rpm spec files, to depend on /etc/cron.hourly, rather than a specific cron package. * Adjust indentation to avoid parts of DSNs unintentionally interpreted as quoted content. * mailbot now generates flowed text-formatted replies. -- -- pgpQOadVSwgUm.pgp Description: PGP signature -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future.
Re: [courier-users] maildirsize race condition and removal of the maildirsize file
Heiko Schlittermann writes: Sam Varshavchik mr...@courier-mta.com (Sun Mar 13 20:34:33 2011): Heiko Schlittermann writes: Courier itself will use the quota, whether it comes from userdb or from somewhere else. If Courier runs an external mail delivery agent, it sets MAILDIRQUOTA and leaves it up to the external mail delivery agent to use it. It looks as if the imapd/popd never gets passed the quota setting from the userdb. Seems to be the locical conclusion, if we suppose, that Courier will find the current active quota settings in the first line of the maildirsize file. That does look like the issue here. There is code in imapd that reads and uses MAILDIRQUOTA from the environment, if it's set, but there's nothing that explicitly sets it; it predates the current authentication architecture where this was done differently. But I do see that the quota data should be available to imaplogin. This should be fixable, I'll look into it. I did it, but unfortunely restructred the source a bit… I was thinking along the same lines. However, there's some duplicated code here that, upon further review, needs to go into the courier-authlib package... -- pgp2YmspaEOoy.pgp Description: PGP signature -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] maildirsize race condition and removal of the maildirsize file
Heiko Schlittermann writes: Hello, the rules about calculating the maildirsize file contain a very last step: if there was a race condition (maildir changes during the recalculation), then return the calculated size, but remove remove the maildirsize file. Now I'm sitting in front of maildir/maildirquota.c around line 512. There the tmp maildirsize file gets renamed to maildirsize. Around line 550 the check for the race condition is done. But I do not see, how the newly created maildirsize file gets deleted. I'm I stupid or just blind? The key code path is maildir_quota_add_start(), the code path that modifies the existing quota. Note that when the aforementioned race condition gets detected, recalculation_needed is set to 1, and errno is set to EAGAIN. Note the outer loop in maildir_quota_add_start() that invokes maildir_checkquota again if errno is EAGAIN. Up to five times. If the race condition gets hit five times in a row, we just throw our hands up, and give up. On the next call to maildir_checkquota, because recalculation_needed is 1, we attempt to add everything up again, which writes out a new maildirsize file, and deletes the existing one. The maildirsize file does not actually get deleted. It cannot be physically deleted, because it defines the maildir's quota. Rather, it gets forcibly recalculated, and a new one gets written out and renamed again. pgpvJ4PovMzdb.pgp Description: PGP signature -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Compatible SASL authentication not available.
Michelle Konzack writes: Hi *, any computers in my intranet *.private.tamay-dogan.net must use the server mail.private.tamay-dogan.net to post messages and because the intranet is on a dynamic IP, I use currently vserver04.tamay-dogan.net as my relay, but now I get an error. I have cloned a mail server like my others, but this give me the error Compatible SASL authentication not available. [mrsam@octopus module.esmtp]$ telnet vserver04.tamay-dogan.net 25 Trying 217.147.94.23… Connected to vserver04.tamay-dogan.net. Escape character is '^]'. 220 This is vserver04.tamay-dogan.net EHLO mail.courier-mta.com 250-vserver04.tamay-dogan.net Ok. 250-STARTTLS 250-XVERP=Courier 250-XEXDATA 250-XSECURITY=NONE,STARTTLS 250-PIPELINING 250-8BITMIME 250-SIZE 250 DSN Authenticated SMTP is not enabled on this server, and it does not offer any SASL authentication mechanisms. It doesn't offer any authentication mechanisms. Check the ESMTPAUTH setting in the esmtpd config files. pgp5Aylmt54wK.pgp Description: PGP signature -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Strange behaviour with IPv4/IPv6 dual stack
Bernd Wurst writes: Hi Sam. It's ridiculous. I'm not a native english speaker, perhaps this is the reason that you are not willing to understand the key point. Am Mittwoch, 9. März 2011, um 00:12:49 schrieb Sam Varshavchik: Bernd Wurst writes: in this case, is blocked via greylisting by the recipient. With greylisting, a connection to the server gets successfully established, but, from the sender's perspective, the delivery attempt fails. Perfect. This is right for the FIRST ATTEMPT. Greylisting is only an example for any reason why the very first attempt fails. It is right for any attempt. Each delivery attempt is an independent event. The reasons for the delivery failures are irrelevant. To attempt to immediately try some other server to deliver the unwanted mail, is considered to be, at least rude, if not abusive. Rather, it is expected that the sender would wait, and try again later. That's a perfect strategy. But this second try is never ever done via IPv4 again. I see no evidence of that happening. There is nothing in the code that discriminates between IPv4 and IPv6 addresses. Any attempt to use another IP address, being IPv4 or IPv6, only occurs if there was a failure to establish a TCP connection. That is not true. When a network problem ocures with IPv6 (routing error), no TCP connection could be established. Courier just gives up and does not try IPv4. That's what I'm trying to say. I see no evidence of that. Once the list of IP addresses for a domain is obtained, the connection attemps are made in a compleletely agnostic manner. There is no difference in treatment between IPv4 and IPv6 addresses. First try CAN establish a TCP connection and then is blocked by greylisting. All further tries run into a timeout because IPv6 is broken. There is no further try on the IPv4 address. I don't know what to tell you. Each delivery attempt, five minutes apart, is executed by a completely different process, that has no knowledge of what happened in some unrelated process, five minutes earlier. A courieresmtp client persists for no longer than a minute, in order to recycle connections. Each delivery attempt you logged was from a different process, each. pgpRILVoS5AkQ.pgp Description: PGP signature -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Strange behaviour with IPv4/IPv6 dual stack
Bernd Wurst writes: Okay. Which component cares about connecting to the secondary MX (or any other available IP address) when TCP connection to the primary fails? As I understood, the connection to the secondary MX should take place immediately after the second try on the first MX fails on TCP layer. But only one connection failure is logged. Looking at the code, only the last connection failure gets logged. If the first IP address tried fails, but Courier connects to the next IP, the connections goes through, and nothing gets logged (and nobody would care, I think). We have 0.65.2 on our production system. When I read the changelog, I stumbled upon the following changelog-entry: 2011-01-22 Gordon Messmer yiny...@eburg.com * rfc1035/rfc1035mksocket.c (rfc1035_mksocket): Set IPV6_V6ONLY socket option to OFF for IPv6 sockets, if the system default is on. Could it be that this fixes my issues? Is this change included in 0.65.3? No, it's not. If you're affected by this, you would not be able to establish IPv4 connections at all, ever. This change undoes a default setting in some kernel configurations that prevents IPv6 sockets from connecting to IPv4 addresses. On systems with IPv6 support, Courier always creates IPv6 sockets, and expects to be able to connect to IPv4 IP addresses, as part of the IPv6 specification. This works under the default kernel configuration, but for some reason Debian's kernel is configured with this switched of by default, and this change explicitly enables IPV6←→4 interoperability. pgppbtdaPGanY.pgp Description: PGP signature -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] defaultdomain
Matus UHLAR - fantomas writes: Matus UHLAR - fantomas writes: So, as I understand it, the defaultdomain gets appended to all addresses without domain name in headers and envelope, and the mail is handles as if it was sent from/to those addresses. If those addresses are not local, courier will deliver them using standard way (e.g. using smtp). And replies back to those addresses would go Is my understanding correct? On 02.03.11 21:02, Sam Varshavchik wrote: Pretty much. Of course, this is subject to what Courier would normally do when given the recipient address (which depends on whether the sending has relaying privileges). So, it should make no real problems, but clients could only use unqualified addresses if they have relaying privileges, OR if the defaultdomain is in exptpacceptmailfor. Yes. If you know what you're doing, this'll work for you. But, it's better to keep things less complicated, and just say Don't do it. Giving such an explanation to someone who's not very familiar with this, is going to make their head spin. Warning If you change the contents of this configuration file, you must run the makealiases command again, else your mail will promptly begin to bounce. If you don´t have this configuration file defined, and you change the system´s network host name, you also must run makealiases. Actually it's both, since if defaultdomain does not exist, me gets used. And if they differ, which one applies? defaultdomain. Again, I think that this is one of those situations where the Doctor, it hurts when I do this. Well, don't do it, then. principle applies. pgpX7cKaso2Ax.pgp Description: PGP signature -- What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Add IP detail to authdaemond logging
Mark Constable writes: It would hugely help trying to match up who is logging in if the IP appeared on this line... Mar 2 14:07:22 mail authdaemond: received auth request, service=esmtp, authtype=login for example... Mar 2 14:07:22 mail authdaemond: received auth request from 12.34.56.78, service=esmtp, authtype=login This is logged by authdaemond. This requires a non-trivial amount of work, since authdaemond knows little about who's on the other end of the local socket. The protocol with the authdaemon client needs to change so that authdaemon can pass its environment variables to authdaemond. pgpNhMZ3u4OX6.pgp Description: PGP signature -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Error generating ip address
Vytautas Kasparavicius writes: Hello, How to investigate which ip address generated folowing error: Mar 2 15:48:37 mail imapd-ssl: couriertls: accept: error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate unknown You'll need to look for a preceding Connection entry. On a busy server there may be several, so it's not always possible to determine the guilty party. pgpxXbOV9VQIB.pgp Description: PGP signature -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] defaultdomain
Matus UHLAR - fantomas writes: So, as I understand it, the defaultdomain gets appended to all addresses without domain name in headers and envelope, and the mail is handles as if it was sent from/to those addresses. If those addresses are not local, courier will deliver them using standard way (e.g. using smtp). And replies back to those addresses would go Is my understanding correct? Pretty much. Of course, this is subject to what Courier would normally do when given the recipient address (which depends on whether the sending has relaying privileges). Similarly, defaultdomain is used in addresses that are specified in the aliases file, if they do not specify a domain. So, if the recipient address is domain-less, defaultdomain gets added, and the correct alias is found. If the address is one of the addressed being aliased to, Courier will then try to deliver mail to that domain via smtp. the 'me' documentation in courier(8) man page indicates that it's the 'me' what is used for addresses without domains in aliases (maybe by makealiases command?): Warning If you change the contents of this configuration file, you must run the makealiases command again, else your mail will promptly begin to bounce. If you don´t have this configuration file defined, and you change the system´s network host name, you also must run makealiases. Actually it's both, since if defaultdomain does not exist, me gets used. pgpbhaCYjFJSc.pgp Description: PGP signature -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] defaultdomain
Matus UHLAR - fantomas writes: Hello, does the name in defaultdomain really NEED to be in locals/hosteddomains, as mentioned in courierd man page? We have MX backups who should forward all mail (even locally generated) to mailhubs where it would be processed and delivered. I'm thinking that even things like aliases should be expanded as those mailhubs. (One thing I'd like to achieve is to have hostname at those servers, so nobody would accidentally send mail directly to to them from outside) Is there any problem with such setup I don't see? Can it generate duplicate message-ids? defaultdomain gets appended to addresses in mail headers that do not specify a FQDN. If defaultdomain is not in locals, then if someone replies to such an address Courier will not recognize the domain as a local domain, and, by default, reject it unless other arrangements are made for that domain. Similarly, defaultdomain is used in addresses that are specified in the aliases file, if they do not specify a domain. So, if the recipient address is domain-less, defaultdomain gets added, and the correct alias is found. If the address is one of the addressed being aliased to, Courier will then try to deliver mail to that domain via smtp. So, if you do not list defaultdomain in locals (or hosteddomains), the world is not going to come to an end, you just have to understand what happens if someone would attempt to send mail to the resulting address, and if that would be the right thing to do. pgpGh37OFoH6Z.pgp Description: PGP signature -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] BOFHCHECKHELO and subnet-based smtpaccess entries
Greg Earle writes: On Feb 17, 2011, at 4:13 PM, Sam Varshavchik mr...@courier-mta.com wrote: Greg Earle writes: syslog:Feb 16 16:15:20 isolar courieresmtpd: [ID 702911 mail.error] error,relay=:::98.138.91.23,from=tsarmstron...@att.net: 517 HELO nm8-vm0.bullet.mail.ne1.yahoo.com does not exist. I don't really understand why, because sometimes they get through just fine: That suggests flaky DNS. Not necessarily your DNS, but Yahoo's DNS. The only thing that can be done, in those cases, is to also whitelist the sending IPs. Agreed - but isn't isolar:1:65 [/opt/courier/etc/smtpaccess] # grep 98.138.91 default 98.138.91 allow,RELAYCLIENT,BOFHCHECKDNS=0,BOFHCHECKHELO=0 whitelist[ing] the sending IPs? Ok, but did you run makesmtpaccess? Check the timestamp on smtpaccess.dat pgpHMLO64SKLH.pgp Description: PGP signature -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] How to track failed authentication attempts?
Lorenzo Perone writes: assumed cause. I'm now monitoring the mailq size via zabbix (as simple as mailq | wc -l ) and triggering alarms when it keeps growing too quickly. Do you think mailq output is a reliable indicator, or should Yes, it's reliable. we resort to maillog analysis for this, too? One reason why I ask is that I vaguely remember messages stuck in the mailq for months, allthough I haven't seen such ones in a while. No, that shouldn't happen. All messages should have the same maximum expiration time. pgpkFuDH7DcyG.pgp Description: PGP signature -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] How to track failed authentication attempts?
Lorenzo Perone writes: Hi List, Hi Sam, I was wondering whether there is some way in Courier (using authlib, using authmysql) to catch the event of a multiple login failure, such as in the case of spambots trying to bruteforce an account, to temporarily ban the IP? Just had a look at the docs but couldn't find anything... is there any way to implement it? Just have to have something parsing mail logs, which will record the client's IP address, and a very distinctive error message. But, I don't believe that spambots are really that much of an issue here. The built-in error delay makes spambots give up rather quickly. pgpwWGGqtYiJn.pgp Description: PGP signature -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Courier 0.65.3 released
Download: http://www.courier-mta.org/download.php This release adds a patch to the stable code that flushes an internal input buffer when the SMTP server receives a STARTTLS command from a sending client. Changes: • Although TLS is effective against the general kind of man-in-the-middle attacks, depending on the SMTP client's behavior an attacker could've still modified the message's sender address and recipients (but not access the envelope or the message body that's sent after TLS is enabled, nor modify it). Note that a party that's capable of hijacking a TLS connection can always filter out the server's STARTTLS capability, preventing STARTTLS, and, it's basically game over. Still, this patch is needed in uncommon, custom configurations where where the sender requires STARTTLS, or which uses client certificate authentication. pgpPwaYgStDlB.pgp Description: PGP signature -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Courier 0.65.3 released
Mark Constable writes: On 14/02/11, Sam Varshavchik wrote: Download: http://www.courier-mta.org/download.php This release adds a patch to the stable code that flushes an internal input buffer when the SMTP server receives a STARTTLS command from a sending client. Great but what about this one?... A transient DNS lookup failure results in an SPF softfail result, rather. I think this is probably wrong; mailfromok should be accepted if the SPF lookup resulted in softfail, as well... So courier is at fault in this particular corner case? Yes. The corner needs to be rounded a bit. I have the fix for this one ready, just need to figure out how to simulate a workable test scenario. pgpABHBNYf3MA.pgp Description: PGP signature -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Checking SPF source
Mark Constable writes:
On 09/02/11, Sam Varshavchik wrote:
The only thing I can think of would be a transient DNS lookup
failure for pobox.com. mailfromok is accepted only if the SPF
lookup on the MAIL FROM resulted in pass.
That may be possible because I'm in AU and a lookup I just did
now from the same mailserver was...
~ dig txt pobox.com
;; Query time: 245 msec
whereas the next attempt was 14 msec. This TXT record is rather
intense so I could well imagine DNS timing out trying to look
for a match through all of this gunk...
~ dig +short txt pobox.com
v=spf1 mx mx:fallback-relay.%{d} a:webmail.%{d} a:smtp.%{d}
a:outgoing.smtp.%{d} a:discard-reports.%{d} a:discards.%{d}
A transient DNS lookup failure results in an SPF softfail
result, rather. I think this is probably wrong; mailfromok
should be accepted if the SPF lookup resulted in softfail,
as well...
So courier is at fault in this particular corner case?
Yes. The corner needs to be rounded a bit.
pgpQuKNpxolw1.pgp
Description: PGP signature
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Moving mails between shared folders
Jan Strube writes: Hello, I have created a shareable folder collection containing two shared folders A and B. When I try to move a mail from folder A to B using Thunderbird, other users see the mail in both folders. On the server the mail file exists in both folders. In my own mail directories shared-folders folder there is a link to the mail in folder A with the T flag and a link to the mail in folder B without the T flag. This seems to be correct. But the other users have both links without the T flag. After a while the obsolete links and the old mail file in folder A are deleted. Sometimes this takes only seconds and sometimes hours. Is it predictable when this cleanup happens or is there an option to speed it up? This is determined by your IMAP client. Your IMAP client sends an IMAP EXPUNGE command that removes messages that have been marked as deleted. Check the documentation of your IMAP client. pgpl33Z85bSLp.pgp Description: PGP signature -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Checking SPF source
Mark Constable writes:
I've got this SPF rejection and I'm still confused as to exactly what
gets trigerred. Obviously the message is rejected before I get to see
any headers that would give me a better clue. The envelope sender domain
SPF does include this IP 64.74.157.52 but the From: domain does not so
I think my question is, that with my bofh SPF rules, how come
BOFHSPFMAILFROM didn't give me a pass?
Feb 9 07:47:38 mail courieresmtpd: error,relay=:::64.74.157.52,
from=SRS0=MnWw=VF=morningstar.com=help...@bounce2.pobox.com:
517 SPF fail help...@morningstar.com: Address does not pass the Sender Policy
Framework
courier-mta 0.60.0
opt BOFHSPFHELO=pass,none,neutral,softfail,unknown,error
opt BOFHSPFMAILFROM=pass,none,neutral,softfail,unknown,error
opt BOFHSPFFROM=pass,none,neutral,softfail,unknown,error,mailfromok
opt BOFHSPFTRUSTME=1
First the From: domain...
~ dig +short txt morningstar.com
v=spf1 a:spfmailer.morningstar.com -all
~ dig +short a spfmailer.morningstar.com
66.35.231.16
66.35.231.15
216.228.234.30
216.228.233.9
216.228.233.10
216.228.228.165
216.228.228.164
216.228.228.163
216.228.228.162
216.228.228.161
216.228.228.160
216.228.224.50
216.228.224.34
216.228.224.33
216.228.224.32
210.193.131.12
12.43.226.3
66.35.231.18
66.35.231.17
No 64.74.157.52 above. Then the sender envelope domain...
~ dig +short txt bounce2.pobox.com
v=spf1 redirect=pobox.com
I presume the above means to now look at the TXT record for pobox.com
~ dig +short txt pobox.com
v=spf1 mx mx:fallback-relay.%{d} a:webmail.%{d} a:smtp.%{d} a:outgoing.smtp.%{d}
a:discard-reports.%{d} a:discards.%{d}
~ dig +short mx pobox.com
10 mx-3.pobox.com.
10 mx-2.pobox.com.
10 mx-6.pobox.com.
10 mx-1.pobox.com.
10 mx-4.pobox.com.
10 mx-5.pobox.com.
10 mx-7.pobox.com.
10 mx-all.pobox.com.
And we have a winner!...
~ dig +short a mx-4.pobox.com
64.74.157.52
64.74.157.52
64.74.157.52
64.74.157.52
64.74.157.52
64.74.157.52
64.74.157.52
64.74.157.52
The only thing I can think of would be a transient DNS lookup failure for
pobox.com. mailfromok is accepted only if the SPF lookup on the MAIL FROM
resulted in pass.
A transient DNS lookup failure results in an SPF softfail result, rather. I
think this is probably wrong; mailfromok should be accepted if the SPF
lookup resulted in softfail, as well…
pgp9i5D6WX3Qi.pgp
Description: PGP signature
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] SPF rejection from forwarded message
Mark Constable writes: On 05/02/11, Sam Varshavchik wrote: I send a test message to yy...@z.com which we know is forwarded to yy...@.com.au which causes a 517 fail on z.com for anyone sending to this user from a domain with an SPF record. Forwarding breaks SPF, film at 11. The only thing they can do is set the envelope sender on forwarded mail to point to their own domain, with its own SPF record. Thanks Sam. So in trying to get some rewritting to work on my courier server, before I google for a postfix solution, first I try this... ~ cat .courier-markc2 !$SENDMAIL -verp t...@.com.au and that seemed to work but I can't see any difference in the destination That'll only work if you really used a | instead of a !. headers compared to a plain t...@.com.au in .courier-markc2, Next... There wouldn't be any difference in the headers. The difference is in the envelope return address. ~ cat .courier-markc2 !$SENDMAIL -f mconsta...@gmail.com t...@.com.au which is just weird. I see there are -bs and a -V options which could be of interest but perhaps a hint as to which one would suit rewritting the envelope From via a .courier file? -f is sufficient. That's the option that sets the envelope return address. Now, don't put the forwarding address itself in -f. If there's a bounce, and the bounce goes here, it gets forwarded, which bounces again. This'll result in a temporary mail loop. -bs results in $SENDMAIL talking SMTP on standard input, which is not very useful in a context of a .courier file. -V sets an optional ESMTP parameter, and aside from that carries no useful purpose. Put an address for -f that simply discards all mail. If the forwarded mail bounces, the bounce will quietly disappear. That's the price to pay for forwarding: if you forward something, there's an expectation that you're forwarding somewhere that actually accepts mail. pgpwifAUMW5B8.pgp Description: PGP signature -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] SPF rejection from forwarded message
Mark Constable writes: On 05/02/11, Mark Constable wrote: The only thing they can do is set the envelope sender on forwarded mail to point to their own domain, with its own SPF record. perhaps a hint as to which one would suit rewritting the envelope From via a .courier file? To answer my own question, this seems to work (Debian)... ~ cat .courier-markc2 |/usr/sbin/sendmail -verp t...@.com.au However, another question, the Return-Path seems to differ from the sender= so which one is the real envelope From as seen by .com.au? Return-Path: is the traditional header where the envelope sender address is saved, when a message is delivered to a mailbox. Delivered-To: t...@.com.au Return-Path: alias-tech=.com...@renta.net You don't really want that. Just use -f. -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] SPF rejection from forwarded message
Mark Constable writes: I send a test message to yy...@z.com which we know is forwarded to yy...@.com.au which causes a 517 fail on z.com for anyone sending to this user from a domain with an SPF record. What can I advise the z.com folks on how to to alter their forwarding system so it doesn't trip this SPF filter at .com.au? Forwarding breaks SPF, film at 11. The only thing they can do is set the envelope sender on forwarded mail to point to their own domain, with its own SPF record. opt BOFHSPFHELO=pass,none,neutral,softfail,unknown,error opt BOFHSPFMAILFROM=pass,none,neutral,softfail,unknown,error opt BOFHSPFFROM=pass,none,neutral,softfail,unknown,error,mailfromok opt BOFHSPFTRUSTME=1 The forwarder's SPF settings have absolutely nothing to do with anything. The forwarded destination's SPF settings are the ones that determine whether or not the destination rejects the mail. pgp1Gao4xvURX.pgp Description: PGP signature -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Weird problem with rejection (511)
Michelle Konzack writes: Hello *, can someone review the attached message an can tell me, WHERE the error is? I have a script which injects modified RSS-Messages into mailing- The error is somewhere in the script that submits a message to Courier's sendmail which does not appear to contain anything that looks like a To:, Cc: or a Bcc: header. As such, sendmail cannot determine to which recipients the message should be mailed to, and thus reports the following error: Your message to the following recipients cannot be delivered: mcforum-ssp-iic-...@lists.electronica.tamay-dogan.net: 511 Headers specify no receipients. sendmail: Unable to submit message. pgp0ocDLOfqHV.pgp Description: PGP signature -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Weird problem with rejection (511)
Michelle Konzack writes: Additional info to a new error message: [ command 'grep 00024145.4D473C20 /var/log/mail.log' ]-- Jan 31 23:48:00 vserver04 courierd: newmsg,id=00024145.4D473C20.19C8: dns; localhost (localhost [127.0.0.1]) Jan 31 23:48:00 vserver04 courierd: started,id=00024145.4D473C20.19C8,from=catchall-electronica@vserver04 .tamay-dogan.net,module=local,host=catchall-electronica-lists!mcforum-ssp -iic-spi!1015!1015!/home/catchall-electronica-lists!!,addr=catchall-elect ronica-lists Jan 31 23:48:00 vserver04 courierlocal: id=00024145.4D473C20.19C8,from=catchall-electron...@vserver04.tamay-dogan.net,addr=catchall-electronica-lists-mcforum-ssp-iic-...@vserver04.tamay-dogan.net: 511 Headers specify no receipients. Jan 31 23:48:00 vserver04 courierlocal: id=00024145.4D473C20.19C8,from=catchall-electron...@vserver04.tamay-dogan.net,addr=catchall-electronica-lists-mcforum-ssp-iic-...@vserver04.tamay-dogan.net: sendmail: Unable to submit message. Jan 31 23:48:00 vserver04 courierlocal: id=00024145.4D473C20.19C8,from=catchall-electron...@vserver04.tamay-dogan.net,addr=catchall-electronica-lists-mcforum-ssp-iic-...@vserver04.tamay-dogan.net,status: failure Jan 31 23:48:00 vserver04 courierd: completed,id=00024145.4D473C20.19C8 Jan 31 23:48:00 vserver04 courierd: started,id=00024145.4D473C20.19C8,from=,module=dsn,host=,addr=catchall-electron...@vserver04.tamay-dogan.net Jan 31 23:48:00 vserver04 courierd: completed,id=00024145.4D473C20.19C8 I have even tried to send the message manualy using sendmail -t but it is the same error. The weird thing is, I am preparing messages from BaSH scripts since more then 10 years and send it with sendmail -t but I do not understand WHY this message wont send. I have the error only on the four mailinglists mcforum-digital-io-ports mcforum-general-pic32-topics mcforum-sci-usart-eusart mcforum-ssp-iic-spi and all others are working fine and I already receive messages. Hmmm... Sam Can it be, that courier does not like the three - in the listnames? Depending on how the mailing lists actually get set up. Addresses with dashes are inherently ambiguous. There's nothing wrong with local account names containing dashes. user-foo-bar may be delivered to either an account named user or user-foo, if either account has the matching .courier file. Courier looks for an account named user-foo-bar, then user-foo, then user, until it finds it, then checks for a proper .courier file, in each case. To prevent an attacker sending an address of the form 'a-b-c-d-e-f-g-h-i…' and causing a plethora of calls against the authentication database, and overloading it. Courier ignorees any dashes after the first three. pgpboklbDw2JQ.pgp Description: PGP signature -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] MLM goes crazy
Michelle Konzack writes: Hello Sam Varshavchik, Am 2011-01-29 21:41:10, hacktest Du folgendes herunter: 556 is backscatter suppression kicking in. How can this be? This mailinglist has never received or send messages because it is currently only installed but inactive. Let's say you've set up the .courier files for this mailing list, but had a typo and your first test message bounced. Courier puts the recipient address into the penalty box, for 1-2 hours. Even if you fix the typo, the address is temporarily blacklisted, and Courier rejects this recipient address until it's out of the penalty box, or you manually void it with courier clear. pgpsyqVT9SI0M.pgp Description: PGP signature -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] MLM goes crazy
Michelle Konzack writes: Hello * I have several 100 Mailinglists and yesterday created 20 new ones, but now I get problems with the subscribtion for two new lists, because it tell me 556 Address unavailable. which can not be because I have send the subscribtion and confirmed it and now it is gone? Any enlightment? 556 is backscatter suppression kicking in. pgpWfgiWJRljV.pgp Description: PGP signature -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Strange behaviour with IPv4/IPv6 dual stack
Bernd Wurst writes: Hi. Tonight, I noticed a strange beaviour with courier MTA on IPv6 enabled destinations. I misconfigured courier with a SOURCE_ADDRESS_IPV6 that accidentially was not configured on the interface, so it was not available. When sending to a peer that has both, IPv4 and IPv6 addresses and greylisting enabled, I got the following history of failures (shortened the lines for readablity): Jan 24 21:24:59 zucker courieresmtp: 451-178.63.68.96 is not yet authorized to deliver mail from Jan 24 21:24:59 zucker courieresmtp: 451 Please try later. Jan 24 21:24:59 zucker courieresmtp,status: deferred Jan 24 21:29:59 zucker courieresmtp: Cannot assign requested address Jan 24 21:29:59 zucker courieresmtp,status: deferred Jan 24 21:34:59 zucker courieresmtp: Cannot assign requested address Jan 24 21:34:59 zucker courieresmtp,status: deferred Jan 24 21:50:14 zucker courieresmtp: Cannot assign requested address Jan 24 21:50:14 zucker courieresmtp,status: deferred [...] When I fixed the IPv6-misconfiguration and after issuing courier flush [msgid], I get a line like this: Jan 25 09:35:40 zucker courieresmtp: 451-178.63.68.96 is not yet authorized to deliver mail from Jan 25 09:35:40 zucker courieresmtp: 451 Please try later. Jan 25 09:35:40 zucker courieresmtp,status: deferred So it seems like Courier prefers IPv4 over IPv6 only ONE TIME and then, on retries, only uses IPv6 without fallback to IPv4. On manual queue flushes, only IPv4 is used, no IPv6. No. Courier carries over no preference on delivery attempts. What is, probably, happening is that Courier keeps the connection open after a delivery attempt, for two minutes by default. If a message to the same domain gets sent, it gets sent using the existing, open connection. Changing SOURCE_ADDRESS_IPV6 requires a restart, which will kill all active connection. pgpB5VGQf2jNP.pgp Description: PGP signature -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Strange behaviour with IPv4/IPv6 dual stack
Bernd Wurst writes: Changing SOURCE_ADDRESS_IPV6 requires a restart, which will kill all active connection. I did not change and restart but set the specified address on the interface. Does not matter. Until Courier gets restarted, it's as if no changes have been made to the configuration files. These specific settings get loaded only when Courier is started/restarted. pgp8B1WT4182m.pgp Description: PGP signature -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] webmail
pascal writes: hi! i have installed the courier-0.65.2.20110103 but I have some trouble whith the webmail I obtain the login page in cgi-bin/webmail but when i press the button login i obtain a : The requested URL /cgi-bin/webmail was not found on this server. i don't understand why if the url is the same one, then the first time the apache finds the cgi before the login, but not for the response! any help would be appreciated Check your Apache configuration. webmail relies on the web server properly initializing the CGI environment. If your web server's hostname is http://x.example.com, but Apache is configured so that it thinks its name is y.example.com, all the links will be pointing to http://y.example.com pgpEJfGSm9fpr.pgp Description: PGP signature -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] IPV6 and Debian testing
Alessandro Vesely writes: On 21/Jan/11 12:58, Sam Varshavchik wrote: Gordon Messmer writes: If Courier specifically sets IPV6_V6ONLY to int 0, it should override Debian's behavior and allow the application to function normally: int on = 0; if (setsockopt(s, IPPROTO_IPV6, IPV6_V6ONLY, (char *)on, sizeof(on)) == -1) perror(setsockopt IPV6_V6ONLY); Splendid. We have our solution. I'm in the middle of pulling all the innards out, and hopefully putting them back, sometime soon, but this is going to be the next thing on the chopping block. Will that have a chance to make it in squeeze before it rolls out? (When is that due?) Yes, I put this in. Just finished everything - it's a major rewrite of all unicode conversion code, which predated iconv(). All the custom unicode code and character sets, are gone and replaced by iconv, except for the upper/lower/titlecase conversion tables, and character width tables. iconv() has no equivalent functionality. Not sure what the schedule is. I'll have some tarballs shortly, but there are more changes here than happened in quite a few years, so for a little while it's better to proceed cautiously. A lot of stuff can potentially break. Hopefully not, we'll see… pgpjFuXyjWf8H.pgp Description: PGP signature -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Build 20110122 of courier, courier-imap, sqwebmail, maildrop, cone packages
Download: http://www.courier-mta.org/download.php The custom implementation of unicode-based character set mapping tables has been replaced by an iconv(3)-based implementation. Changes since the previous build. • sqwebmail and Cone can now process mail coded in any character set that's supported by the system iconv(3) library, not just a few dozen character sets that used to be built into the codebase. This is true, of course, only if the browser or the terminal display supports UTF-8. Similarly Courier-IMAP now accepts search queries encoded in any character set known to iconv(3). • This is the result of a large scale replacement of the internal character set and unicode library, whose roots predate the standardization of iconv(3) has been rewritten and replaced. The new iconv(3)-based API is completely different than the previous library API. The only remaining remnants are a few bits that case-convert character data, as well as compute character width (there's no analogous functionality in iconv(3)). • Translating and mapping between different character sets is well entrenched into all parts of the system; from converting email content, in sqwebmail and Cone, to client's character set, to parsing i18n data from various mail headers (which have several different character set and language encoding formats as well), to being involved in searching and sorting messages, by sqwebmail, Cone, or the IMAP server. Most the impact from the rewrite should hopefully go unnoticed, aside from the larger character set universe known to sqwebmail, Cone, and Courier-IMAP. Other changes since the last release: * There's a search box at the bottom of the folder index page. sqwebmail searches the messages in the order of their appearance on the folder index screen. The search starts with the first message on the folder index screen. If the folder index screen does not start with the first message in the folder, the previous messages are not searched, and the search stops when enough messages with the search string are found to fill one folder index screen. In this manner, a poorly chosen search string that finds a hit in a lot of messages will limit itself. If necessary, the search can be repeated after navigating the folder index screen to the starting point for the second search. * Up to four occurrences of the search string in each message are shown on the search results page. * Suppress logging the contents of a failed AUTH command in syslog, in case it includes encoded passwords. * Fix requirements of rpm spec files, to depend on /etc/cron.hourly, rather than a specific cron package. * Adjust indentation to avoid parts of DSNs unintentionally interpreted as quoted content. pgpPSwCZFOyoR.pgp Description: PGP signature -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] IPV6 and Debian testing
Gordon Messmer writes: On 01/20/2011 07:19 PM, Sam Varshavchik wrote: Gordon Messmer writes: Wouldn't the easiest fix be to use IPV6_V6ONLY mentioned in section 5.3 of RFC 3493? No, that's something that's unrelated. I really think they're the same thing. The documentation for the IPV6_V6ONLY sockopt indicates that this is a boolean value controlling whether or not an AF_INET6 is V6ONLY or not. The Linux man page for ipv6 further clarifies that /proc/sys/net/ipv6/bindv6only, which Debian has set to 1 specifies the default value for IPV6_V6ONLY. If Courier specifically sets IPV6_V6ONLY to int 0, it should override Debian's behavior and allow the application to function normally: int on = 0; if (setsockopt(s, IPPROTO_IPV6, IPV6_V6ONLY, (char *)on, sizeof(on)) == -1) perror(setsockopt IPV6_V6ONLY); Splendid. We have our solution. I'm in the middle of pulling all the innards out, and hopefully putting them back, sometime soon, but this is going to be the next thing on the chopping block. pgpyeSnlPrHtp.pgp Description: PGP signature -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] local-extensions with different character?
Matus UHLAR - fantomas writes: Matus UHLAR - fantomas writes: is it possible to use different character for local extensions? many of our customers are already using dashes in mail addresses, so using dash for local extensions could cause problems. sendmail supports + for similar usage, perhaps we could use that one? It seems that this would require change courier code, would it be an easy change? On 16.12.10 20:05, Sam Varshavchik wrote: Nope -- no easy way to change that. can I at least limit local extensions to some prefixes? I would be OK with the srs- prefix, but not with others... I'm not quite sure what you're trying to do here. Even though courier uses -, you can have accounts that contain a - in their name. The logic to resolve an ambiguous address is, hopefully, intuitive, but why make one's life so complicated? pgpKWG4oT5VdN.pgp Description: PGP signature -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] IPV6 and Debian testing
Mark Constable writes:
I upgraded to Debian testing with courier-mta 0.65.0 on one server
about 6 months ago and courier stopped working with strange network
errors so I moved that mail host to another non-Debian box. Today I
finally found a solution after seeing this and some more googling...
# strace testmxlookup debian.org
[...]
sendto(3, IC\1\0\0\1\0\0\0\0\0\0\6debian\3org\0\0\17\0\1, 28, 0, {sa_family=AF_INET6,
sin6_port=htons(53), inet_pton(AF_INET6, :::127.0.0.1, sin6_addr),
sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 ENETUNREACH (Network is unreachable)
[...]
edit /etc/sysctl.d/bindv6only.conf
change net.ipv6.bindv6only = 1 to 0
invoke-rc.d procps restart
This setting only affected courier, all other services seemed to
work just fine.
My question is how to configure courier-mta to work with the above
default net.ipv6.bindv6only = 1 setting for when Debian testing
becomes stable and I go to upgrade other servers?
The problem is that IPv6-mapped IPv4 addresses are a part of the official
IPv6 spec. If you have an IPV6 socket, you are expected to be able to use it
to contact IPv4 addresses. RFC 4038, 4.2.
Courier's code relies on being able to use IPv6 sockets to connect to either
IPv4 or IPv6 addresses. There is no way to configure that an IPv4 socket be
used for IPv4 addresses, and IPv6 sockets for IPv6 addresses. Doing
something like this requires some code rewriting.
pgpcspF0oziiq.pgp
Description: PGP signature
--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] IPV6 and Debian testing
Mark Constable writes: On 21/01/11, Sam Varshavchik wrote: My question is how to configure courier-mta to work with the above default net.ipv6.bindv6only = 1 setting for when Debian testing becomes stable and I go to upgrade other servers? The problem is that IPv6-mapped IPv4 addresses are a part of the official IPv6 spec. If you have an IPV6 socket, you are expected to be able to use it to contact IPv4 addresses. RFC 4038, 4.2. Courier's code relies on being able to use IPv6 sockets to connect to either IPv4 or IPv6 addresses. There is no way to configure that an IPv4 socket be used for IPv4 addresses, and IPv6 sockets for IPv6 addresses. Doing something like this requires some code rewriting. Perhaps this could be a heads up that when Debian 6 (squeeze) is released in the next month or so that this will become an issue for Debian stable + courier users. ~ cat /etc/sysctl.d/bindv6only.conf # This sysctl sets the default value of the IPV6_V6ONLY socket option. # # When disabled, IPv6 sockets will also be able to send and receive IPv4 # traffic with addresses in the form :::192.0.2.1 and daemons listening # on IPv6 sockets will also accept IPv4 connections. # # When IPV6_V6ONLY is enabled, daemons interested in both IPv4 and IPv6 # connections must open two listening sockets. # This is the default behaviour of almost all modern operating systems. net.ipv6.bindv6only = 1 For future googlers, I had to change the above 1 to 0 for courier to work. One way of mitigating this situation for your specific case, of DNS resolution on localhost, is to append nameserver ::1 In addition to nameserver 127.0.0.1 in /etc/resolv.conf. If Courier fails to reach 127.0.0.1, it should then try ::1, and succeed. This won't address, though, outgoing connections. Courier will still try to use IPv6 sockets to connect to IPv4 addresses for sending mail. The only thing that can be done there is to smarthost all outgoing mail, to another IPv6 relay. pgpk7AhLftNXs.pgp Description: PGP signature -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] IPV6 and Debian testing
Gordon Messmer writes: On 01/20/2011 03:31 PM, Sam Varshavchik wrote: Courier's code relies on being able to use IPv6 sockets to connect to either IPv4 or IPv6 addresses. There is no way to configure that an IPv4 socket be used for IPv4 addresses, and IPv6 sockets for IPv6 addresses. Doing something like this requires some code rewriting. Wouldn't the easiest fix be to use IPV6_V6ONLY mentioned in section 5.3 of RFC 3493? No, that's something that's unrelated. But RFC 3493 also serves as a clear counterexample to what Debian's doing. The language in section 3.7 is just as clear as day: Applications may use AF_INET6 sockets to open TCP connections to IPv4 nodes, or send UDP packets to IPv4 nodes, by simply encoding the destination's IPv4 address as an IPv4-mapped IPv6 address, and passing that address, within a sockaddr_in6 structure, in the connect() or sendto() call. With such, clear, unambiguous language, you can't help but ask yourself not only WTF is Debian's default config explicitly does the opposite, but why is that option even in the Linux kernel to start with? So now you have not one, but multiple RFCs document that IPv6 sockets should be interoperable IPv4, and I just do not understand why this freight train is going in exactly the opposite direction. This one's a headscratcher. pgp0d73B69flc.pgp Description: PGP signature -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] SPF and mailing lists
Mark Constable writes: I'm using these SPF related entries in bofh... opt BOFHSPFHELO=all opt BOFHSPFMAILFROM=all opt BOFHSPFFROM=all,mailfromok opt BOFHSPFTRUSTME=1 where I thought BOFHSPFFROM=all,mailfromok would let through all or most messages from mailing-lists in general but it seems that (from this list) if anyone sends a message to it from a domain that uses SPF then it bounces, ie; Jan 19 00:19:59 mail courieresmtpd: error, relay=:::87.238.50.203, from=qt-qml-bounces+markc=renta@qt.nokia.com: 517 SPF softfail ext-ivailo.il...@nokia.com: Address does not pass the Sender Policy Framework The qt.nokia.com sub-domain does not have any SPF record at all but nokia.com does so it seems the From: is overriding the From . Of course I never get to see the headers of these 517 messages so it's a bit hard to exactly work out the difference between the ones that work and the bounces. Are my opt BOFH* lines just wrong, or any suggestions how to work around this? Did you restart Courier after making changes in the bofh file. With all, you should not be bouncing mail, just recording the SPF verification status in the headers. pgpPZ1Di2vMf5.pgp Description: PGP signature -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] mailbot and -T forward / forwardatt
Jani Ollikainen writes: On 15.01.2011 03:40, Sam Varshavchik wrote: # cat testmail.txt | /usr/lib/courier/bin/mailbot -T forward -c UTF-8 -t reply.txt -A 'From: u...@example.org' -s 'Test' 511 Headers specify no receipients. sendmail: Unable to submit message. But without -T parameters it works # cat testmail.txt | /usr/lib/courier/bin/mailbot -c UTF-8 -t reply.txt -A 'From: u...@example.org' -s 'Test' A forward is not a reply. -T controls not just how the content of the generated message is formatted, but also the headers. When you hit the Forward menu item or button in your mail client, the new message comes up without any listed recipients. Same thing here. Ok, then I would need to add -A 'To: $VARIABLE' to mailbot line in mailfilter. After reading documentation there is FROM but This information may or may not be available to maildrop on your system. /etc/courier/courierd: DEFAULTDELIVERY=|| /usr/lib/courier/bin/dotforward | /usr/lib/courier/bin/maildrop -w 90 And documentation also says If the -f option is not given, maildrop looks for the From_ line in the message.. And when doing `set /tmp/variables.txt` in .mailfilter I don't see FROM. So if I would like to use -T forward or -T forwardatt in mailfilter to send auto replies what is needed? You should have $SENDER available. And, once again, make sure that you fully understand how all your manufactured shell scripting needs to quote its variables. Otherwise, you'll have an exploitable security hole on your hands. pgpWDbvWPP1r7.pgp Description: PGP signature -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Courier 20110101 build
Matus UHLAR - fantomas writes: On 02.01.11 11:33, Sam Varshavchik wrote: Download: http://www.courier-mta.org/download.php A few minor fixes. Changes: • Suppress logging the contents of a failed AUTH command in syslog, in case it includes encoded passwords. can this differentiate between incvalid usernames and invalid passwords? If not, can this be turned off? Explain how you were able to tell the difference previously. You couldn't. I know about potential security problems about revealed passwords, but I would like to know when an attack is done against users' passwords No. Previously, only some opaque encoded blob was logged, whatever its contents were. Furthermore, there is no substantial difference. Look for failed AUTH errors. I see no difference between whether there's userid guessing or password guessing going on. Both the requested userid and password is collected at the same time. Either they are accepted, or they're not. pgpfSo74Tyifh.pgp Description: PGP signature -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] mailbot and -T forward / forwardatt
Jani Ollikainen writes: Hi, Noticed that there's -T in mailbot and I think that those sounds better to have the original message as attachment than directly reply to it. As if the original message is long, reader might not notice the reply text. Did some testing: # cat testmail.txt | /usr/lib/courier/bin/mailbot -T forward -c UTF-8 -t reply.txt -A 'From: u...@example.org' -s 'Test' 511 Headers specify no receipients. sendmail: Unable to submit message. But without -T parameters it works # cat testmail.txt | /usr/lib/courier/bin/mailbot -c UTF-8 -t reply.txt -A 'From: u...@example.org' -s 'Test' Why? A forward is not a reply. -T controls not just how the content of the generated message is formatted, but also the headers. When you hit the Forward menu item or button in your mail client, the new message comes up without any listed recipients. Same thing here. pgpVuXBpAUI7x.pgp Description: PGP signature -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Courier and Dovecot delivery
komodo writes: Hi I'm trying to setup courier with Deovecot LDA instead of maildrop. I need to use sieve filters. And i am not able to find some usefull informations about settings courier with dovecot on the internet Everything is working fine if i have dot-courier file in users home directory like this | /usr/bin/spamc -U /var/run/spamassassin/spamd.sock -e /usr/libexec/dovecot/deliver -f $SENDER Now i need to setup this globaly so i need to replace DEFAULTDELIVERY in courierd, and here is the problem. I need this -f $SENDER there, but i am not able to do this in courierd config file. Of course you can do it. You just need to understand how the configuration file is read and used. And how quoting works. You should use apostrophes to set the DEFAULTDELIVERY variable in courierd, so that it contains the verbatim variable reference. So that variable expansion occurs when the default delivery instructions take place. And, oh, you better use double quotes to quote $SENDER itself. Otherwise, if someone were to send you an email with the sender address set to something like this: MAIL FROM:;rm -rf $HOME;@example.com then you'll have lots of fun on your hands, if Courier doesn't reject such a sender address for syntax reason -- can't think of any reason why. Anytime you want to put together some complicated rube-goldbergian contraption with your mail system, you must have it audited by someone with experience in information security and penetration testing. Otherwise, it's only a matter of time before you get hacked. pgpC4SemUF5Qy.pgp Description: PGP signature -- Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] make check failed on maildrop/testsuite.txt.idn
pascal writes: El 09/01/11 17:04, Sam Varshavchik escribió: pascal writes: The output of make check is: Making check in maildrop make[1]: Entering directory `/home/pascal/courier-0.65.2.20110103/maildrop' make check-am make[2]: Entering directory `/home/pascal/courier-0.65.2.20110103/maildrop' ./testsuite | cmp -s - ./testsuite.txt.idn make[2]: *** [check-am] Error 1 make[2]: Leaving directory `/home/pascal/courier-0.65.2.20110103/maildrop' make[1]: *** [check] Error 2 make[1]: Leaving directory `/home/pascal/courier-0.65.2.20110103/maildrop' make: *** [check-recursive] Error 1 thanks for any help or a clue to keep searching As you can see from the above, the makefile in the maildrop directory runs the testsuite script, and compares its output to testsuite.txt.idn. There's a difference, hence the error. Your next step is to run the testsuite script yourself, compare its output to testsuite.txt.idn, and see where the disrepancy is. first, thanks for anserwing Ok, i have tried it pas...@spinoza:~/courier-0.65.2.20110103$ cd maildrop pas...@spinoza:~/courier-0.65.2.20110103/maildrop$ ./testsuite a pas...@spinoza:~/courier-0.65.2.20110103/maildrop$ diff a testsuite.txt.idn 115c115 On dom, 22 nov 2009 10:57:32 -0500, --- On Sun, 22 Nov 2009 10:57:32 -0500, it seems to me that there is no difference (did i make it right?) pascal For some reason your locale is affecting the testsuite output. Can you show the output from the following four commands: locale date LANG=en_US.utf-8 date LANG=en_US.utf8 date pgpZPFULWU4cd.pgp Description: PGP signature -- Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] make check failed on maildrop/testsuite.txt.idn
pascal writes: El 09/01/11 18:24, pascal escribió: El 09/01/11 17:04, Sam Varshavchik escribió: pascal writes: The output of make check is: Making check in maildrop make[1]: Entering directory `/home/pascal/courier-0.65.2.20110103/maildrop' make check-am make[2]: Entering directory `/home/pascal/courier-0.65.2.20110103/maildrop' ./testsuite | cmp -s - ./testsuite.txt.idn make[2]: *** [check-am] Error 1 make[2]: Leaving directory `/home/pascal/courier-0.65.2.20110103/maildrop' make[1]: *** [check] Error 2 make[1]: Leaving directory `/home/pascal/courier-0.65.2.20110103/maildrop' make: *** [check-recursive] Error 1 thanks for any help or a clue to keep searching As you can see from the above, the makefile in the maildrop directory runs the testsuite script, and compares its output to testsuite.txt.idn. There's a difference, hence the error. Your next step is to run the testsuite script yourself, compare its output to testsuite.txt.idn, and see where the disrepancy is. first, thanks for anserwing Ok, i have tried it pas...@spinoza:~/courier-0.65.2.20110103$ cd maildrop pas...@spinoza:~/courier-0.65.2.20110103/maildrop$ ./testsuite a pas...@spinoza:~/courier-0.65.2.20110103/maildrop$ diff a testsuite.txt.idn 115c115 On dom, 22 nov 2009 10:57:32 -0500, --- On Sun, 22 Nov 2009 10:57:32 -0500, it seems to me that there is no difference (did i make it right?) pascal sorry! what you were expecting was : pas...@spinoza:~/courier-0.65.2.20110103/maildrop$ diff testsuite.txt.idn testsuite.txt.noidn Nope, not this. I was looking for what you gave initially. pgpxhgSHy3g5c.pgp Description: PGP signature -- Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Courier 20110109
Download: http://www.courier-mta.org/download.php I pushed out new builds of courier, courier-imap, and sqwebmail packages. • The sqwebmail build fixes a few more bugs in the new search code. • Courier-IMAP's search/sort/thread code innards were rewritten, replacing the internal characted unicode tables with an iconv-based implementation. The IMAP server nows accepts search strings using any iconv-supported character set. This depends entirely on the IMAP client support; it's probably unlikely that this change would be noticed, but it's a step towards a complete conversion to the iconv library, which is a good thing; but there's always the possibility of breaking existing code, with something like this. • The courier package includes the sqwebmail and courier-imap changes. pgp06HPo5R4UB.pgp Description: PGP signature -- Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
