[Mimedefang] order of filter_* routines called
I'm trying to figure out what order the various filter_* routines are called during a session. I can find where filter_begin and filter_end are called but what about the order of the following: filter_relay filter_sender filter_helo (which apparently is going away) filter_recipient Can anyone give me the order in which they are executed? Specifically I have a filter_relay and looks like I need a filter_sender in my environment but need to know how they are evaluated. Would it be best to just combine the code from these procedures into a single procedure? If so which is the best to use? -- Mike Campbell ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] x64 compatible?
I hope I'm not way off here, but are you running with selinux enabled or disabled? -Rich ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] order of filter_* routines called
On Tue, 2006-11-14 at 10:37 -0600, Mike Campbell wrote: I'm trying to figure out what order the various filter_* routines are called during a session. I can find where filter_begin and filter_end are called but what about the order of the following: filter_relay filter_sender filter_helo (which apparently is going away) filter_recipient Can anyone give me the order in which they are executed? Specifically I have a filter_relay and looks like I need a filter_sender in my environment but need to know how they are evaluated. Would it be best to just combine the code from these procedures into a single procedure? If so which is the best to use? In general, you can put all your filter code in filter_end. Depending on your goals and environment, you may want to put code in filter_(relay|sender|recipient). From `man mimedefang-filter` SMTP FLOW This section illustrates the flow of messages through MIMEDefang. 1. INITIAL CONNECTION If you invoked mimedefang with the -r option and have defined a filter_relay routine, it is called. 2. SMTP HELO COMMAND The HELO string is stored internally, but no filter functions are called. 3. SMTP MAIL FROM: COMMAND If you invoked mimedefang with the -s option and have defined a filter_sender routine, it is called. 4. SMTP RCPT TO: COMMAND If you invoked mimedefang with the -t option and have defined a filter_recipient routine, it is called. 5. END OF SMTP DATA filter_begin is called. For each MIME part, filter is called. Then filter_end is called. signature.asc Description: This is a digitally signed message part ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] Re: Help with white listing
Date: Mon, 13 Nov 2006 10:25:32 -0700 From: Ashley M. Kirchner [EMAIL PROTECTED] Subject: [Mimedefang] Help with white listing person who placed the order. The only thing I have to go by is that the messages get relayed through their server. So really I need to white list their relay server and I don't know if that's even possible. HI I think that you can try the following: man Mail::SpamAssassin::Conf Then search for: whitelist_from_rcvd For example (correct me if I'm wrong): whitelist_from_rcvd [EMAIL PROTECTED] mailserver.domain.name Yizhar ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] HOME=/var/spool/MIMEDefang
HI. I have several MD 2.57 installations, which I plan to upgrade to MD 2.58. All installs are on redhat systems (RHEL4, FC4, FC5, FC6). I would like to better understand the exact meaning of the new 2 lines in the suggested /etc/init.d/mimedefang file: HOME=/var/spool/MIMEDefang export HOME I know about the problem with spamassassin on redhat discussed in this group (the errors in /var/log/maillog), and I have also experienced it myself on some of these servers. My bayes and awl databased are stored at: /home/defang/.spamassassin In /etc/mail/sa-mimedefang.cf I have: auto_whitelist_path /home/defang/.spamassassin/auto-whitelist bayes_path /home/defang/.spamassassin/bayes BTW - On most of the servers, /var/spool/MIMEDefang is a ram drive. So my question is - should I use the new suggested /etc/init.d/mimedefang file as is, or change it to: HOME=/home/defang (or /home/defang/.spamassassin) export HOME I simply don't understand what is the exact effect of this settings - is it used for temporary lock files and such, or is it also used for storing SA databases such as bayes and awl? Thanks Yizhar Hurwitz ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] x64 compatible?
--On Monday, November 13, 2006 5:59 AM -0500 [EMAIL PROTECTED] wrote: Core was generated by `mimedefang -U defang -q -p /var/spool/MIMEDefang/mimedefang.sock -d'. Program terminated with signal 11, Segmentation fault. # 0 0x00407806 in ?? () (gdb) At this prompt, type bt to get a stack backtrace which should show the routine where the crash happened. Make sure you built MD with debugging information so that actual routine names will be displayed. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
