Re: [courier-users] Courier not handling cases propperly?
I remember reading somewhere in the SMTP RFC about the fact that e-mail addresses are to be case-insensitive. domains yes, but everything before the @ can be case sensitive. Courier is case sensitive unless you tell it to not be like so: touch /etc/courier/locallowercase If you do that, courier will drop all incoming messages to lower case so you need to make sure that none of your accounts have upper case letters in them, or else you'll get a 550 again. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Permission Denied Error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Are you sure that courier is configured to run as the courier user/group? It may configured to run as something else. Common choices are mail and nobody. To find out which user courier is running as, use the courier-config program. If you discover that courier is running as something other than the courier user/group, you have two choices. You can either fix up the permitions, or you can recompile courier so that it runs as the desired user and group. - --- Joseph C. Lininger [EMAIL PROTECTED] - - Original Message - From: Carolyn Longfoot [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 10, 2004 8:51 AM Subject: [courier-users] Permission Denied Error All, since upgrading to courier-0.44.2_1 I receive the following errors: Mar 10 6:34:33 box courierd: Purging /var/spool/courier/msgq Mar 10 6:34:33 box courierd: Purging /var/spool/courier/msgs Mar 10 6:34:33 box courierd: Permission denied Mar 10 6:34:33 box courierd: ABNORMAL TERMINATION, exit status: 1 Mar 10 6:34:33 box courierd: Will restart in 60 seconds. ... etc repeat This looks like the GID/UID issue that has come up before, but they are the same for me: /etc/group courier:*:1003:courier /etc/passwd courier:*:1003:1003:Courier Mail System:/nonexistent:/sbin/nologin And this box# ls -l /var/spool/courier total 544 -r 1 courier courier 0 Mar 9 10:54 .noident drwxr-x--- 2 courier courier 512 Mar 9 10:54 allfilters drwxrwx--- 2 courier courier 512 Mar 9 21:01 authdaemon -rw--- 1 root wheel524288 Mar 9 15:37 couriersslcache drwx-- 2 courier courier 512 Mar 9 10:54 faxtmp drwxr-x--- 2 courier courier 512 Mar 9 10:54 filters drwxr-x--- 2 courier courier 512 Mar 9 10:54 msgq drwxr-x--- 2 courier courier 512 Mar 9 10:54 msgs srwxrwxrwx 1 courier courier 0 Mar 9 13:16 sqwebmail.sock -rw--- 1 courier courier 0 Mar 9 13:16 sqwebmail.sock.lock -rw-r--r-- 1 courier courier 6 Mar 9 13:16 sqwebmail.sock.pid drwxrwx--- 8 courier courier 512 Mar 10 15:32 tmp What's wrong with this picture and what user/group is courierd expecting if not courier? Thanks for any help, Caro _ Frustrated with dial-up? Lightning-fast Internet access for as low as $29.95/month. http://click.atdmt.com/AVE/go/onm00200360ave/direct/01/ --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=clic k ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users -BEGIN PGP SIGNATURE- Version: PGP 8.0.3 iQA/AwUBQFAh2yenap9Jqj2wEQI7RACdGTdxQf3RQn3BETflUEgLKT1Z+qwAn23m wBN81tKEMNcFXkG7P01qOnqQ =5v1V -END PGP SIGNATURE- --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Permission Denied Error
After the hint to look at courier-config that is exactly what I did. Turns out the old install used different ID's from the new one. Grrr... Thanks all, Caro or you can recompile courier so that it runs as the desired user and group. _ Get a FREE online computer virus scan from McAfee when you click here. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] RE: How to force SMTP AUTH only for MAIL FROM addresses of hosted domains?
Lorenzo Perone [EMAIL PROTECTED] wrote: I'm actually trying to solve a serious spam problem: spammers sending mail claiming to be someone of my domain, asking people to send their user id and password, etc. I've written a perl script that can make (fairly) sure if one is authenticated - but I can not just throw away the other mails, i.e. those which are not authenticated (and still have a From: header pretending to be from the same domain) because I cannot tell, at that level, whether it's a spammer or a user with an old client who tries to send some mail without authenticating first. If the server forced authentication for those claiming to be a hosted user at the Return Path (MAIL FROM) level, spammers could still claim to be someone else and later, in the DATA, use a From: of my domain. But in the latter case I could easilly catch that with my maildrop-triggered script. Of course, a last-resort option would be to make an extfilter out of the script, and alter the subject or body, telling that it could _possibly_ be spam and not to trust the sender in case of doubt. But an error at SMTP level, which the users would inevitably notice and force them to update/setup their clients would be much better. I've setup Communigate Pro several times - and its smtp module has this option for example. I can't believe that an otherwise superb product as courier is going to leave me alone on this issue... :| Please try to be a bit more coherent. I'm having a hard time trying to understand your problem. Just reading your subject (see what a precise, to the point subject can do for you? *g*), I think you want to reject incoming messages that claim (by means of the envelope sender) to come from one of your hosted domains *if* the SMTP connection hasn't been authenticated. That's a subset of what SPF[1] does. Until the SPF people manage to make a patch to properly integrate SPF (and SRS, a closely related technology) into Courier, you can use the SPF module of Courier::Filter[2]. As Courier::Filter (like any courierfilter) only activates after the incoming message has been completely received, you cannot save the traffic caused by spam, but on the other hand, you can examine the whole message header and body to make more detailed checks. If you really only want to check for your *own* hosted domains, you can as well write a new Courier::Filter::Module::FromHostedDomain filter module (it's easy!) that matches any messages that come from a hosted domain. Using such a module in trusting mode (see the documentation of Courier::Filter) does exactly what you want. [1] http://spf.pobox.com [2] http://search.cpan.org/~jmehnle/Courier-Filter-0.12/ --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Re: Courier/authmysql failure
Jason Dixon writes: On Mar 10, 2004, at 6:51 PM, Sam Varshavchik wrote: Jason Dixon writes: I'm having problems getting a new server running Courier imapd (1.7.2) on OpenBSD 3.4 with authmysqlrc and authpwd. Authpwd works great for local real accounts, but I keep running into authentication problems with the virtual accounts. I've turned on debugging, but all I'm seeing in the log is LOGIN FAILED. I would greatly appreciate it if anyone could point me in the right direction. Here are my config files: You have post a lot of information. Except for the actual database record for the account in question. Because it affects _all_ virtual users. Nevertheless, here's an example: mysql select * from mailbox where username like '%testy%'\G; *** 1. row *** username: [EMAIL PROTECTED] This means that you must log in with the userid set to '[EMAIL PROTECTED]', not 'testy'. Additionally, check for spurious whitespace in the configuration file. pgp0.pgp Description: PGP signature
[courier-users] Re: How to force SMTP AUTH only for MAIL FROM addresses of hosted domains?
Lorenzo Perone writes: Is there anyone that can help me, who got it working...? There's nothing in the documentation that even remotely suggests that such a bizarre configuration is possible in the first place. pgp0.pgp Description: PGP signature
[courier-users] Re: 550 Error: No multihop relaying . . .
Jason Flatt writes: Last Friday a client of mine started getting the error message in the subject for all out-bound e-mails. All in-bound e-mail works fine and all There's no such error message in Courier. pgp0.pgp Description: PGP signature
[courier-users] Re: Whitelist for RBL blocking ?
Mark Constable writes: Is it possible in anyway to be able to except or whitelist some IPs from RBL (ie; spamcop) blocking ? Yes. Use smtpaccess to set BLOCK to an empty string for those IP address ranges. pgp0.pgp Description: PGP signature
Re: [courier-users] Re: Courier/authmysql failure
On Mar 11, 2004, at 7:09 AM, Sam Varshavchik wrote: username: [EMAIL PROTECTED] This means that you must log in with the userid set to '[EMAIL PROTECTED]', not 'testy'. /me smacks himself in the forehead. LOL. Thanks, Sam! -- Jason Dixon, RHCE DixonGroup Consulting http://www.dixongroup.net --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Cannot Delete Mail from Trash
Hi, I recently installed our second mail server and followed the guidelines given by Bill's Qmail Toaster (http://www.shupp.org/toaster/). I then gzipped all the vpopmail users and moved them to the new server. Everything is working flawlessly except for one small problem. When a user deletes/purges mail (either from Outlook or Squirrelmail), it gets put in the Trash folder. Upon attempting to delete/purge the Trash folder, the messages are un-marked as deleted and simply marked as read. Help! I've included portions of my imap config below. I've searched quite a bit on the list and the Internet but have yet to come upon an answer. Can anyone help? --Configuration Setup via http://www.shupp.org/toaster/ IMAP_TRASHFOLDERNAME="Trash" IMAP_EMPTYTRASH=Trash:7,Sent:7 IMAP_MOVE_EXPUNGE_TO_TRASH=1
Re: [courier-users] RE: How to force SMTP AUTH only for MAIL FROM addresses of hosted domains?
On 11. Mrz 2004, at 12:51, Julian Mehnle wrote: Lorenzo Perone [EMAIL PROTECTED] wrote: I'm actually trying to solve a serious spam problem: spammers sending mail claiming to be someone of my domain, asking people to send their user id and password, etc. I've written a perl script that can make (fairly) sure if one is authenticated - but I can not just throw away the other mails, i.e. those which are not authenticated (and still have a From: header pretending to be from the same domain) because I cannot tell, at that level, whether it's a spammer or a user with an old client who tries to send some mail without authenticating first. If the server forced authentication for those claiming to be a hosted user at the Return Path (MAIL FROM) level, spammers could still claim to be someone else and later, in the DATA, use a From: of my domain. But in the latter case I could easilly catch that with my maildrop-triggered script. Of course, a last-resort option would be to make an extfilter out of the script, and alter the subject or body, telling that it could _possibly_ be spam and not to trust the sender in case of doubt. But an error at SMTP level, which the users would inevitably notice and force them to update/setup their clients would be much better. I've setup Communigate Pro several times - and its smtp module has this option for example. I can't believe that an otherwise superb product as courier is going to leave me alone on this issue... :| Please try to be a bit more coherent. I'm having a hard time trying to understand your problem. Just reading your subject (see what a precise, to the point subject can do for you? *g*), I think you want to reject incoming messages that claim (by means of the envelope sender) to come from one of your hosted domains *if* the SMTP connection hasn't been authenticated. sorry for that! nonetheless, you got exactly what i meant :). That's a subset of what SPF[1] does. Until the SPF people manage to make a patch to properly integrate SPF (and SRS, a closely related technology) into Courier, [1] http://spf.pobox.com SPF is a cool way to use existing technology (DNS) to implement some kind of control over MAIL FROM. Yet as I understand it, nameservers around the globe need to have the IN TXT v=spf1... entry to enforce this. it definitively needs some more advertising before it can be used (besides implementations in mtas such as courier). you can use the SPF module of Courier::Filter[2]. As Courier::Filter (like any courierfilter) only activates after the incoming message has been completely received, you cannot save the traffic caused by spam, but on the other hand, you can examine the whole message header and body to make more detailed checks. If you really only want to check for your *own* hosted domains, you can as well write a new Courier::Filter::Module::FromHostedDomain filter module (it's easy!) that matches any messages that come from a hosted domain. Using such a module in trusting mode (see the documentation of Courier::Filter) does exactly what you want. [2] http://search.cpan.org/~jmehnle/Courier-Filter-0.12/ This is great. Thanks a _lot_ for this tip. I'm sure I can solve most of the issues with it :). I guess the control files described in [2] are among other things, what I was missing. And, while filters are triggered after the DATA segement, they seem to still allow to return a message within the SMTP transaction: (from [2]): The mail filter processes the message and its control file(s), and returns an SMTP-style status response. If the status response is a positive (2xx) one, Courier accepts the message. Otherwise, Courier rejects the message using the returned response code and text. Regards, Lorenzo --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] IMAP AUTH Problems
Hello everyone. I'm new to this list as well as Courier-IMAP so please forgive me for my ignorance. I have been given the thankless, unhappy task of getting a Postfix + Courier server up and running by Friday of this week. (3/12/04) Firstly, I am receiving the following message when I telnet to port 143: Trying 127.0.0.1... Connected to localhost.avcschool.com. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP ready. Copyright 1998-2004 Double Precision, Inc. See COPYING for distribution information. LOGIN username password NO Error in IMAP command received by server. * BYE Courier-IMAP server shutting down LOGOUT OK LOGOUT completed I am not too sure what is wrong but I can tell you that my AUTHMODULES=authdaemon authpwd . Also, I am working with a FreeBSD box. Now, all documentation seems to state that AUTHMODULES is managed in imapd.conf. Unfortunately, this file does not seem to exist. But I have found a /usr/lib/etc/imapd without the .conf. In it I did find a line for AUTHMODULES. I edited it but don't know if this is indeed the conf file in question. Also, do any of you think it possible to get a fully functional Postfix + Courier-IMAP server up and running in two days? Thank you very much. -- David Brock Technology Coordinator Apple Valley Christian School [EMAIL PROTECTED] --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] IMAP AUTH Problems
On Thursday 11 March 2004 07:49, Tech wrote:
Trying 127.0.0.1...
Connected to localhost.avcschool.com.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL
ACL2=UNION STARTTLS] Courier-IMAP ready. Copyright 1998-2004
Double Precision, Inc. See COPYING for distribution information.
LOGIN username password
NO Error in IMAP command received by server.
* BYE Courier-IMAP server shutting down
LOGOUT
OK LOGOUT completed
I am not too sure what is wrong but I can tell you that my
AUTHMODULES=authdaemon authpwd . Also, I am working with a FreeBSD
box. Now, all documentation seems to state that AUTHMODULES is
managed in imapd.conf. Unfortunately, this file does not seem to
exist. But I have found a /usr/lib/etc/imapd without the .conf. In it
I did find a line for AUTHMODULES. I edited it but don't know if
this is indeed the conf file in question.
Also, do any of you think it possible to get a fully functional
Postfix + Courier-IMAP server up and running in two days?
Prefix your commands with a number.
001 LOGIN ${username} ${password}
--
Jesse Keating RHCE (geek.j2solutions.net)
Fedora Legacy Team (www.fedoralegacy.org)
GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub)
Was I helpful? Let others know:
http://svcs.affero.net/rm.php?r=jkeating
pgp0.pgp
Description: signature
Re: [courier-users] IMAP AUTH Problems
Hi, I got my own Courier working just today (Wheee! ;) ): it's not a matter of your authentication modules, but you have to prefix every command with an (freely selectable (?)) alphanumeric string, eg.: A1234 LOGIN [EMAIL PROTECTED] mypassword A1234 OK Password accepted B0003 NOOP B0003 OK ...etc... ...then it'll work :) You may have a glance at the IMAP-RFC (found at http://www.imap.org/about/ for instance), where this much more of the protocol is described. Good luck! cu, Bjoern --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] outgoing mail
Hi, I've asked this question before, and got the answer that I shall use mailfilter for it, but afterwards I couldn't manage to get it work. So my problem was that I use courier, and people who have account to the server can send mail after authentication, which is not a problem. The problem is that they - after auth - can send mail from any address, even if it is not hosted on my server. So I need to specify email address(es) for each email account on the server. I would appreciate a working example for this, in any way. I use mysql auth btw. Thanks in advance, Peter Koczan --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] FreeBSD: Cannot find function res_query
I noticed some recent messages about problems with NetBSD and this same error (Cannot find function res_query). I just tried to compile 3.0.0 of imapd on FreeBSD 4.9. While trying to configure authlib, I got the error. To fix it, I had to change the configure script to include sys/types.h before netinet/in.h. I didn't see a bug database on the sourceforge site, but I figured someone might want to know. -Eric --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] outgoing mail
On 12/03/2004, at 6:22 AM, Kóczán Péter wrote: Hi, I've asked this question before, and got the answer that I shall use mailfilter for it, but afterwards I couldn't manage to get it work. So my problem was that I use courier, and people who have account to the server can send mail after authentication, which is not a problem. The problem is that they - after auth - can send mail from any address, even if it is not hosted on my server. So I need to specify email address(es) for each email account on the server. You are using SMTP. It's a problem with the protocol, not the server. It would be possible to check using a courierfilter that the From: header was from your server, if the top Received: header has the AUTH keyword. -- Phillip Hutchings [EMAIL PROTECTED] http://www.sitharus.com/ smime.p7s Description: S/MIME cryptographic signature
[courier-users] authlib/configure script fails on OpenBSD 3.4
Hi everyone, I've tried everything that comes to mind and I can not get
this thing to load the appropriate header files, etc. All help is
greatly appreciated.
--- Screen Errors ---
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking whether -lresolv is needed for res_query... configure: error:
Cannot find function res_query
configure: error: /bin/sh './configure' failed for authlib
--- authlib/config.log excerpts ---
## - ##
## Platform. ##
## - ##
hostname =
uname -m = i386
uname -r = 3.4
uname -s = OpenBSD
uname -v = GENERIC#18
...
configure:4980: checking netinet/in.h presence
configure:4991: gcc -E conftest.c
configure:4997: $? = 0
configure:5016: result: yes
configure:5052: checking for netinet/in.h
configure:5059: result: yes
configure:5081: checking whether -lresolv is needed for res_query
configure:5107: gcc -o conftest -g -O2 -Wall -I.. -I./.. conftest.c 5
In file included from configure:5111:
/usr/include/netinet/in.h:134: syntax error before `in_addr_t'
/usr/include/netinet/in.h:209: syntax error before `u_int8_t'
/usr/include/netinet/in.h:213: syntax error before `int8_t'
/usr/include/netinet/in.h:228: syntax error before `int8_t'
In file included from /usr/include/netinet/in.h:502,
from configure:5111:
/usr/include/netinet6/in6.h:118: syntax error before `u_int8_t'
/usr/include/netinet6/in6.h:140: syntax error before `u_int8_t'
/usr/include/netinet6/in6.h:145: syntax error before `u_int32_t'
/usr/include/netinet6/in6.h:609: syntax error before `struct'
/usr/include/netinet6/in6.h:613: syntax error before `*'
/usr/include/netinet6/in6.h:615: syntax error before `*'
/usr/include/netinet6/in6.h:615: warning: data definition has no type or storage class
/usr/include/netinet6/in6.h:616: syntax error before `u_int8_t'
/usr/include/netinet6/in6.h:617: syntax error before `u_int8_t'
/usr/include/netinet6/in6.h:619: syntax error before `inet6_rthdr_space'
/usr/include/netinet6/in6.h:619: warning: data definition has no type or storage class
In file included from configure:5111:
/usr/include/netinet/in.h:510: syntax error before `int'
configure:5110: $? = 1
configure: failed program was:
| #line 5083 configure
| /* confdefs.h. */
|
| #define PACKAGE_NAME
| #define PACKAGE_TARNAME
| #define PACKAGE_VERSION
| #define PACKAGE_STRING
| #define PACKAGE_BUGREPORT
| #define AUTHCHANGEPASS 1
| #define HAVE_EXPECT 1
| #define HAVE_MD5LIB 1
| #define HAVE_SHA1LIB 1
| #define HAVE_HMACLIB 1
| #define USERDB /usr/local/courier/etc/userdb
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_STDIO_H 1
| #define HAVE_SYSLOG_H 1
| #define HAVE_NETINET_IN_H 1
| /* end confdefs.h. */
|
| #if HAVE_NETINET_IN_H
| #include netinet/in.h
| #endif
| #include resolv.h
|
| void (*func)()= (void (*)())res_query;
|
| int
| main ()
| {
| (*func)();
| ;
| return 0;
| }
configure:5151: gcc -o conftest -g -O2 -Wall -I.. -I./.. conftest.c -lresolv 5
In file included from configure:5155:
/usr/include/netinet/in.h:134: syntax error before `in_addr_t'
/usr/include/netinet/in.h:209: syntax error before `u_int8_t'
/usr/include/netinet/in.h:213: syntax error before `int8_t'
/usr/include/netinet/in.h:228: syntax error before `int8_t'
In file included from /usr/include/netinet/in.h:502,
from configure:5155:
/usr/include/netinet6/in6.h:118: syntax error before `u_int8_t'
/usr/include/netinet6/in6.h:140: syntax error before `u_int8_t'
/usr/include/netinet6/in6.h:145: syntax error before `u_int32_t'
/usr/include/netinet6/in6.h:609: syntax error before `struct'
/usr/include/netinet6/in6.h:613: syntax error before `*'
/usr/include/netinet6/in6.h:615: syntax error before `*'
/usr/include/netinet6/in6.h:615: warning: data definition has no type or storage class
/usr/include/netinet6/in6.h:616: syntax error before `u_int8_t'
/usr/include/netinet6/in6.h:617: syntax error before `u_int8_t'
/usr/include/netinet6/in6.h:619: syntax error before `inet6_rthdr_space'
/usr/include/netinet6/in6.h:619: warning: data definition has no type or storage class
In file included from configure:5155:
/usr/include/netinet/in.h:510: syntax error before `int'
configure:5154: $? = 1
configure: failed program was:
| #line 5127 configure
| /* confdefs.h. */
|
| #define PACKAGE_NAME
| #define PACKAGE_TARNAME
| #define PACKAGE_VERSION
| #define PACKAGE_STRING
| #define PACKAGE_BUGREPORT
| #define AUTHCHANGEPASS 1
| #define HAVE_EXPECT 1
| #define HAVE_MD5LIB 1
| #define HAVE_SHA1LIB 1
| #define HAVE_HMACLIB 1
| #define USERDB /usr/local/courier/etc/userdb
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
|
[courier-users] RE: outgoing mail
Phillip Hutchings [EMAIL PROTECTED] wrote: On 12/03/2004, at 6:22 AM, Kczn Pter wrote: I've asked this question before, and got the answer that I shall use mailfilter for it, but afterwards I couldn't manage to get it work. So my problem was that I use courier, and people who have account to the server can send mail after authentication, which is not a problem. The problem is that they - after auth - can send mail from any address, even if it is not hosted on my server. So I need to specify email address(es) for each email account on the server. You are using SMTP. It's a problem with the protocol, not the server. It would be possible to check using a courierfilter that the From: header was from your server, if the top Received: header has the AUTH keyword. Generally enforcing the From: header to be within a hosted domain doesn't make much sense. The From: header only contains the sender's address if there's no Sender: header. Generally, checking the *envelope sender* (from the message control file) is a better idea. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
RE: [courier-users] FreeBSD: Cannot find function res_query
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Huss Sent: Thursday, March 11, 2004 01:06 PM To: [EMAIL PROTECTED] Subject: [courier-users] FreeBSD: Cannot find function res_query I noticed some recent messages about problems with NetBSD and this same error (Cannot find function res_query). I just tried to compile 3.0.0 of imapd on FreeBSD 4.9. While trying to configure authlib, I got the error. To fix it, I had to change the configure script to include sys/types.h before netinet/in.h. I didn't see a bug database on the sourceforge site, but I figured someone might want to know. -Eric All, I experienced a similar error on OpenBSD 3.3: checking for netinet/in.h... yes checking whether -lresolv is needed for res_query... configure: error: Cannot find function res_query configure: error: /bin/sh './configure' failed for authlib Attached please find a tar ball with the config.log file. Sam Stern Baltimore, MD, USA courier-0-45-1-res_query-openbsd33-error-configure-log.tar.gz Description: Binary data
[courier-users] ssl problems with courier-imap 3.0
Hello gurus, I have just compiled courier-imap 3.0 with ssl support. Everything works perfect if I don't use ssl The problem is that I can't browse my folders with my IMAP client when I login with ssl. The login itself seems to be ok. I can see my certificate. Mar 11 21:59:24 www imapd-ssl: LOGIN, user=david, ip=[:::213.200.148.86], protocol=IMAP I have tried with different clients. Evolution, Microsoft Entourage and Apple mail.app. I get an unknown error respond from my mail clients. Is there a way to verbose the maillog. I don't know how to debug courier-imap. Where should I look?? Blue Skies, /David --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] RE: outgoing mail
You are using SMTP. It's a problem with the protocol, not the server. It would be possible to check using a courierfilter that the From: header was from your server, if the top Received: header has the AUTH keyword. Generally enforcing the From: header to be within a hosted domain doesn't make much sense. The From: header only contains the sender's address if there's no Sender: header. Generally, checking the *envelope sender* (from the message control file) is a better idea. Generally there's no Sender: header on personal emails. Lists often use them, but most MUAs don't. I know my mail client doesn't even listen to it, much to my annoyance. Bug reports have been filed :) People who want this sort of control are more likely to be worried about the From: header, as that's what shows to the receivers of the e-mails. Considering that, the envelope sender makes little sense to check, as it has no relation to the MUA's From: header. Normally MUAs link them, but they don't have to. -- Phillip Hutchings [EMAIL PROTECTED] http://www.sitharus.com/ smime.p7s Description: S/MIME cryptographic signature
[courier-users] RE: outgoing mail
Phillip Hutchings [EMAIL PROTECTED] wrote: Generally enforcing the From: header to be within a hosted domain doesn't make much sense. The From: header only contains the sender's address if there's no Sender: header. Generally, checking the *envelope sender* (from the message control file) is a better idea. Generally there's no Sender: header on personal emails. Lists often use them, but most MUAs don't. I know my mail client doesn't even listen to it, much to my annoyance. Bug reports have been filed :) People who want this sort of control are more likely to be worried about the From: header, as that's what shows to the receivers of the e-mails. Considering that, the envelope sender makes little sense to check, as it has no relation to the MUA's From: header. Normally MUAs link them, but they don't have to. First, it's just plain wrong to generally rely on the From: header. To determine the alleged sender address (it cannot be the *true* sender since it is easily forgeable), you may rely on the From: header exactly as long as there is no Sender: header. Regardless of how often that is the case, if there is a Sender: header, you *must* consider its value over the From: header as the alleged sender address. There's simply no point in arguing about that. You might want to always consider the From: header the sender address *for simplicity of code*, but be aware that it's just plain wrong. Second, IMO it *does* make sense to rely on the envelope sender if you somehow verify its validity (using sender authorization schemes or anti-forgery schemes like SPF, or maybe even Yahoo's DomainKeys) and then overwrite any existing Sender: header with it, optionally adding an X-Message-Flag: header as a warning if the original Sender: header contained a differing address. This methodology can even be a tool against phishing (visually faking the From: or Sender: addresses, e.g. [EMAIL PROTECTED] or [EMAIL PROTECTED] [EMAIL PROTECTED]). --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] How to force SMTP AUTH only for MAIL FROM addresses of hosted domains?
Hi Lorenzo! Lorenzo Perone schrieb am 2004-03-11 02:11:59: This means: it works - but it _shouldn't!_ Instead, I would prefer and I wished that if a MAIL FROM is within the hosted domains, the server said 535 Authentication required. I really would recomment against this setup as there are situations where it is okay for other servers to send you mails with local senders. Think of news websites that allow the users to transmit articles using their own e-mail address. Tot kijk Matthias signature.asc Description: Digital signature
[courier-users] Re: IMAP AUTH Problems
Tech writes: LOGIN username password This is not a valid IMAP command. I am not too sure what is wrong but I can tell you that my AUTHMODULES=authdaemon authpwd . This is wrong, too. You need to review the description of the authdaemon authentication module. pgp0.pgp Description: PGP signature
[courier-users] RE: How to force SMTP AUTH only for MAIL FROM addresses of hosted domains?
Matthias Wimmer [EMAIL PROTECTED] wrote: Lorenzo Perone schrieb am 2004-03-11 02:11:59: Instead, I would prefer and I wished that if a MAIL FROM is within the hosted domains, the server said 535 Authentication required. I really would recomment against this setup as there are situations where it is okay for other servers to send you mails with local senders. Think of news websites that allow the users to transmit articles using their own e-mail address. Actually, no. Such sites very well can (and should!) use an envelope sender within their own domain: MAIL FROM: [EMAIL PROTECTED] RCPT TO: [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] ... --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Re: FreeBSD: Cannot find function res_query
Eric Huss writes: I noticed some recent messages about problems with NetBSD and this same error (Cannot find function res_query). I just tried to compile 3.0.0 of imapd on FreeBSD 4.9. While trying to configure authlib, I got the error. To fix it, I had to change the configure script to include sys/types.h before netinet/in.h. I didn't see a bug database on the sourceforge site, but I figured someone might want to know. Someone now knows. Someone would've knows this sooner had people tried any one of the numerous development builds that lead up to the 3.0.0 release. pgp0.pgp Description: PGP signature
Re: [courier-users] RE: outgoing mail
First, it's just plain wrong to generally rely on the From: header. To determine the alleged sender address (it cannot be the *true* sender since it is easily forgeable), you may rely on the From: header exactly as long as there is no Sender: header. Regardless of how often that is the case, if there is a Sender: header, you *must* consider its value over the From: header as the alleged sender address. There's simply no point in arguing about that. You might want to always consider the From: header the sender address *for simplicity of code*, but be aware that it's just plain wrong. Tell that to all the people that write clients. Outlook 2000 MAY support it, but many don't. Most webmail systems and Apple Mail (what I use) doesn't. It may be plain wrong, but it happens a lot. (As evidenced by this message going to the wrong address...) Likewise, MIME should be formatted a certain way, but 99% of programmers seem to be unaware of this, judging by the number of automated messages that get wrapped by courier. Second, IMO it *does* make sense to rely on the envelope sender if you somehow verify its validity (using sender authorization schemes or anti-forgery schemes like SPF, or maybe even Yahoo's DomainKeys) and then overwrite any existing Sender: header with it, optionally adding an X-Message-Flag: header as a warning if the original Sender: header contained a differing address. This methodology can even be a tool against phishing (visually faking the From: or Sender: addresses, e.g. [EMAIL PROTECTED] or [EMAIL PROTECTED] [EMAIL PROTECTED]). That's a good point. I know my domain has SPF, though I don't actually run any spf checks yet. I'm considering installing Courier::Filter's SPF filter. If a filter that processed the envelope sender and rewrote the Sender: header existed, I would probably use it. It's useful to know. -- Phillip Hutchings [EMAIL PROTECTED] http://www.sitharus.com/ smime.p7s Description: S/MIME cryptographic signature
[courier-users] RE: outgoing mail
Phillip Hutchings [EMAIL PROTECTED] wrote: [...] You might want to always consider the From: header the sender address *for simplicity of code*, but be aware that it's just plain wrong. Tell that to all the people that write clients. Outlook 2000 MAY support it, but many don't. Most webmail systems and Apple Mail (what I use) doesn't. It may be plain wrong, but it happens a lot. Likewise, MIME should be formatted a certain way, but 99% of programmers seem to be unaware of this, judging by the number of automated messages that get wrapped by courier. Of course you are right in that a lot of software is sloppy. But that doesn't justify advising implementors or admins to be sloppy, too. If Lorenzo Perone is going to write his own filter, he'd better do it right. Especially since it really isn't much of an effort to use the Sender: header instead of From:, if it's there. Second, IMO it *does* make sense to rely on the envelope sender if you somehow verify its validity [...] and then overwrite any existing Sender: header with it [...] That's a good point. I know my domain has SPF, though I don't actually run any spf checks yet. I'm considering installing Courier::Filter's SPF filter. If a filter that processed the envelope sender and rewrote the Sender: header existed, I would probably use it. It's useful to know. Courier::Filter, and courierfilters in general, cannot modify messages due to a limitation in Courier, so I'm going to write a maildrop script or something similar to do just that. I'm performing SPF checks already, thus I consider the envelope senders of my incoming mail to be validated. So I can just use an independent maildrop script to rewrite the Sender: header. I'll post here as soon as I have a working solution. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] RE: How to force SMTP AUTH only for MAIL FROM addresses of hosted domains?
Lorenzo Perone wrote: On 11. Mrz 2004, at 12:51, Julian Mehnle wrote: That's a subset of what SPF[1] does. Until the SPF people manage to make a patch to properly integrate SPF (and SRS, a closely related technology) into Courier, [1] http://spf.pobox.com SPF is a cool way to use existing technology (DNS) to implement some kind of control over MAIL FROM. Yet as I understand it, nameservers around the globe need to have the IN TXT v=spf1... entry to enforce this. For the purposes of protecting your own domain, only *your* DNS servers need the TXT entry. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] forcing Courier to accept mail for a domain
I need to force Courier to accept mail for a domain. Right now it rejects mail to that domain with a 513 Relaying denied message. I tried adding a line to esmtproutes with my domain name and the IP address of the local machine, but it didn't make any difference. I also have the domain listed in esmtpacceptmailfor and hosteddomains, and an entry in aliases to deliver the mail. Is there anything else I can do? Thanks, Michael Best --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Re: forcing Courier to accept mail for a domain
Michael Best writes: I need to force Courier to accept mail for a domain. Right now it rejects mail to that domain with a 513 Relaying denied message. I tried adding a line to esmtproutes with my domain name and the IP address of the local machine, but it didn't make any difference. I also have the domain listed in esmtpacceptmailfor and hosteddomains, and an entry in aliases to deliver the mail. Is there anything else I can do? Prove that you've listed the domain in esmtpacceptmailfor, and that you've specified the domain in the RCPT TO: command. pgp0.pgp Description: PGP signature
RE: [courier-users] Re: forcing Courier to accept mail for a domain
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sam Varshavchik Sent: Thursday, March 11, 2004 8:31 PM To: [EMAIL PROTECTED] Subject: [courier-users] Re: forcing Courier to accept mail for a domain Michael Best writes: I need to force Courier to accept mail for a domain. Right now it rejects mail to that domain with a 513 Relaying denied message. I tried adding a line to esmtproutes with my domain name and the IP address of the local machine, but it didn't make any difference. I also have the domain listed in esmtpacceptmailfor and hosteddomains, and an entry in aliases to deliver the mail. Is there anything else I can do? Prove that you've listed the domain in esmtpacceptmailfor, and that you've specified the domain in the RCPT TO: command. When I thought about it more, I tried running makeacceptmailfor and then sending the email again. Now it works! Thanks for the challenge! -- Michael Best --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
