Re: [Mailman-Users] posting restrictions still confusing to me (or not
About posting that are held for approval even thought they seem to be coming from a list member when member_posting_only is set to true...
Here's what I'm seeing. I put the following in Mailman/MailList.py inside the Post() method:
sys.stderr.write('envsend: %s, sender: %s\n' %
(msg.GetEnvelopeSender(), msg.GetSender()))
This will write the envelope sender and `header' sender to logs/error, which you can tail as you send messages to the list. For me, envelope sender is always None, so the test falls through to msg.GetSender(), which is taken from my spoofable From: header.
Back in November, Scott added the use of GetEnvelopeSender() before GetSender() because he'd been hit by a spam getting through that should have been held for approval, but IIRC, Scott's also been backing away from using the envelope sender in some situations. Maybe Scott is able to elaborate.
rfc822.py gets the envelope sender as the unixfrom attribute on the message object. This it gets from the "From " line in the message. I don't understand why you're getting something different from me (I'm using sendmail 8.9.something).
Anyway, here's what I propose. I'll add a variable to Defaults.py/mm_cfg.py called, say APPROVE_WITH_ENVELOPE_SENDER which will be set to true by default. You set it to false and Mailman will only use the sender. I'll add info to the FAQ and such explaining that this is easier to spoof, but may work around problems where the envelope sender isn't getting set correctly.
If anybody can debug this further, I'd appreciate it.
-Barry
Hello,
This is the error crontab message I got. Would someone help me out? Mailman was running very in past one month. Suddently I just got this message. I am running beta 9.
Subject: Cron <mailman@academy> /usr/bin/python /usr/local/mailman/cron/run_queue X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/usr/local/mailman> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=mailman> :
shell-init: could not get current directory:
Alex
Hello,
Actually I tried to su as mailman, I got the following bad message.
[/usr/local] # su - mailman shell-init: could not get current directory: job-working-directory: could not get current directory: job-working-directory: could not get current directory: job-working-directory: could not get current directory: job-working-directory: could not get current directory: job-working-directory: could not get current directory:
Any1 knows how to fix it?
Alex
Check the permissions on ~mailman. Did they get messed up some how?
At 05:06 PM 1999/3/9 -0500, Alex Yu wrote:
Actually I tried to su as mailman, I got the following bad message. [/usr/local] # su - mailman
Sorry, I just fixed the problem. I found out that you can't have umkas 711 on /usr/bin, /usr/sbin, /usr/local/bin and /usr/local/sbin. Thanks.
Alex
participants (2)
-
Alex Yu
-
Barry A. Warsaw