Skip to Content.
Sympa Menu

en - RE: [sympa-users] Restriction of sending by IP Address

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: "Joe Gilbert" <address@concealed>
  • To: "'Joe Gilbert'" <address@concealed>, "'Adam Bernstein'" <address@concealed>, <address@concealed>
  • Subject: RE: [sympa-users] Restriction of sending by IP Address
  • Date: Fri, 18 Jul 2003 22:32:28 -0700

Ok, I figured this one out myself. I did some more research and
realized that I had bypassed adding the aliases listed in the Robot
Aliases section of the documentation. Now, I am running into a
different issue which is perplexing me. After I send the mail to
distribute the message, the users get a message like this:

An encrypted message from sqex@<host>
has been distributed to
mylist@<host> list subscribers.
Subject : Test


It was not possible to send it to you because the mailing list manager
was unable to access to your personal certificat (email
address@concealed). Please, in order to receive futur crypted messages
send a signed message to sympa@<host>.

This is baffling. I figure if I understood scenarii better, I would
know why this is happening.

Any suggestions?

Joe

-----Original Message-----
From: Joe Gilbert [mailto:address@concealed]
Sent: Friday, July 18, 2003 6:56 PM
To: 'Adam Bernstein'; address@concealed
Subject: RE: [sympa-users] Restriction of sending by IP Address


Thanks, this is doing what I want. I think this will be more than
acceptable for now. The only issue is that the mail to sympa is going
into the sympa mailbox but is not being processed so the modification
does not work. Am I supposed to set up an alias for sympa@<hostname> to
pipe the message to a script or do I need to configure the path to the
mailbox somewhere?

Joe

-----Original Message-----
From: Adam Bernstein [mailto:address@concealed]
Sent: Friday, July 18, 2003 6:06 PM
To: address@concealed
Subject: RE: [sympa-users] Restriction of sending by IP Address


> > When I set it up before, the editor email was sent an email that
> > just stated there was a message to be approved. It gave no
> > indication on how to approve it.
>
> That's strange. I don't know of a config option for this; the
> notifications I

I think that's the result of using "moderated (old style)", aka
"editor", instead of "editorkey" or one of its variants as the send
parameter. I took "moderated/editor" out of my config because someone
had this problem. Use one of the editorkey settings.

FWIW, I also added a line to the moderation email so you can choose to
reject it silently or with a notice -- the modified "moderate.us.tpl"
file follows. And I just realized I have no idea what that [IF
method=md5] is doing there, but it seems to work right...

adam


From: [from]
To: Moderators of list [list->name] <[list->name]-editor@[list->host]>
Subject: Article to be approved for [list->name]
Mime-version: 1.0
Content-Type: multipart/mixed; boundary="[boundary]"

--[boundary]
Content-Type: text/plain
Content-transfer-encoding: 7bit

[IF method=md5]
To distribute the attached message to the list [list->name]:
<mailto:[conf->email]@[conf->host]?subject=DISTRIBUTE%20[list->name]%20[
modkey]>
Or send a message to [conf->email]@[conf->host] with the following
subject: DISTRIBUTE [list->name] [modkey]

To reject it silently (no notication sent to sender):
<mailto:[conf->email]@[conf->host]?subject=QUIET%20REJECT%20[list->name]
%20[modkey]>
Or send a message to [conf->email]@[conf->host] with the following
subject: REJECT [list->name] [modkey]

To reject it and notify sender:
<mailto:[conf->email]@[conf->host]?subject=REJECT%20[list->name]%20[modk
ey]>
Or send a message to [conf->email]@[conf->host] with the following
subject: REJECT [list->name] [modkey] [ENDIF]

--[boundary]
Content-Type: message/rfc822
Content-Transfer-Encoding: 8bit
Content-Disposition: inline

[INCLUDE msg]

--[boundary]--




Archive powered by MHonArc 2.6.19+.

Top of Page