The mailing list for listmasters using Sympa

[David Verdin <address@concealed>]

Hi Pat and sorry for this late answer. It looks like everybody in the list is very busy these days. ;-)

To understand what happens, you could launch sympa in debug mode (/home/sympa/bin/sympa.pl -d) and see what messages are issued when you try to send a message to private list.
You SHOULD see this kind of output:

notice main::DoMessage() Message for test-stable from address@concealed rejected() because sender not allowed

debug2 report::reject_report_msg() reject::reject_report_msg(auth,send_closed,address@concealed)

debug2 List::send_file() List::send_file(message_report, address@concealed, dev-sympa.cru.fr)

debug2 List::get_user_db() List::get_user_db(address@concealed)

debug2 tools::decrypt_password() tools::decrypt_password (73cb6b72256e44942c7f57fbd3faf257)

debug2 List::get_subscriber() List::get_subscriber(address@concealed)

debug2 List::get_subscriber_no_object() List::get_subscriber_no_object(test-stable, address@concealed, dev-sympa.cru.fr)

debug2 List::get_subscriber_no_object() custom_attribute  = (<?xml version="1.0" encoding="UTF-8" ?><custom_attributes></custom_attributes>)

debug2 List::get_subscriber_no_object() 1. custom_attribute  = (<?xml version="1.0" encoding="UTF-8" ?><custom_attributes></custom_attributes>)

debug2 List::get_subscriber_no_object() 2. custom_attribute  = ()

debug2 List::get_subscriber_no_object() 3. custom_attribute  = (HASH)

debug2 List::get_subscriber_no_object() keys custom_attribute  = 

debug2 List::get_first_admin_user() List::get_first_admin_user(test-stable,owner,domain,0,0)

debug Lock::new() Lock::new(/usr/local/sympa-stable/expl/test-stable/include_admin_user)

debug Lock::lock() Trying to put a lock on /usr/local/sympa-stable/expl/test-stable/include_admin_user.lock in mode read

debug2 List::get_first_admin_user() SQL: SELECT user_admin AS email, comment_admin AS gecos, reception_admin AS reception, visibility_admin AS visibility, UNIX_TIMESTAMP(date_admin) AS "date", UNIX_TIMESTAMP(update_admin) AS update_date, info_admin AS info, profile_admin AS profile, subscribed_admin AS subscribed, included_admin AS included, include_sources_admin AS id, REVERSE(SUBSTRING(user_admin FROM position('@' IN user_admin) FOR 50)) AS "dom" FROM admin_table WHERE (list_admin = 'test-stable' AND robot_admin = 'dev-sympa.cru.fr' AND role_admin = 'owner' ) ORDER BY "dom"

debug2 List::get_next_admin_user() List::get_next_admin_user

debug Lock::new() Lock::new(/usr/local/sympa-stable/expl/test-stable/include_admin_user)

debug Lock::unlock() Removing lock on /usr/local/sympa-stable/expl/test-stable/include_admin_user.lock

debug2 mail::mail_file() mail::mail_file(/usr/local/sympa-stable/default/mail_tt2/message_report.tt2, address@concealed, )

debug Language::PushLang() Language::PushLang(en_US)

debug2 Language::SetLang() Language::SetLang(en_US)

debug Language::PopLang() 

debug2 Language::SetLang() Language::SetLang(en_US)

debug Language::PushLang() Language::PushLang(en_US)

debug2 Language::SetLang() Language::SetLang(en_US)

debug2 Language::SetLang() Language::SetLang(en_US)

debug Language::PopLang() 

debug2 Language::SetLang() Language::SetLang(en_US)

debug Bulk::store() Bulk::store(<msg>,<rcpts>,from = address@concealed,robot = dev-sympa.cru.fr,listname= test-stable,priority_message = 1, delivery_date= 1339762272,verp = 0, merge = 0, dkim: d=  i=, last: )

notice Moving bad file address@concealed to bad/

If not, the means that Sympa has a problem. Please send us the debug logs and we'll probably understand you problem.

Also, you could check whetehr there is not an implicitly included scenario somewere on your server (https://www.sympa.org/manual/authorization-scenarios#scenario_inclusion). It could contain a rule that would have precedence on any other rule.

Regards,

David

Le 03/06/12 15:18, Pat Allen a écrit : Hi everyone,

I've not heard anything back on this since David's initial post on May 15. This is really a bother. Can somebody possibly explain why a NDR isn't being generated when a non-subscriber sends to a private list?

Thanks!
Pat

---

From: "Pat Allen" <address@concealed>
To: "sympa-users" <address@concealed>
Sent: Wednesday, May 23, 2012 7:11:47 AM
Subject: Re: [sympa-users] Rejected mail not sending NDR?

Hi David,

Sorry it took me so long to get back to you. I was on holiday.

The complete ~sympa/bin/scenari/send.private scenari is:

title.gettext restricted to subscribers

is_subscriber([listname],[sender])             smtp,smime,md5    -> do_it
is_editor([listname],[sender])                 smtp,smime,md5    -> do_it
is_owner([listname],[sender])                  smtp,smime,md5    -> do_it
true()                                         smtp,md5,smime  -> reject(reason='send_subscriber')

Thanks for the help.
Pat

---

From: "David Verdin" <address@concealed>
To: "Pat Allen" <address@concealed>
Cc: address@concealed
Sent: Tuesday, May 15, 2012 3:25:03 AM
Subject: Re: [sympa-users] Rejected mail not sending NDR?

Hi Pat,

I can't see the end of the last rule in your scenario (after the "true()" condition). Is it "smtp,smime,md5    ->   reject" ?


David
Le 14/05/12 18:37, Pat Allen a écrit :

Hi David,

Thanks for the quick response. I haven't customized these particular scenario. Here's what the send.private scenari looks like:

title.gettext restricted to subscribers

is_subscriber([listname],[sender])             smtp,smime,md5    -> do_it
is_editor([listname],[sender])                 smtp,smime,md5    -> do_it
is_owner([listname],[sender])                  smtp,smime,md5    -> do_it
true()

Just to do a sanity check I grep'd for "quiet" in /bin/etc/scenari and etc/scenari and it was only referenced in subscribe.open_quiet.

Pat

---

From: "David Verdin" <address@concealed>
To: address@concealed
Sent: Monday, May 14, 2012 8:28:55 AM
Subject: Re: [sympa-users] Rejected mail not sending NDR?

Hi Pat,

What "send" scenario do you use for these lists? Is the "rejct" option is followed by "quiet", then the message is silently dismissed. remove the "quiet" to notify the user that her message was rejected.

Regards,

David

Le 14/05/12 16:33, Pat Allen a écrit :

Good morning,

I'm currently running Sympa 6.1.3.  Some users have reported that they do not receive NDR messages when sending to lists which are restricted. There is no notification to the user that the message is rejected. They assume that the mail was delivered successfully. I was surprised because I thought this used to work.

I configured a test list to accept mail only from subscribers and attempted to send a message to it. The sympa.log shows that it is being rejected:
May 14 07:09:11 xxxxxx sympa[19936]: notice main::DoFile() Processing /home/sympa/spool/msg/test@xxxxxx.mbari.org.1337004546.24320 ; sender: Pat Allen <address@concealed>  ; message-id: <address@concealed>
May 14 07:09:11 xxxxxx sympa[19936]: info main::DoMessage() Processing message for test with priority 5, <address@concealed>
May 14 07:09:11 xxxxxx sympa[19936]: notice main::DoMessage() Message for test from address@concealed rejected() because sender not allowed
May 14 07:09:11 xxxxxx sympa[19936]: notice Moving bad file test@xxxxxx.mbari.org.1337004546.24320 to bad/

The maillog simply shows the message arriving but no outgoing NDR:
May 14 07:09:06 xxxxxx sendmail[24318]: q4EE96dP024318: from=<address@concealed>, size=1808, class=0, nrcpts=1, msgid=<address@concealed>, bodytype=7BIT, proto=ESMTP, daemon=MTA, relay=asdf.shore.mbari.org [134.89.12.31]
May 14 07:09:07 xxxxxx sendmail[24319]: q4EE96dP024318: to="| /home/sympa/bin/queue test@xxxxxx.mbari.org", ctladdr=<test@xxxxxx.mbari.org> (8/0), delay=00:00:01, xdelay=00:00:01, mailer=prog, pri=32020, dsn=2.0.0, stat=Sent

Is there a bug which has been introduced or fixed between 6.1.3 and 6.1.11? I couldn't find anything in the archives.

Thanks,
Pat

---

Pat Allen (address@concealed & http://www.mbari.org/staff/pat)
Monterey Bay Aquarium Research Institute (MBARI)
7700 Sandholdt Rd, Moss Landing, CA 95039
(voice) 831-775-1724; (fax) 831-775-1620

Attachment: smime.p7s
Description: Signature cryptographique S/MIME