headers
FLASSE Damien | 14 Jul 2011 14:02
Favicon

Cannot authenticate on GUI after move and upgrade to a new server

Dear,

 

I’ve upgraded sympa from 5.4.3 to 6.15 on another server (Ubuntu 10.04) following this procedure: http://www.sympa.org/manual/upgrading

 

Everything went fine (no error during the upgrade process) but I cannot authenticate on the web GUI. In the log, I’ve the following error message:

 

Jul 14 10:23:45 oracle2 wwsympa[11032]: err Auth::authentication() authentication: incorrect password for user

 

It goes for all users I’ve tested.

 

Any attempt to reset the password (lost password procedure) looks ok on screen (check you inbox it says) but nothing happens. I trust email config is ok because I receive warnings from sympa when I restart the daemon.

 

I compared the password hash from the users in user_table and they are identical both on the new and the old server. The ‘old’ server runs perfectly well.

 

I don’t know what else I could do. Any help would be greatly appreciated.

 

Damien

Permalink | Reply | 1 comment |
headers
Giuseppe Giacomini | 14 Jul 2011 14:47
Picon

strange problem after upgradin to 6.1.5

Good morning,

we use sympa as university mailing list server, last day I have upgraded or 6.1.2  version of sympa to 6.1.5
and I notice this problem:

when a user subscribe or unsubscribe a mailing list it receive the corresponding welcome.tt2 o removed.tt2 message
but it is empty. (only Subject is present).

Tracing the activity I found the message become empty after the execution of function
 $msg = &fix_part($msg, $parser, $attachments, $defcharset);
in mail.pm

Before this call if I print  the content of $msg->as_string
I get the full message ie
To: gigiacom-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Auto-Submitted: auto-generated From: prova1-request-JX7+OpRa80TznsXVEfjgbl6hYfS7NtTn@public.gmane.org Subject: Removed from prova1  Your address (gigiacom-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org) has been removed from list prova1-JX7+OpRa80TznsXVEfjgbl6hYfS7NtTn@public.gmane.org, likely due to excessive non-delivery reports for your address.  You can subscribe again: mailto:sympa-JX7+OpRa80TznsXVEfjgbl6hYfS7NtTn@public.gmane.org?subject=sub%20prova1

If I print the same message after  fix_part I get this content of $msg->as_string

To: gigiacom-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7BIT Auto-Submitted: auto-generated From: prova1-request-JX7+OpRa80TznsXVEfjgbl6hYfS7NtTn@public.gmane.org Subject: Removed from prova1 Content-length: 0 X-Mailer: Sympa 6.1.5


Could it be a misconfiguration?

thank you
-- Giuseppe Giacomini Universita' Ca' Foscari Venezia Centro Servizi Informatici e di Telecomunicazioni di Ateneo gigiacom-Vg7Evjp7JRQ@public.gmane.org +39 041 234 7118
Permalink | Reply | 0 comments |
headers
Adam Bernstein | 14 Jul 2011 23:37

expanding the SOAP interface -- contract help?

We're experiencing a new wave of interest from clients in using an API 
to connect to Sympa from other applications, so we're looking more and 
more at the SOAP server.  And it seems like each new client has one new 
specific need that the SOAP API doesn't meet, which isn't very 
surprising since the number of functions in the SOAP interface is fairly 
limited.  We have been able to hack up one or two new SOAP functions on 
our own, already submitted to Sympa for future inclusion, but more 
complicated requirements are beyond our capabilities.

So we're looking for help.  One source would be the Sympa team: would it 
be possible for us to sponsor some focused work on the SOAP interface, 
to benefit all users and Sympa's global appeal as well as our own 
clients?  There is money available, although I know that with Sympa 
development happening in a higher education environment, there may be 
practical challenges in arranging for such sponsorship.  David, Olivier, 
and Serge, please let me know.

Another source would be other experienced Sympa implementers and hackers 
on this list.  If any of you are interested in a short-term and 
well-defined contract job to work on the Sympa SOAP interface (or at 
least an EE version of it), please get in touch.  Specifically, our 
immediate need involves adding the ability to view and change list 
configuration settings (including moderators), and possibly perform 
message moderation, via SOAP.

Thanks for reading!

     adam
     worker-owner, electric embers cooperative inc.
Permalink | Reply | 0 comments |
headers
David Verdin | 15 Jul 2011 09:56
Picon

Re: Cannot authenticate on GUI after move and upgrade to a new server

Hi Damien,

Your passwords should actually have changed. Passwords are now stored as fingerprints.
So the question is: did you run the "sympa.pl --md5_encode_password" command? Normally, you should have been reminded to do it when completing the "make install". If not, then it is abnormal.

Before doing so, please note the this operation is not reversible, so backup your database before.

Regards,

David

Le 14/07/11 14:02, FLASSE Damien a écrit :

Dear,

 

I’ve upgraded sympa from 5.4.3 to 6.15 on another server (Ubuntu 10.04) following this procedure: http://www.sympa.org/manual/upgrading

 

Everything went fine (no error during the upgrade process) but I cannot authenticate on the web GUI. In the log, I’ve the following error message:

 

Jul 14 10:23:45 oracle2 wwsympa[11032]: err Auth::authentication() authentication: incorrect password for user

 

It goes for all users I’ve tested.

 

Any attempt to reset the password (lost password procedure) looks ok on screen (check you inbox it says) but nothing happens. I trust email config is ok because I receive warnings from sympa when I restart the daemon.

 

I compared the password hash from the users in user_table and they are identical both on the new and the old server. The ‘old’ server runs perfectly well.

 

I don’t know what else I could do. Any help would be greatly appreciated.

 

Damien


--
David Verdin
Comité réseau des universités

Due to the limitations of human brain, I fail to remember all the mails.
So if you want your bug reports or feature requests for Sympa to be processed, please post them to the Sympa tracker
Attachment (smime.p7s): application/pkcs7-signature, 5589 bytes
Permalink | Reply | 0 comments |
headers
Steffen Gebert | 16 Jul 2011 14:17
Picon
Gravatar

Multiple "Re:" headers

Dear sympa users,

we have a sympa list server running and a few users complain about subjects like
> Re: Re: AW: Re: Re: foo bar

Is there a way that sympa automatically removes (at least) the Re: prefixes of such subjects?

I wasn't able to find a configuration option for that.

Thanks in advance!
Steffen
Permalink | Reply | 1 comment |
headers
Paul Menzel | 16 Jul 2011 18:54

Re: Multiple "Re:" headers

Dear Steffen,

On Sa, 2011-07-16 at 14:17 +0200, Steffen Gebert wrote:

> we have a sympa list server running and a few users complain about subjects like
> > Re: Re: AW: Re: Re: foo bar

you must be running an old version of Sympa. Please always include such
information.

> Is there a way that sympa automatically removes (at least) the Re: prefixes of such subjects?

Please take a look at the thread »Excessive "re:" in subjects« [1] and
back port that patch to your installation.

> I wasn't able to find a configuration option for that.

There is none as far as I know.

Thanks,

Paul

[1] https://listes.cru.fr/sympa/arc/sympa-users/2010-08/msg00088.html
Permalink | Reply | 0 comments |
headers
Paul Menzel | 16 Jul 2011 18:58

Re: Bug with Replies

On Fr, 2009-09-18 at 12:12 -0600, Mark Ogden wrote:
> Was there ever a solution to this issue?

I am sorry for the late reply, which is why I put you into CC. Please
take a look at the thread »Excessive "re:" in subjects« [1].

Thanks,

Paul

[1] https://listes.cru.fr/sympa/arc/sympa-users/2010-08/msg00088.html
Permalink | Reply | 0 comments |
headers
sympa | 17 Jul 2011 00:58
Picon

Reminder of your subscription to sympa-users

Your are subscriber of list sympa-users@... with  email
gmsu-sympa-users <at> m.gmane.org

Everything about this list: https://listes.cru.fr/sympa/info/sympa-users

Unsubscription:
mailto:sympa@...?subject=sig%20sympa-users%20gmsu-sympa-users%40m.gmane.org
Permalink | Reply | 0 comments |
headers
Sérgio Afonso | 19 Jul 2011 15:39
Picon

Using SYMPA in 2 distinct servers.

Hello *,

I have a doubt about a scenario I am trying to implement using Sympa.

I have 2 servers (One is the Relay server (Postfix) and the other one is
where the mailboxes are located (Sendmail)).

The distinction between this 2 servers is done via an external/internal
DNS zones.

I tried to install Sympa in the Relay server but when a message is
delivered to a list it tries to send to the local mailboxes which do not
exist. Is it possible to have Sympa and WWSympa installed in the Relay
server and deliver the mail on the Mailboxes server?

Can I have a separation between the Web Interface and the Sympa daemon
in 2 different servers?

Thanks for any hint you could give me. Best regards,

Sérgio Afonso
Permalink | Reply | 1 comment |
headers
Amos | 20 Jul 2011 03:57
Picon

spam flood

Well, due to some unpleasant circumstances, one of our lists got hammered with thousands of mail.  I'm trying to cut-off further delivery of mail out of this list.  I even removed and purged the list.  However, mail is still coming out from this list.  My guess is that the internal queue/db still have tons of mail.  However, how do I clear this out?  I want to obliterate all artifacts of this list from our server!



Permalink | Reply | 2 comments |

Gmane