Re: [vchkpw] qmail-tap patch + spamcontrol
qmail-tap patch can be found on http://www.inter7.com/?page=qmailtap New Release version 1.1 Mon Jun 6 13:18:04 CDT 2005 This version allows for setting a different email address for each line in the taps control file. The new syntax is email address to tap:Address to send the copy to. For example: [EMAIL PROTECTED]:[EMAIL PROTECTED] [EMAIL PROTECTED]:[EMAIL PROTECTED] * The qmail tap patch adds additional functionality: Specify which email addresses tap using a regex style control file. With the regex function, you can specify full domains or individual email addresses. * Specify which email address to send the tapped email address. * Qmail does not need to be restarted to change the above. Just update the taps control file. The regex match is applied to both the to and from email addresses. So email sent to or from the addresses will be copied. - Original Message - From: Erwin Hoffmann [EMAIL PROTECTED] To: vchkpw@inter7.com; vchkpw@inter7.com Sent: Friday, July 01, 2005 3:24 AM Subject: Re: [vchkpw] qmail-tap patch + spamcontrol Hi, At 15:56 30.06.2005 +0800, Ronald Chan wrote: Hi everyone, has anyone from you guys know is there a modified qmail-tap patch that can be integrate with spamcontrol found in www.fehcom.de/qmail/spamcontrol.htm i really want to integrate it since spamcontrol patch is a rock solid code for me, My current setup is OpenBSD 3.7 with Qmail-1.0.3 + spamcontrol patch + vpopmail + qmail-scanner. Please tell me more about the qmail-tab patch. What is it ? Where to find ? regards. --eh. Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de/ Wiener Weg 8, 50858 Cologne | T: +49 221 484 4923 | F: ...24
Re: [vchkpw] qmail-tap patch + spamcontrol
On Thursday 30 June 2005 06:14 pm, Brian Lanier wrote: My understanding was that the when addressed to someone on the BCC line it simply existed as roughly [EMAIL PROTECTED] I thought each message only had one envelope recipient so that to have the message go to multiple parties you got multiple messages in the queue each with a different envelope recipient. no, qmail stores multi-recipient messages in the queue as one message, with multiple recipients. Am I way off on my understanding here? If so, is there an environment variable that stores the BCC field or are we saying the same thing only different. no, there is no way to get the entire contents of the envelope in a .qmail file. This would pose a privacy issue. Say I sent bob an email and BCC'ed it to Jane. There is no evidence in my email that jane received it, but if the entire envelope information was available in an environment variable, or some other fashion, to all local recipients, then the BCC recipients could be leaked. The only recipient you will get with [EMAIL PROTECTED] in a .qmail file is the recipient that is currently being delivered to. Currently I am migrating my logging down into my maildrop file to catch the envelope recipients due to fact that queue_extra changes what I know as the envelope recipient to log, which is set up as a an alias that runs maildrop with a special filter file. If I can do it all at once and at the queue level that would be great. My method doesn't seem to be the most efficient yet it does work. maildrop still will not have information about the *entire* contents of the envelope. -Jeremy -- Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc. [EMAIL PROTECTED] ++ inter7.com ++ 866.528.3530 ++ 815.776.9465 int'l kitchen @ #qmail #gentoo on EFnet IRC ++ scriptkitchen.com/qmail GnuPG Key ID: 481BF7E2 ++ qmail wiki @ qmailwiki.org !! pgpbJauBTFSLU.pgp Description: PGP signature
RE: [vchkpw] qmail-tap patch + spamcontrol
-Original Message- From: Jeremy Kitchen [mailto:[EMAIL PROTECTED] Sent: Friday, July 01, 2005 9:40 AM To: vchkpw@inter7.com Subject: Re: [vchkpw] qmail-tap patch + spamcontrol On Thursday 30 June 2005 06:14 pm, Brian Lanier wrote: My understanding was that the when addressed to someone on the BCC line it simply existed as roughly [EMAIL PROTECTED] I thought each message only had one envelope recipient so that to have the message go to multiple parties you got multiple messages in the queue each with a different envelope recipient. no, qmail stores multi-recipient messages in the queue as one message, with multiple recipients. Everyday I learn more about how much I don't know... Its great. :-) Am I way off on my understanding here? If so, is there an environment variable that stores the BCC field or are we saying the same thing only different. no, there is no way to get the entire contents of the envelope in a .qmail file. This would pose a privacy issue. Say I sent bob an email and BCC'ed it to Jane. There is no evidence in my email that jane received it, but if the entire envelope information was available in an environment variable, or some other fashion, to all local recipients, then the BCC recipients could be leaked. Which was how I knew it to work, I just didn't understand where or how. The only recipient you will get with [EMAIL PROTECTED] in a .qmail file is the recipient that is currently being delivered to. Currently I am migrating my logging down into my maildrop file to catch the envelope recipients due to fact that queue_extra changes what I know as the envelope recipient to log, which is set up as a an alias that runs maildrop with a special filter file. If I can do it all at once and at the queue level that would be great. My method doesn't seem to be the most efficient yet it does work. maildrop still will not have information about the *entire* contents of the envelope. Correct, which is why I have to worry about caching message id's to prevent duplicate deliveries of messages due to the fact that I am checking the same message multiple times. I went back and read a bunch of the qmail man pages just now. Amazing how differently I understand qmail now. Thanks for your patience and helping me out on this. I think I get it now. The tap patch does the checking at the queue level and only t's off a copy when needed. That's great and really cuts down on my efficiency. Next question based on functionality. I thought I read somewhere that as soon as qmail-tap finds a match it stops processing. Is that per domain or for the whole list? I want to assume that its per domain, i.e. as soon as it finds a match for one line in the control file, it stops logging for that entry but continues checking the rest of the list for other matches and possible deliveries. Is that the case? The only thing I have left is maybe a feature request. If I knew enough C to submit a patch I would. Is it possible to set up different delivery addresses for the archive user based on direction? Inbound messages could be logged to a separate user from the outbound. Kind of like the distinction for the mysql setup in vpopmail. If only one line exists it is used for both read and write, otherwise use one for read and the second line for write. Something like: [EMAIL PROTECTED]:[EMAIL PROTECTED]:[EMAIL PROTECTED] Where the format was item_to_log:if_to_matches_deliver_here:if_from_matches_deliver_here and done in such a way so that if the third field didn't exist it used the second field to provide backwards compatibility or for those that only want one final deliver. I believe the side effect of this would be two copies for each line in the control file if it hit the regex in both the to and from addresses, which is desirable by me but I am only one fish in the big pond... My concern is that if I have multiple domains using logging sending to each other, they all get the appropriate messages logged accordingly. Some of our clients have also requested the split of direction to more easily track down something. So far, all the attention into all the products mentioned and used by this list have not let me down, but I still need to ask. Any thoughts on any of this Is it time to go learn C and start breaking things? :-)
[vchkpw] qmail-tap patch + spamcontrol
Hi everyone, has anyone from you guys know is there a modified qmail-tap patch that can be integrate with spamcontrol found in www.fehcom.de/qmail/spamcontrol.htm i really want to integrate it since spamcontrol patch is a rock solid code for me, My current setup is OpenBSD 3.7 with Qmail-1.0.3 + spamcontrol patch + vpopmail + qmail-scanner. Thanks in advance God Bless Ronald Chan
Re: [vchkpw] qmail-tap patch + spamcontrol
Hi, At 15:56 30.06.2005 +0800, Ronald Chan wrote: Hi everyone, has anyone from you guys know is there a modified qmail-tap patch that can be integrate with spamcontrol found in www.fehcom.de/qmail/spamcontrol.htm i really want to integrate it since spamcontrol patch is a rock solid code for me, My current setup is OpenBSD 3.7 with Qmail-1.0.3 + spamcontrol patch + vpopmail + qmail-scanner. Please tell me more about the qmail-tab patch. What is it ? Where to find ? regards. --eh. Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de/ Wiener Weg 8, 50858 Cologne | T: +49 221 484 4923 | F: ...24
Re: [vchkpw] qmail-tap patch + spamcontrol
On Thursday 30 June 2005 2:24 pm, Erwin Hoffmann wrote: Hi, At 15:56 30.06.2005 +0800, Ronald Chan wrote: Hi everyone, has anyone from you guys know is there a modified qmail-tap patch that can be integrate with spamcontrol found in www.fehcom.de/qmail/spamcontrol.htm i really want to integrate it since spamcontrol patch is a rock solid code for me, My current setup is OpenBSD 3.7 with Qmail-1.0.3 + spamcontrol patch + vpopmail + qmail-scanner. Please tell me more about the qmail-tab patch. What is it ? Where to find http://www.inter7.com/?page=qmailtap It gives you greater control than stock qmail in archiving email messages. Ken Jones
RE: [vchkpw] qmail-tap patch + spamcontrol
-Original Message- From: Ken Jones [mailto:[EMAIL PROTECTED] Sent: Thursday, June 30, 2005 2:39 PM To: vchkpw@inter7.com Subject: Re: [vchkpw] qmail-tap patch + spamcontrol On Thursday 30 June 2005 2:24 pm, Erwin Hoffmann wrote: Hi, At 15:56 30.06.2005 +0800, Ronald Chan wrote: Hi everyone, has anyone from you guys know is there a modified qmail-tap patch that can be integrate with spamcontrol found in www.fehcom.de/qmail/spamcontrol.htm i really want to integrate it since spamcontrol patch is a rock solid code for me, My current setup is OpenBSD 3.7 with Qmail-1.0.3 + spamcontrol patch + vpopmail + qmail-scanner. Please tell me more about the qmail-tab patch. What is it ? Where to find http://www.inter7.com/?page=qmailtap It gives you greater control than stock qmail in archiving email messages. Ken Jones How do you handle BCC entries using qmail-tap? My C is limited to very basic understanding, so I see it runs some regex checks but against what? In the past when using the QUEUE_EXTRA code, I noticed I lost the envelope recipient as a variable for use($EXT and $HOST). It got changed to whatever I set up under QUEUE_EXTRA. Because of that I couldn't grab BCC emails. $SENDER was still set just fine. Thanks Brian
Re: [vchkpw] qmail-tap patch + spamcontrol
On Thursday 30 June 2005 05:50 pm, Brian Lanier wrote: -Original Message- From: Ken Jones [mailto:[EMAIL PROTECTED] Sent: Thursday, June 30, 2005 2:39 PM To: vchkpw@inter7.com Subject: Re: [vchkpw] qmail-tap patch + spamcontrol On Thursday 30 June 2005 2:24 pm, Erwin Hoffmann wrote: Hi, At 15:56 30.06.2005 +0800, Ronald Chan wrote: Hi everyone, has anyone from you guys know is there a modified qmail-tap patch that can be integrate with spamcontrol found in www.fehcom.de/qmail/spamcontrol.htm i really want to integrate it since spamcontrol patch is a rock solid code for me, My current setup is OpenBSD 3.7 with Qmail-1.0.3 + spamcontrol patch + vpopmail + qmail-scanner. Please tell me more about the qmail-tab patch. What is it ? Where to find http://www.inter7.com/?page=qmailtap It gives you greater control than stock qmail in archiving email messages. Ken Jones How do you handle BCC entries using qmail-tap? My C is limited to very basic understanding, so I see it runs some regex checks but against what? BCC is just an extra envelope recipient that isn't in the headers. qmail-tap uses the envelope information, and ignores headers. In the past when using the QUEUE_EXTRA code, I noticed I lost the envelope recipient as a variable for use($EXT and $HOST). It got changed to whatever I set up under QUEUE_EXTRA. Because of that I couldn't grab BCC emails. $SENDER was still set just fine. that will occur here as well, because this is basically an extension to the QUEUE_EXTRA code, and just adds a recipient to queued messages. -Jeremy -- Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc. [EMAIL PROTECTED] ++ inter7.com ++ 866.528.3530 ++ 815.776.9465 int'l kitchen @ #qmail #gentoo on EFnet IRC ++ scriptkitchen.com/qmail GnuPG Key ID: 481BF7E2 ++ qmail wiki @ qmailwiki.org !! pgpWUoD8zI8T5.pgp Description: PGP signature
RE: [vchkpw] qmail-tap patch + spamcontrol
-Original Message- From: Jeremy Kitchen [mailto:[EMAIL PROTECTED] Sent: Thursday, June 30, 2005 3:59 PM To: vchkpw@inter7.com Subject: Re: [vchkpw] qmail-tap patch + spamcontrol --- snip --- How do you handle BCC entries using qmail-tap? My C is limited to very basic understanding, so I see it runs some regex checks but against what? BCC is just an extra envelope recipient that isn't in the headers. qmail-tap uses the envelope information, and ignores headers. Ok... I had that part about BCC only existing in the envelope... In the past when using the QUEUE_EXTRA code, I noticed I lost the envelope recipient as a variable for use($EXT and $HOST). It got changed to whatever I set up under QUEUE_EXTRA. Because of that I couldn't grab BCC emails. $SENDER was still set just fine. that will occur here as well, because this is basically an extension to the QUEUE_EXTRA code, and just adds a recipient to queued messages. -Jeremy My understanding was that the when addressed to someone on the BCC line it simply existed as roughly [EMAIL PROTECTED] I thought each message only had one envelope recipient so that to have the message go to multiple parties you got multiple messages in the queue each with a different envelope recipient. Am I way off on my understanding here? If so, is there an environment variable that stores the BCC field or are we saying the same thing only different. Currently I am migrating my logging down into my maildrop file to catch the envelope recipients due to fact that queue_extra changes what I know as the envelope recipient to log, which is set up as a an alias that runs maildrop with a special filter file. If I can do it all at once and at the queue level that would be great. My method doesn't seem to be the most efficient yet it does work. I think I am missing a piece here and I don't even know what to ask about... I hope this makes enough sense... Brian
