Re: [courier-users] mailfilter deliver and mark as read option?
Chris Petersen said the following on 11/03/2004 05:55 AM: I currently have a mailfilter rule that copies certain incoming messages to an archive maildir. These come in marked as new messages, so I'm wondering if there is a way via the mailfilter to mark them as read so they don't trigger new-message notification in my mail clients. There is no way to do that. so is there a non-maildrop (ie. shellscript) way to do it? file rename? directory move? Maybe you may abuse fetchmail for this. As far as I understand the man-page, fetching mail with the keep-Option set should mark mails as read while leaving them on the server. Regards Mirko --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Sending mail to servers that are hosted on the local machine but mx is still pointing to other delivers mail to local machine?!?
Hi, I have a problem from time to time when changing IP-adresses for servers or taking over other domains: I have example.com correctly set up on a mailserver-A as a hosteddomain, this server is working good, no problems and maildelivery for this example.com works well. BUT: MX records for example.com are still pointing to mailserver-B and NOT to mailserver-A. This is still ok, because the take over should take place on a quiet sunday night... NOW if I send mail from any account on mailserver-A to example.com, the mail is NOT delivered to mailserver-B, as this is still set in the actual mx-record for example.com, but the message never leaves mailserver-A and is delivered to the hosted mail account for example.com on mailserver-A. In other words: in such a case, that a domain is setup to be hosteddomained and esmtpacceptedfor on my mailserver-A courier doesn´t seem to be interested in the actual mx record for a domain. In other words: my courier-installation overrides the mx record data with local configuration info. In other words: maybe courier does not even look for the actual mx record, because the target domain is configured to be accepted as a locally hosted domain. I hope, I could describe the situation so that everybody can understand, what I mean... sorry, my english is still not A-Class. Question: Is this a configuration error? If not, is it a hardwired courier behavior to ignore mx records for domains setup to be hosted on the actual server? If this is NOT a configuration error, am I the only one that has problems with this kind of behaviour? How can it be avoided? Thank you very much for your attention, Peter --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88alloc_id065op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Courier 20041103
Download URLs: http://www.courier-mta.org/beta/courier-authlib/courier-authlib-0.50.20041103.tar.bz2 http://www.courier-mta.org/beta/courier/courier-0.47.20041103.tar.bz2 http://www.courier-mta.org/beta/imap/courier-imap-3.0.8.20041103.tar.bz2 http://www.courier-mta.org/beta/sqwebmail/sqwebmail-4.0.7.20041103.tar.bz2 Changes: * LDAP authentication module fixed. * Various fixes to Makefiles. * sqwebmail - fix validation of mail filter regular expressions. pgpdhKevXDgDl.pgp Description: PGP signature
[courier-users] dot-courier unknown mailbox return type
Ive got a default dot-courier script to do some address rewriting so that I can have several domains associated with one user account.#!/bin/sh## Written 24Jan03 by Stephen S Kelley# last modified 24Jan03 SSK## this script delivers mail for addresses that have no specific accountsor aliases# give sysad all mail not matching specific domainsNEWADDR=[EMAIL PROTECTED]case $HOST in # rewrite [EMAIL PROTECTED] to [EMAIL PROTECTED] domain1) NEWADDR=[EMAIL PROTECTED] ;; # rewrite [EMAIL PROTECTED] to [EMAIL PROTECTED] domain2) NEWADDR=[EMAIL PROTECTED] ;; # return mail with mailbox unknown return ??? (what do I return here? Ive tried 64, 65, 67, 68, 69, 70, 76, 77, 78, or 112) ;;esacprintf $NEWADDR\nexit 0 This works fine except for addresses where there is no user account and then the bounce reads: The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator. brahma.virtustate.com #5.0.0 How can I get the bounce to report that the mailbox does not exist on this server? Dr. Stephen S. Kelley, President VirtuState, Inc. [EMAIL PROTECTED] http://www.virtustate.com
RE: [courier-users] Sending mail to servers that are hosted on th e local machine but mx is still pointing to other delivers mail to local machine?!?
From: Peter Holm [mailto:[EMAIL PROTECTED] Hi, I have a problem from time to time when changing IP-adresses for servers or taking over other domains: I have example.com correctly set up on a mailserver-A as a hosteddomain, this server is working good, no problems and maildelivery for this example.com works well. BUT: MX records for example.com are still pointing to mailserver-B and NOT to mailserver-A. This is still ok, because the take over should take place on a quiet sunday night... I'm not sure what take over you are referring to. Exactly what are you trying to accomplish? NOW if I send mail from any account on mailserver-A to example.com, the mail is NOT delivered to mailserver-B, as this is still set in the actual mx-record for example.com, but the message never leaves mailserver-A and is delivered to the hosted mail account for example.com on mailserver-A. In other words: in such a case, that a domain is setup to be hosteddomained and esmtpacceptedfor on my mailserver-A courier doesn´t seem to be interested in the actual mx record for a domain. In other words: my courier-installation overrides the mx record data with local configuration info. In other words: maybe courier does not even look for the actual mx record, because the target domain is configured to be accepted as a locally hosted domain. If the domain is listed in hosteddomains (or locals), mail to that domain is delivered locally. I hope, I could describe the situation so that everybody can understand, what I mean... sorry, my english is still not A-Class. Question: Is this a configuration error? If not, is it a hardwired courier behavior to ignore mx records for domains setup to be hosted on the actual server? Yes, this is expected behavior. If the domain is listed in hosteddomains or locals, Courier will deliver the mail locally and not attempt to relay it further. If this is NOT a configuration error, am I the only one that has problems with this kind of behaviour? How can it be avoided? What you probably want to do is remove the domain from hosteddomains. Courier will accept the mail, since the domain is still in esmtpacceptmailfor, but since the domain isn't in locals or hosteddomains, Courier will then look up the MX records to see where to deliver it. Bowie --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88alloc_id065op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] esmtp authentication
has anyone gotten esmpt authentication to work with mozilla or thunderbird email? I have clients outside the firewall with varying ip's who need to send email, but do not want an open relay! thanks __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] esmtp authentication
chester c young said: has anyone gotten esmpt authentication to work with mozilla or thunderbird email? I have clients outside the firewall with varying ip's who need to send email, but do not want an open relay! thanks Yes, it works perfectly. I configure tb to use port 465 (ESMTP SSL) so that passwords and email are not sent in clear text. It authenticates against the same LDAP backend that IMAP and POP3 do. Are you asking just to ask or are you having specific problems with ESMTP Auth? Jay -- Jay Lee Network / Systems Administrator Information Technology Dept. Philadelphia Biblical University -- --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] esmtp authentication
I do the same thing, but use TLS over esmtpd-msa (587). And I did this for exactly the same reason as the original poster... so that only authenicated (and secure) connections can relay. :-) Jay Lee wrote: chester c young said: has anyone gotten esmpt authentication to work with mozilla or thunderbird email? I have clients outside the firewall with varying ip's who need to send email, but do not want an open relay! Yes, it works perfectly. I configure tb to use port 465 (ESMTP SSL) so that passwords and email are not sent in clear text. It authenticates against the same LDAP backend that IMAP and POP3 do. Are you asking just to ask or are you having specific problems with ESMTP Auth. I do the same thing, but use TLS over esmtpd-msa (587). And I did this for exactly the same reason as the original poster... so that only authenicated (and secure) connections can relay. :-) smime.p7s Description: S/MIME Cryptographic Signature
Re: [courier-users] dot-courier unknown mailbox return type
Stephen S. Kelley writes: This works fine except for addresses where there is no user account and then the bounce reads: The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator. brahma.virtustate.com #5.0.0 There's no such error message in Courier. This is an error message from some other mail server. pgp7fhqD85DGx.pgp Description: PGP signature
[courier-users] Still having issues with 20041103 and LDAP
I still can't get the 20041103 release working with LDAP Authentication. This is all on my test box which I installed 0.47 on, configured it for LDAP Auth identical to my production box and then compiled and installed the 20041103 test release on. /var/maildir and all subfolders are owned by vmail.vmail which is a real user/group on the server as confirmed in /etc/passwd and /etc/group. Here's what maillog says with debug=2: imapd: Connection, ip=[:::127.0.0.1] authdaemond: received auth request, service=imap, authtype=login authdaemond: authldap: trying this module authdaemond: selected ldap protocol version 3 authdaemond: binding to LDAP server as DN 'null', password 'null' authdaemond: using search filter: (uid=it_staff) authdaemond: one entry returned, DN: cn=IT_STAFF,ou=LMC,o=PCB authdaemond: raw ldap entry returned: authdaemond: | uid: IT_STAFF authdaemond: | cn: IT_STAFF authdaemond: authldaplib: sysusername=, sysuserid=501, sysgroupid=501, homedir=/var/maildir/IT_STAFF, address=it_staff, fullname=IT_STAFF, maildir=null, quota=null, options=null authdaemond: authldaplib: clearpasswd=null, passwd=null authdaemond: rebinding with DN 'cn=IT_STAFF,ou=LMC,o=PCB' to validate password authdaemond: authentication bind successful authdaemond: Authenticated: sysusername=, sysuserid=501, sysgroupid=501, homedir=/var/maildir/IT_STAFF, address=it_staff, fullname=IT_STAFF, maildir=null, quota=null, options=null authdaemond: Authenticated: clearpasswd=x, passwd=null imapd: getpwnam: Success Here's what I've got in /etc/authlib/authldaprc: LDAP_SERVER 10.1.1.13 10.1.1.14 LDAP_PORT 389 LDAP_PROTOCOL_VERSION 3 LDAP_BASEDN o=PCB LDAP_TIMEOUT5 LDAP_AUTHBIND 1 LDAP_MAIL uid LDAP_GLOB_UID vmail LDAP_GLOB_GID vmail LDAP_HOMEDIRuid LDAP_MAILROOT /var/maildir LDAP_FULLNAME fullname LDAP_CLEARPWclearPassword LDAP_CRYPTPWuserPassword I realise this is somewhat non-standard but it's worked quite well. Our LDAP server is a Netware 6 machine running eDirectory (NDS). Last but not least, here's what authtest returns: # authtest it_staff Authentication succeeded. Authenticated: it_staff (system username: ) Home Directory: /var/maildir/IT_STAFF Maildir: (none) Quota: (none) Encrypted Password: (none) Cleartext Password: (none) Options: (none) # authtest it_staff x Authentication succeeded. Authenticated: it_staff (system username: ) Home Directory: /var/maildir/IT_STAFF Maildir: (none) Quota: (none) Encrypted Password: (none) Cleartext Password: x Options: (none) Any suggestions? Jay -- Jay Lee Network / Systems Administrator Information Technology Dept. Philadelphia Biblical University -- --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Courier 20041103
I downloaded the new version of courer-authlib, but when I try to run the ./configure --with-mailuser=daemon --with-mailgroup=daemon I get the following error: Cannot obtain information for userid groupid: No such file or directory Is this a bug in the program or is this something wrong on my end? Any ideas? Thank you. Regards, Camilo Rostoker Sam Varshavchik wrote: Download URLs: http://www.courier-mta.org/beta/courier-authlib/courier-authlib-0.50.20041103.tar.bz2 http://www.courier-mta.org/beta/courier/courier-0.47.20041103.tar.bz2 http://www.courier-mta.org/beta/imap/courier-imap-3.0.8.20041103.tar.bz2 http://www.courier-mta.org/beta/sqwebmail/sqwebmail-4.0.7.20041103.tar.bz2 Changes: * LDAP authentication module fixed. * Various fixes to Makefiles. * sqwebmail - fix validation of mail filter regular expressions. -- -- Camilo Rostoker Senior I.T. Consultant Web Developer Scottsdale Developments, Inc. email: [EMAIL PROTECTED] web : www.scottsdale.ca --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] sqwebmail error
I'm using apt-get to intall sqwebmail ( i'm using debian ). So, after installation I just went to http://localhost/cgi-bin/sqwebmail I've got this error message on the page : Internal Error The webmail system is temporarily unavailable. An error occured in function write: Transport endpoint is not connected I'd read the readme doc come from the installation but I have no clue. Googling for this, all I can find is that it's caused by authdaemonrc not running ( hell, my authdaemon is running well -- if not I can't send and recieve e-mails, right ? ) Thanks --me-- = I love Linux but how many years will I wait to have awesome games run on my linux box ??? During that time I will always have dual boot __ Do You Yahoo!? Download the latest ringtones, games, and more! http://sg.mobile.yahoo.com --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] No Berkeley db at all with courier-authlib?
Lloyd Zusman writes: Is it possible when building courier-authlib to not have it do anything at all with Berkeley db? Before this component was split off from courier, all I had to do is configure with --with-db=gdbm, and everything used to build fine. But now, when I configure courier-authlib with --with-db=gdbm, I get errors in the bdb* routines because things like db_open cannot be found. Is there any way to totally prevent any of this bdb* stuff from getting built in the first place in courier-authlib? What part of the build process is having a problem? --with-db=gdbm still works, and will end up building a GDBM-based authlib. The bdbobj directly will still be compiled, if DB is available, but not included in the final link. pgp7kRkD8qVOM.pgp Description: PGP signature
