Size limiting auto notification for the sender
Hi All! I have followed the steps described in the FAQ about the size limiting of the list and about sending auto notification for the sender. In the FAQ the place of this rule is said to be rc.local.00. The list archive contains the same. I assume it should be rc.local.r00, because if set in rc.local.s00 nothing happens. My problem with this is the following: If I send a mail bigger than the maximum size, then the owner-listaddr gets a message about the size not the sender. I've set the reply_to="Reply-To: owner-$listaddr" in rc.custom to avoid auto replays. In the tmp.from file I can see a foo@bar line after processing. It seems to me that the mail gets processed, the reply_to address is set, and the size check follows only then. The original sender gets no error messages . I might be wrong about this, but there are no other lines in config files or "binaries" which uses owner-listaddr. Any ideas how should I solve this problem? Thanks for your help: Odri Kornel -- Odri Kornél (Netstudio Hungary Kft.-- http://www.netstudio.hu ) Key fingerprint: 8B80 FEFA 3817 2432 A862 3620 C15F AA96 F681 97B2 mailto:korci@netstudio.hu
Zitat von Odri Kornel <korci@netstudio.hu>:
I have followed the steps described in the FAQ about the size limiting of the list and about sending auto notification for the sender. In the FAQ the place of this rule is said to be rc.local.00.
That should be changed to rc.local.s00
The list archive contains the same. I assume it should be rc.local.r00, because if set in rc.local.s00 nothing happens.
rc.local.s00 is the right place. Take care that you uncomment RC_LOCAL_SUBMIT_00 in rc.custom. If you still see nothing put "VERBOSE=ON" on the top of rc.local.s00 and look in the log file what happens.
My problem with this is the following: If I send a mail bigger than the maximum size, then the owner-listaddr gets a message about the size not the sender. I've set the reply_to="Reply-To: owner-$listaddr" in rc.custom to avoid auto replays.
You won't have these problems if you make rc.local.s00 work. -- Werner Reisberger pgp-public-key available: http://www.pure.ch/mypubkey.txt
Hello! Thanks for Your quick response...
That should be changed to rc.local.s00 rc.local.s00 is the right place. Take care that you uncomment RC_LOCAL_SUBMIT_00 in rc.custom. If you still see nothing put "VERBOSE=ON" on the top of rc.local.s00 and look in the log file what happens.
I've tried that already, but without success. Here is what I got this time in an empty letter(I have divertcheck switched to no): X-From_:foo@bar Wed Feb 19 23:28:29 2003 X-Diagnostic: Not on the accept list # Of course foo@bar is not on the From: listman@myhost.com (Smartlist) # the list. But he wasn't the sender To: undisclosed-recipients: ; After that I've got the already well known mail from the list-request to the fake address (which is only mentioned in the reply-to field in rc.custom) Afther this I've tried switching on the divertchek, without pass. That way got only one letter from the list-request to the fake replay adress. Then I switched on pass, and got two mails again the second is the same, but then an emty one with the following lines in the header: X-From_:foo@bar Wed Feb 19 23:45:05 2003 X-Diagnostic: Diverted & unprocessed From: listman@mylist.com (SmartList) To: undisclosed-recipients: ; I think the list can not figure out the sender from the header of the mail, and thats why it sets foo@bar. I have the following lines in rc.local.s00: :0 wfbh * !< $size_limit |formail -rk -I "X-Loop: $listreq" -I "From: $listreq" \ -I "Subject: Sorry, but ... $list max.: $size_limit bytes!" | \ $SENDMAIL -t I forgot to say, but in the mails which were sent by the list-request to the fake are no X-Diagnostic lines. Any suggestions? Now I really want to solve this! :)) Thanks: Odri Kornel
My problem with this is the following: If I send a mail bigger than the maximum size, then the owner-listaddr gets a message about the size not the sender. I've set the reply_to="Reply-To: owner-$listaddr" in rc.custom to avoid auto replays.
You won't have these problems if you make rc.local.s00 work.
-- Werner Reisberger pgp-public-key available: http://www.pure.ch/mypubkey.txt
_______________________________________________ Smartlist mailing list Smartlist@lists.RWTH-Aachen.DE http://MailMan.RWTH-Aachen.DE/mailman/listinfo/smartlist
Zitat von korci@netstudio.hu:
I've tried that already, but without success. Here is what I got this time in an empty letter(I have divertcheck switched to no):
Did you sent an empty letter to trigger a recipe which checks for a size limit?? If you sent a big message (over the size limit in rc.custom) to the list address (not to the request address) rc.local.s00 will be triggered and you will see logging information in the log file of your list. Of course, you also set "VERBOSE=on". Simply saying, I tried this "without success" gives me no clue to give any advice. -- Werner Reisberger pgp-public-key available: http://www.pure.ch/mypubkey.txt
Hello!
Did you sent an empty letter to trigger a recipe which checks for a size limit?? If you sent a big message (over the size limit in rc.custom) to the list address (not to the request address) rc.local.s00 will be triggered and you will see logging information in the log file of your list. Of course, you also set "VERBOSE=on".
I've sent a big message (over the limit in rc.custom) to the list address (not the request address), and this shows up in the log file: procmail: Program failure (67) of " formail -rtzc -xTo: >tmp.from" Sorry if I wasn't precise enough in my previous mails. :) Thanks: Odri Kornel
Zitat von korci@netstudio.hu:
Did you sent an empty letter to trigger a recipe which checks for a size limit?? If you sent a big message (over the size limit in rc.custom) to the list address (not to the request address) rc.local.s00 will be triggered and you will see logging information in the log file of your list. Of course, you also set "VERBOSE=on".
I've sent a big message (over the limit in rc.custom) to the list address (not the request address), and this shows up in the log file: procmail: Program failure (67) of " formail -rtzc -xTo: >tmp.from"
If that's the only line you get you didn't set "VERBOSE=on" and/or you didn't include rc.local.s00 as I suggested earlier. This line is executed far behind rc.local.s00. In a current SmartList-Dist. rc.local.s00 is included in the third line of rc.submit. You failure happened in line 163 and its not possible that this is the only entry if you set VERBOSE on. If you configure SmartList correct you will see that rc.local.s00 will be included and you will see what happened there. As long as you cannot show me this log entries I can only guess. -- Werner Reisberger pgp-public-key available: http://www.pure.ch/mypubkey.txt
On Thu, Feb 20, 2003 at 01:46:38PM +0100, Werner Reisberger wrote:
If that's the only line you get you didn't set "VERBOSE=on" and/or you didn't include rc.local.s00 as I suggested earlier. This line is executed far behind rc.local.s00.
In a current SmartList-Dist. rc.local.s00 is included in the third line of rc.submit. You failure happened in line 163 and its not possible that this is the only entry if you set VERBOSE on. If you configure SmartList correct you will see that rc.local.s00 will be included and you will see what happened there. As long as you cannot show me this log entries I can only guess.
You are right. There is not only one line in the log file, but I'm a bit lost in there. Here I'm sending the log file... Thanks: Odri Kornel
On Thu, Feb 20, 2003 at 03:25:09PM +0100, Odri Kornel wrote:
You are right. There is not only one line in the log file, but I'm a bit lost in there. Here I'm sending the log file...
The example in the FAQ doesn't work the way it should. Change the line :0 wfbh to :0 w and it should work. Pete, can you correct this in the FAQ (also the typo rc.local.00 to rc.local.s00)? Werner
participants (4)
-
korci＠netstudio.hu -
Odri Kornel -
Odri Kornel
-
Werner Reisberger