FYI - This does not appear to be the case. Program aliases to not appear to be able to execute rules. This is because they are aliases, not users.
-Chase
Chase Seibert | Network and Systems Engineer | Bullhorn Inc | 617.464.2440 x119 | www.bullhorn.com
-----Original Message-----
From:Darin Cox [EMAIL PROTECTED]
To: "Declude.JunkMail@declude.com";
Sent: Jun 23, 2005 03:44:13 PM
Subject: Re: [Declude.JunkMail] custom delivery executable?
From:Darin Cox [EMAIL PROTECTED]
To: "Declude.JunkMail@declude.com"
Sent: Jun 23, 2005 03:44:13 PM
Subject: Re: [Declude.JunkMail] custom delivery executable?
?
The program alias would not be fired until local mailbox delivery occurs, so that would be after all IMail and Declude processing.
Can't speak to imail1.exe replacement, though it sounds a little risky to me.
Darin.
----- Original Message -----
From: Chase Seibert
Sent: Thursday, June 23, 2005 1:25 PM
Subject: RE: [Declude.JunkMail] custom delivery executable?
Both of your suggestions have merit. Will a program alias execute after iMail has run the message through it's rules? If rules result in the message going to a particular folder, how would that information be preserved in the hand-off to the executable?
As for imail1.exe, does anyone know the extent of what that executable does in the stock iMail install? Are rules processed before, after or inside this executable?
-Chase
Chase Seibert | Network and Systems Engineer | Bullhorn Inc | 617.464.2440 x119 | www.bullhorn.com
-----Original Message-----
From: [EMAIL PROTECTED]
To: "Declude.JunkMail@declude.com";
Sent: Jun 23, 2005 11:47:35 AM
Subject: Re: [Declude.JunkMail] custom delivery executable?
From: [EMAIL PROTECTED]
To: "Declude.JunkMail@declude.com"
Sent: Jun 23, 2005 11:47:35 AM
Subject: Re: [Declude.JunkMail] custom delivery executable?
Or another thought to try is renaming your custom delivery app to imail1.exe
and replacing theirs Althought I am not sure what else this would break.
Darrell
------------------------------------------------------------------------
Check out http://www.invariantsystems.com for utilities for Declude And
Imail. IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG
Integration, and Log Parsers.
Darin Cox writes:
> You could change all email addresses to be program aliases. The batch file run by the program alias could then dump the message into a text file, or even post the message straight into your database.
>
> Darin.
>
>
> ----- Original Message -----
> From: Chase Seibert
> To: Declude.JunkMail@declude.com
> Sent: Thursday, June 23, 2005 9:53 AM
> Subject: [Declude.JunkMail] custom delivery executable?
>
>
> Hey guys,
>
> We have a very non-standard iMail/Declude install. Basically, we only us the system for the SMTP protocol, as well as virus and spam filtering. Once a message has passed through those systems, it's delivered to a mailbox as normal. However, we don't allow POP or IMAP access to our systems. Instead, we parse the mailboxes when they change, pull out new mail and insert it into a SQL Server database for access in our web-based CRM. Messed up, huh?
>
> We are looking to skip the whole step of delivering the mail to a mailbox and then chunking it out. It's not a speed problem, but rather a reliability concern. Our current solution has about a .1% failure rate, meaning that some messages are not delivered until the next message comes along into that folder to knock it out.
>
> Ok, here is my question. I am wondering if there is some way to setup iMail/Declude so that it delivers a message right to a stand alone file, as apposed to a mailbox Qmail, for example, can do this. I doubt there is any out of the box support for this, so I started investigating using a custom Declude filter for this.
>
>>From the manual:
>> For more flexibility, you can have Declude JunkMail pass parameters to your program, using variables. For example, you can set up the test as 'TESTNAME external returnvalue "filename %INOROUT%"', which would send the %INOROUT% variable as a parameter to your program (which would be "incoming" for an incoming E-mail, or "outgoing" for an outgoing E-mail).
>
> Presumably, we could write a custom executable and define a rule for it in Junkmail. The custom executable would get the entire message body and just pipe it to a stand-alone file. If the message was later also delivered to an iMail mailbox, that's fine.
>
> However, I think the issue with that idea is that the filters will not have executed when that custom executable is called Accoring to the Declude manaul, the order of execution is:
>
> 1. IMail's Control Access file (to block IPs)
> 2. IMail's Kill List (to block return addresses)
> 3. IMail v8 anti-spam (most tests)
> 4. Declude Virus
> 5. Declude Hijack
> 6. Declude JunkMail
> 7. IMail's filters and extra IMail v8 anti-spam tests
> *we want to insert a custom exectuable here
>
> Is this even possible, or should I just start looking as Linux mail systems?
>
>
> -Chase
> Chase Seibert | Network and Systems Engineer | Bullhorn Inc | 617.464.2440 x119 | www.bullhorn.com
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
