Re: [courier-users] Maildrop ALWAYS failling with 0x06 - SOLVED

2004-11-24 Thread Hanford, Seth
> On Wednesday 24 November 2004 09:03 am, Hanford, Seth wrote: >> It appears that my g++ version and the libraries are matching (3.3.2 >> and so.32.0), but I've also asked at the OpenBSD sparc list for a bit > > "3.3.2" and "32" do *not* seem like a

Re: [courier-users] Maildrop ALWAYS failling with 0x06

2004-11-24 Thread Hanford, Seth
> This is definitely a mismatch between your C++ compiler, and your C++ > runtime and/or development libraries. This should also explain the memory > corruption. > > I think you mentioned what operating system you're running in the beginning > of the thread, but I forgot. > > Are you using a C++ c

Re: [courier-users] Maildrop ALWAYS failling with 0x06

2004-11-23 Thread Hanford, Seth
- Original Message - From: "Sam Varshavchik" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 23, 2004 7:05 AM Subject: Re: [courier-users] Maildrop ALWAYS failling with 0x06 > Some kind of an internal memory corruption. > > The current version of maildrop is 1.7.0 > >

Re: [courier-users] Maildrop ALWAYS failling with 0x06

2004-11-22 Thread Hanford, Seth
You should rebuild "maildrop" with "-g" so it will have debugging symbols. Rebuilt maildrop-1.5.3.tar.bz2 from source with --enable-DEBUG Program received signal SIGABRT, Aborted. 0x447e1b80 in abort () from /usr/lib/libc.so.34.1 ... and ... and ... ??? At least learn the "bt" command in "

Re: [courier-users] Maildrop ALWAYS failling with 0x06

2004-11-22 Thread Hanford, Seth
Hanford, Seth writes: There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "sparc64-unknown-openbsd3.6"...(no debugging symbols found)... (gdb) run "< testmsg" Try leaving out the quotes. $gdb maildrop GNU gdb

Re: [courier-users] Maildrop ALWAYS failling with 0x06

2004-11-22 Thread Hanford, Seth
When I run this from the command line, the singal 0x06 happens immediately. When I run it in gdb, the process waits the full five minutes, then times out with "Timeout quota exceeded". $maildrop < testmsg maildrop: signal 0x06 $gdb maildrop GNU gdb 6.1 Copyright 2004 Free Software Foundation, Inc.

Re: [courier-users] Maildrop ALWAYS failling with 0x06

2004-11-20 Thread Hanford, Seth
Hanford, Seth writes: > maildrop: signal 0x06 You'll have to look up what's signal 6 on OpenBSD. On Linux it's SIGABRT, which obviously is not what it is on OpenBSD. Once you know what the signal is, then you can try to figure out why you're getting it. Signal 6 is

[courier-users] Maildrop failure

2004-11-19 Thread Hanford, Seth
Is there any known incompatibility between Maildrop-1.5.3 and Sparc64 or other 64-bit architectures? Or OpenBSD 3.6? I have torn the mailing list archives apart and cannot tell why I'm still having this problem: http://marc.theaimsgroup.com/?l=courier-users&m=110087545019920&w=2 Maildrop seems t

Re: [courier-users] Maildrop ALWAYS failling with 0x06

2004-11-19 Thread Hanford, Seth
An off-list reply led me to maildrop -V (level). This is an output of V 4. There seemed to be no more information in V 10, so I added this. Right after the message evaluates (either true or false) it returns 0x06. I don't see why... /home/shanford/Maildir/.System.SpamAlert/cur/$cat 1 | maildrop

[courier-users] Maildrop ALWAYS failling with 0x06

2004-11-19 Thread Hanford, Seth
Please help me find the simple thing I am overlooking. I'm going crazy. No matter what I do, maildrop always returns 0x06. When mail comes to the server, it of course fills the deferred queue, but if I cat a message on the command line and pipe that to maildrop it returns 0x06, the .mailfilter is

[courier-users] Maildrop environment variables

2004-10-01 Thread Hanford, Seth
I'm trying to call maildrop from fetchmail, and I've seen reports that I need to set environment variables to make everything work well. What environment variables does maildrop require to deliver mail successfully? I'm assuming that I will need a properly defined $HOME, but I'm not sure if that

Re: [courier-users] Courier ignoring LDAP_MAILDIR ?

2004-02-23 Thread Hanford, Seth
> mailbox = /home/virtmail/[EMAIL PROTECTED] > > What happens is that Linux users get their mail the way they should, but > mail to virtual users is put into a mailbox file named: > /home/virtmail/[EMAIL PROTECTED]/Maildir This is classic trailing slash misbehaviour. While I'm not _certain_ of th

Re: [courier-users] Re: Amavis/SpamAssassin/Anti-Virus Recommendations/Experiences

2004-02-18 Thread Hanford, Seth
> I'd love to integrate spamassassin via amavis-new as well, but I > haven't had a chance to figure out how amavis-new handles the "I have 2 > recipients with different spam settings" scenario. Anyone else done > this? It might be easy, just haven't tried. Your lucky day... I was just reading this

Re: [courier-users] Maildrop and xfilter losing mail

2003-12-12 Thread Hanford, Seth
cc "|/usr/local/bin/relaydb -w" } } or: if (^X-Spam-Status: YES) { exception{ cc "|/usr/local/bin/relaydb -b" } } else { exception{ cc "|/usr/local/bin/relaydb -w" } } Thanks, Seth - Original Message - From: "Gordon M

[courier-users] Maildrop and xfilter losing mail

2003-12-02 Thread Hanford, Seth
Running Postfix + Courier Maildrop + SpamAssassin. I'm trying to use maildrop in conjunction with relaydb, much like it is described here for Procmail: http://www.benzedrine.cx/relaydb.html I would like to set a global filtering rule in /etc/maildroprc such that all mail tagged as spam is marked