mainSavannah Administration - Support: sr #106478, After committed to www project's...

 
 

sr #106478: After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Submitter:  Ali Servet Donmez <exalted>
Submitted:  Mon 25 Aug 2008 01:09:45 PM UTC
   
 
Category:  Project mailing lists Priority:  5 - Normal
Severity:  3 - Normal Status:  Done
Privacy:  Public Assigned to:  yavor
Operating System:  GNU/Linux Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Wed 03 Dec 2008 12:09:36 AM UTC, comment #44: 


> Did you rather mean "the absence of fix"?


No, I meant that the changes you made to "fix" Ali's problem had the negative effect of losing commit notifications (even in the form of a bounce to the committer), which is now hopefully not a problem after Ward's intervention.

Yavor Doganov <yavor>
Tue 02 Dec 2008 06:36:43 AM UTC, comment #43: 


> Closing this as the negative effect of Sylvain's changes to fix
> this has been workarounded by the GNU sysadmins:


Nice job.

Did you rather mean "the absence of fix"?

Sylvain Beucler <Beuc>
Mon 01 Dec 2008 09:14:16 PM UTC, comment #42: 

Closing this as the negative effect of Sylvain's changes to fix this has been workarounded by the GNU sysadmins:

http://lists.gnu.org/archive/html/savannah-hackers/2008-12/msg00000.html

Yavor Doganov <yavor>
Wed 22 Oct 2008 06:21:52 PM UTC, comment #41: 


> > Which reminds me somebody offered Perl skills recently
> Certainly not me,


For reference I was refering to Steve Dickinson, who said he'd work on it.

Sylvain Beucler <Beuc>
Thu 16 Oct 2008 08:53:46 PM UTC, comment #40: 


> It is highly undesirable for me to change this piece


Yeah, I can imagine and suspected so.  Agreed completely.

> Which reminds me somebody offered Perl skills recently


Certainly not me, Perl looks like output from /dev/random to me.  But I'll look into this (provided that nobody else volunteers) once  I finish the other PHP thing I (once) promised to finish...

Yavor Doganov <yavor>
Thu 16 Oct 2008 08:00:13 PM UTC, comment #39: 


> You mean, if the message exceeds the defined size limit, to send only the summary of the files modified/added/removed (plus eventually CVSWeb URLs), right? That would be ideal.


Or we can crop the diff.

> Do you know if other CVS commit notification software (cvs-mailcommit, cvs-syncmail, etc.) already implement this? (Of course provided that it is not highly undesirable to switch to them for other reasons.)


It is highly undesirable for me to change this piece of software because all the commit hooks management is based on it and I don't want to reimplement it. It also has branch-filtering features, it's been tested pretty thoroughly now, and I've got a good enough contact with the (passive) maintainer.

So best is to implement said diff cropping.
Which reminds me somebody offered Perl skills recently (grin ;)).

Sylvain Beucler <Beuc>
Thu 16 Oct 2008 02:36:30 PM UTC, comment #38: 


>> If the message is rejected due to (say) size limit, the user
>> won't get a bounce.


This happened several times already.

> In this case, what we need is patching CVS log_accum to support
> diff size limit


You mean, if the message exceeds the defined size limit, to send only the summary of the files modified/added/removed (plus eventually CVSWeb URLs), right?  That would be ideal.

Do you know if other CVS commit notification software (cvs-mailcommit, cvs-syncmail, etc.) already implement this?  (Of course provided that it is not highly undesirable to switch to them for other reasons.)

Yavor Doganov <yavor>
Thu 11 Sep 2008 08:21:17 PM UTC, comment #37: 

That's true.
In this case, what we need is patching CVS log_accum to support diff size limit (as the competition does).

Sylvain Beucler <Beuc>
Thu 11 Sep 2008 08:59:16 AM UTC, comment #36: 

Hmm, I'm not sure, but I think this implementation will have nefarious effects sometimes.  If the message is rejected due to (say) size limit, the user won't get a bounce.

This is important for me, because GNUN builds often generate large diffs, which I read at least partially in the bounced message.  And the most important information is the files which were modified/added...

Yavor Doganov <yavor>
Thu 11 Sep 2008 08:47:45 AM UTC, comment #35: 

I'll keep this as short and as informative as possible: I love you guys! =D

(file #16462)

Ali Servet Donmez <exalted>
Thu 11 Sep 2008 08:30:28 AM UTC, comment #34: 

I'll check if this will work at our next commit.

Ali Servet Donmez <exalted>
Thu 11 Sep 2008 06:11:02 AM UTC, comment #33: 

Hi grischka, this has nothing to do with the current issue, please don't add to the confusion and post separately :)
Nonetheless your problem is fixed.

Sylvain Beucler <Beuc>
Thu 11 Sep 2008 03:38:36 AM UTC, comment #32: 

FYI, I don't know if it's related but I just got this error:

cvs: cd tinycc && cvs -q -z9 ci -R -m "fix isidnum_table for CH_EOF (-1)" tcc.c
/sources/tinycc/tinycc/tcc.c,v  <--  tcc.c
new revision: 1.206; previous revision: 1.205

  • Fatal error: /tmp/#tinycc_89.19228.lastdir is not present.

  It should have been generated by commit_prep.
  Check your CVSROOT/commitinfo file. at /usr/local/bin/log_accum.pl line 1474, <STDIN> line 7.

Appearantly no message was sent to the mailing list, but the commit is there.

--- grischka

Anonymous
Wed 10 Sep 2008 10:30:50 PM UTC, comment #31: 

Another pro of solution #2 is that it's now implemented at Savannah :)
Let's see if this works out.

Sylvain Beucler <Beuc>
Wed 10 Sep 2008 08:06:39 PM UTC, comment #30: 

I understand it as "We won't change our setup, people have to adapt to us and not the other way around. For future reference, the reason is: because."

Yet, despite the lack of information from their part, Yavor's post#26 is very interesting and shows that they implement a sender rewriting scheme (SRS) which means they accept error returns ("bounces") as long as mail is sent from their servers.

In this case Savannah is sending mail on your behalf through, well, Savannah, which isn't their webservers, so this doesn't work. I think I had an issue with a SPF user quite a while ago but this eventually settled down, but I can't say why.

So,

We have 2 solutions:

- configure your Savannah account to use a different mail account, one which accepts basic sender verification, or

- bug the Savannah team into changing the CVS commit notifications so they don't attempt to send mail on your behalf (and trigger those sender verifications). This essentially means user won't receive errors ("bounces") if anything goes wrong. This also means they won't have sender-verification-related issues.

Advantage of solution #1 is that you can make it work in the next 5mns.

Advantage of solution #2 is that it's probably something we should do.

Sylvain Beucler <Beuc>
Mon 08 Sep 2008 12:59:41 PM UTC, comment #29: 

They meant that this is a problem on gnu.org's end. I'll try to re-contact them whenever I can.

"perhaps it would be much easier to setup a gnu.org account for you as Turkish team co-ordinator :-)". I wouldn't say "no" as I'm already checking 7-8 different accounts every day, once more wouldn't much hurt me... =)

Regards,
Ali

Ali Servet Donmez <exalted>
Mon 08 Sep 2008 12:49:41 PM UTC, comment #28: 

I couldn't understand whether they acknowledge the problem but are unable to fix it or they claim that it is gnu.org's fault?

This is definitely a problem of your service -- please tell them to try the session with mx.pittle.org at comment #23.  The response of the server to the RCPT command should be a 2xx code, and not 5xx like this:

550 5.1.1 Host 213.91.219.2 error: B1.1.1

Just for the sake of completeness, here are truncated sessions to Debian, FSFE, Microsoft, BIMCO and Karl Berry's server -- they all use different software, but are configured properly and are standards compliant.  lists.gnu.org is performing a legitimate check which fails due to a problem at your end.  I am not sure what else can we do to convince them -- perhaps it would be much easier to setup a gnu.org account for you as Turkish team co-ordinator :-)

$ telnet master.debian.org 25
220 master.debian.org ESMTP Exim 4.63 Mon, 08 Sep 2008 12:37:11 +0000
rcpt to: <zinoviev@debian.org>
250 Accepted

$ telnet cavendish.fsfeurope.org 25
220 cavendish.fsfeurope.org ESMTP Postfix (Debian/GNU)
rcpt to: <xreina@fsfe.org>
250 2.1.5 Ok

$ telnet mail.global.frontbridge.com 25
220 mail35-wa4.bigfish.com ESMTP Postfix EGGS and Butter
rcpt to: <support@microsoft.com>
250 Ok
(Wow!  They're using Postfix!)

$ telnet cluster1.comendo.dk 25
220 Comendo Mailfence v.4.0 Ready!
rcpt to: <mailbox@bimco.org>
250 Ok

$ telnet freefriends.org 25
220 f7.net ESMTP Sendmail 8.11.7-20030920/8.11.7; Mon, 8 Sep 2008 07:46:29 -0500
rcpt to: <karl@freefriends.org>
250 2.1.5 <karl@freefriends.org>... Recipient ok

Yavor Doganov <yavor>
Mon 08 Sep 2008 12:00:34 PM UTC, comment #27: 

I've contacted tech support of my provider and below is the transcript of our chat for your consideration:

----------------------------------------------------------------------

Ali Servet Dönmez: I'm not able to send e-mails to a mailing list
which does "callback verification" as they say, and apparently this
verification won't succeed in my side, thus their mailing service will
refuse to receive my message. How can you help me?

Allan Ross: Can you please elaborate the issue?

Ali Servet Dönmez: Sure there's a full transcript of our support chat
with the mailing list support here:
https://savannah.gnu.org/support/?106478 if you could just give it a
look from bottom to top.

Allan Ross: Could you please hold for 2 to 3 minutes, while I check
this for you?

Ali Servet Dönmez: Sure Allan, I'll hold.

Allan Ross: Thank you for holding.

Allan Ross: Ali, I have consulted this issue with one of our
specialists and he mentioned that the issue is from the their end and
you need to contact them to resolve the issue.

Ali Servet Dönmez: How did he be sure about this? I mean they too said
the same to me.

Ali Servet Dönmez: I don't wanna bounce my self here and there with no
results?

Ali Servet Dönmez: Could you please explain me what's wrong exactly?

Allan Ross: Ali, one of our specialists checked the transcript and he
had mentioned that we are unable to do any thing for the callback
verification from our end.

Allan Ross: I apologize for any inconvenience this has caused you.

Ali Servet Dönmez: Okay Allan, thank you very much. I'll get back to
them and mention what you've said.

Allan Ross: Sure.

Allan Ross: You're welcome!

----------------------------------------------------------------------

Regards,
Ali

Ali Servet Donmez <exalted>
Fri 29 Aug 2008 05:09:51 PM UTC, comment #26: 

I think I am beginning to realize why you can post directly but notifications are not delivered.

When you post to a GNU mailing list (or to me personally, it doesn't matter), the message is picked by fw-pool-128.gruppocredit.it (your ISP/company's SMTP server, I guess) and it passes through several hops at yourhostingaccount.com, rewriting the envelope to something like <SRS0=Q+E4By=ZF=pittle.org=asd@yourhostingaccount.com>. 

I believe this is what the gnu.org server performs the callout verification for, e.g. the following (simulated) check happens:

telnet mail.yourhostingaccount.com 25
[...]
mail from: <>      
250 2.1.0 <> sender ok
rcpt to: <SRS0=Q+E4By=ZF=pittle.org=asd@yourhostingaccount.com>
250 2.1.5 <srs0=q+e4by=zf=pittle.org=asd@yourhostingaccount.com> recipient ok

So the verification succeeds, and therefore delivery.

By contrast, when you do a commit, cvs.savannah.gnu.org (the CVS server) constructs the message (with the help of log_accum.pl) with envelope <exalted@savannah.gnu.org> (your Savannah account), which is then changed by savannah.gnu.org to <asd@pittle.org> (the email address you registered at Savannah), and passed along.  This is the what's being verified then, and the verification fails with this cryptic error (which is easily reproducible in a SMTP session, as I've shown in comment #23).

It looks like this error is something specific to this email service provider.

Such a check by automatically constructed messages like the CVS commit notifications are always going to fail to deliver to hosts which perform (again, entirely legitimate) sender callout verification.

Options:
1) If you have control over the server configuration of yourhostingaccount.com, please do the necessary changes so that this particular check succeeds.  It is a non-standard behavior if it does not, like now.  (It looks like this is some large hosting company, so I doubt this is realistic.)

2) Inform their support about this problem, and ask them to solve it (it seems others have encountered it too, and probably reported it, but it's still worth trying).

3) Stop using their service.  This might be very inconvenient depending on how your things are set up.  Anyway, just mentioning it as an option.

In any event, let's wait for the GNU sysadmins.

(Disclaimer: Obviously I'm not an expert, so I might be very wrong in all of this.)

Yavor Doganov <yavor>
Fri 29 Aug 2008 10:43:43 AM UTC, comment #25: 

Your mail server rejects bounces, i.e. it cannot handle mail from the null envelope sender address.  Look how there is no problem here:

$ telnet mx.pittle.org 25
Trying 65.254.254.50...
Connected to mx.pittle.org.
Escape character is '^]'.
220 impinc03.yourhostingaccount.com NO UCE ESMTP server ready
ehlo southway-varna.com
250-impinc03.yourhostingaccount.com hello [213.91.219.2], pleased to meet you
250-HELP
250-SIZE 34603008
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250 OK
mail from: <y.doganov@southway-varna.com>
250 2.1.0 <y.doganov@southway-varna.com> sender ok
rcpt to: <asd@pittle.org>
250 2.1.5 <asd@pittle.org> recipient ok
quit
221 2.0.0 impinc03.yourhostingaccount.com NO UCE closing connection
Connection closed by foreign host.

This also explains why you don't get a bounce that your commits cannot be delivered to www-commits -- you were clueless and didn't know the reason; if your mail service had accepted the bounces, you would know at least the error code/reason.

Yavor Doganov <yavor>
Fri 29 Aug 2008 10:27:44 AM UTC, comment #24: 

I'm afraid I don't get any of this. ;-(

Ali Servet Donmez <exalted>
Fri 29 Aug 2008 10:20:54 AM UTC, comment #23: 

First -- no need to send anything to sysadmin, Sylvain already did that yesterday with CC to you.

Second -- the link Sylvain gave in comment #17 is pretty descriptive.

Before accepting the message, lists.gnu.org does this SMTP callback to ensure that the sender really exists.  Let me try to emulate this in a live session.  I'm connecting from my workstation at work to my mailserver at home:

$ telnet yavor.doganov.org 25
Trying 213.91.245.92...
Connected to yavor.doganov.org.
Escape character is '^]'.
220 yavor.doganov.org ESMTP Exim 4.69 Fri, 29 Aug 2008 13:11:54 +0300
ehlo southway-varna.com
250-yavor.doganov.org Hello bow.southway-varna.com [213.91.219.2]
250-SIZE 52428800
250-PIPELINING
250 HELP
mail from: <>
250 OK
rcpt to: <xxx@yavor.doganov.org>
550 Unrouteable address
rcpt to: <yavot@yavor.doganov.org>
550 Unrouteable address
rcpt to: <yavor@yavor.doganov.org>
250 Accepted
quit
221 yavor.doganov.org closing connection
Connection closed by foreign host.

So if I change my Savannah email address to <yavot@yavor.doganov.org> and try to commit, the notification message will get rejected in the same manner like yours (although with a different error).  If I change it to <yavor@yavor.doganov.org> -- this is a real address, and the callback returns success, so I guess there won't be any problems.

Now let's do the same thing with you:

$ telnet mx.pittle.org 25
Trying 65.254.254.51...
Connected to mx.pittle.org.
Escape character is '^]'.
220 impinc02.yourhostingaccount.com NO UCE ESMTP server ready
ehlo southway-varna.com
250-impinc02.yourhostingaccount.com hello [213.91.219.2], pleased to meet you
250-HELP
250-SIZE 34603008
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250 OK
mail from: <>
250 2.1.0 <> sender ok
rcpt to: <asd@pittle.org>
550 5.1.1 Host 213.91.219.2 error: B1.1.1
Connection closed by foreign host.

I don't know what that means, as my knowledge about DNS is very poor (and so is for SMTP).  lists.gnu.org uses Exim as most of the GNU servers, and I believe this particular feature is described at

info "(exim4)Callout verification"

Hope that helps identifying and solving the problem.

Yavor Doganov <yavor>
Fri 29 Aug 2008 09:48:09 AM UTC, comment #22: 

Could you please explain "SMTP callback"? I might be able to make some changes in server side, in case something is wrong with my configuration...

Which e-mail address, SMTP server, is used as sender when I commit into www, or is this done automatically in your side? Where is this configured?

I wouldn't want, for some strange reason, my email address results as -email is unavailable- (exalted is my local user name) instead of asd@pittle.org, so an e-mail sent to addresses that do not exist at my domain, except for the specific addresses that I configured, will be returned to the sender and not delivered to my account.

By returning (or bouncing) the message to the sender, I am protecting myself from unwanted spam. If the message is legitimate but was simply sent to the wrong address, the sender will be notified that the address is not valid.

@yavor: I still haven't open a support request for sysadmins, should I do that to you?

Ali Servet Donmez <exalted>
Fri 29 Aug 2008 08:51:42 AM UTC, comment #21: 

No clues; perhaps this SMTP callback is performed only under certain conditions -- for example, for messages coming from cvs.savannah.gnu.org.  The sysadmins will tell.

Meanwhile, this is a legitimate way to perform sender verification.  Your mail service is not RFC compliant, so the actual problem is in your yard.

Let's wait for the sysadmins comments.

Yavor Doganov <yavor>
Fri 29 Aug 2008 08:15:38 AM UTC, comment #20: 

I am actually able to send mail on -email is unavailable- from my mail client with speed of light. Comments?

Ali Servet Donmez <exalted>
Fri 29 Aug 2008 08:12:51 AM UTC, comment #19: 

Sure, I am using many www-tr-* mailing lists, trans-coord-discuss, etc. Now I'll try to send a message on -email is unavailable- from my daily mail client and see if that will succeed.

Ali Servet Donmez <exalted>
Thu 28 Aug 2008 05:36:18 PM UTC, comment #18: 

Also, did you manage to send mail to any other GNU list?

Sylvain Beucler <Beuc>
Thu 28 Aug 2008 05:30:24 PM UTC, comment #17: 

Nope, message was rejected again.

I believe that your mail server rejects "bounces", that is, failure notifications.

I found this topic about a guy who is at the same hosting service that you:
http://forums.whirlpool.net.au/forum-replies-archive.cfm/949575.html
Same problem.

Your mail service is breaking the mail standard by not accepting "bounces", and thus this may have impact. In particular this breaks sender verification, which lists.gnu.org uses.

It is strange that it happened suddenly, maybe there was a change at your mail service recently. Let's forward this to -email is unavailable- to see if they have more info.

Sylvain Beucler <Beuc>
Thu 28 Aug 2008 04:03:02 PM UTC, comment #16: 

$ cvs commit -m "Sync with home.tr.po in www-tr's repo." po/home.tr.po
/web/www/www/po/home.tr.po,v  <--  po/home.tr.po
new revision: 1.11; previous revision: 1.10
Triggering webpages update...
Mailing notification to www-commits@gnu.org... sent.

$ cvs log -d today po/home.tr.po

[...]
revision 1.11
date: 2008-08-28 15:59:42 +0200;
[...]

No luck I guess?

Ali Servet Donmez <exalted>
Thu 28 Aug 2008 08:38:31 AM UTC, comment #15: 

I'll check this out once I'll make a commit.

Ali Servet Donmez <exalted>
Thu 28 Aug 2008 08:20:42 AM UTC, comment #14: 

It might be a temporary problem as Sylvain says (although I doubt it, as I advised you to open a support request if the problem persists).

Try to commit these days, and if it's not delivered to the list, write to -email is unavailable- (and get yourself armed with patience, as they're usually overloaded).

Yavor Doganov <yavor>
Thu 28 Aug 2008 08:16:06 AM UTC, comment #13: 

I am completely lost here. What did exactly happen and/or resolved Sylvain please?

Ali Servet Donmez <exalted>
Thu 28 Aug 2008 07:43:11 AM UTC, comment #12: 

Karl and Yavor: the mails you reference were posted before this support request. Most likely there is a temporary problem (spam suspicion, maintenance, etc.) which made Ali's mail service to reject mails (or more precisely, mail verifications) from the GNU computers.

Apparently now Savannah can again send mail to @pittle.org.
I don't know for lists.

If problems persist, I suggest contacting -email is unavailable- and ask them to look for problems related to asd@pittle.org.

Sylvain Beucler <Beuc>
Wed 27 Aug 2008 08:20:40 AM UTC, comment #11: 

So, correct me if I'm wrong, but there's not much that I can do to fix the problem?

I mean, I've never ever had problems sending mails nowhere before and as yavor cited [0], I can actually send mails on gnu.org mailing lists (well... except "www-tr-admin" really).

[0]: https://savannah.gnu.org/support/?106478#comment9

Ali Servet Donmez <exalted>
Tue 26 Aug 2008 08:01:10 PM UTC, comment #10: 

I'm sorry if this is already known, but I believe the problem is with the creation of the commits mail, not with www-commits list configuration or Ali's mail configuration, broken as it may be.

I think this because the (human-written) msgs which Ali has sent to www-commits in reply to various commits have made it to the archives, at least into the file /home/mharc/mbox/www-commits/2008-08.  (I did not have a chance to check other archives.)  They are attached as aliarch.txt.gz.  (And I already asked Ali not to reply on www-commits any more. :)

FWIW.




(file #16363)

Karl Berry <karl>
Site Administrator
Tue 26 Aug 2008 06:57:33 PM UTC, comment #9: 

I find it odd that he posts without problem to GNU mailing lists directly, for example:
<http://lists.gnu.org/archive/html/www-commits/2008-08/msg00199.html>
<http://lists.gnu.org/archive/html/www-commits/2008-08/msg00192.html>
<http://lists.gnu.org/archive/html/www-commits/2008-08/msg00198.html>

(And many others examples to -email is unavailable- and www-discuss@gnu.org, but they're private lists.)

Yavor Doganov <yavor>
Tue 26 Aug 2008 06:47:39 PM UTC, comment #8: 

In English: your mail service is misconfigured, and hence lists.gnu.org rejects all your mail.


More precisely, when lists.gnu.org checks if -email is unavailable- exists, your mail service answers:
"Host 199.232.41.3 error: B1.1.1"
(which doesn't really help understand what the problem is, heh)


Sylvain Beucler <Beuc>
Tue 26 Aug 2008 08:45:59 AM UTC, comment #7: 

Most probably this is due to DNS mismatch:

$ dig -t MX pittle.org
mx.pittle.org.          1592    IN      A       65.254.254.52
mx.pittle.org.          1592    IN      A       65.254.254.50
mx.pittle.org.          1592    IN      A       65.254.254.51

$ dig -x 65.254.254.50
50.254.254.65.in-addr.arpa. 3320 IN     PTR     mail.yourhostingaccount.com

$ dig -t MX gnu.org
mx10.gnu.org.           300     IN      A       199.232.76.166
mx20.gnu.org.           300     IN      A       199.232.41.8

$ dig -x 199.232.76.166
rev-c76-166.gnu.org.    300     IN      PTR     mx10.gnu.org.

You should check/fix the DNS records of pittle.org.

Yavor Doganov <yavor>
Tue 26 Aug 2008 08:16:05 AM UTC, comment #6: 

I couldn't literally understand what's wrong here? Could you please explain me what's wrong in plain English? Thanks.

Regards,
Ali Servet Dönmz

Ali Servet Donmez <exalted>
Tue 26 Aug 2008 07:41:16 AM UTC, comment #5: 

Uhhh sorry I must have been pretty tired...
This isn't a translation commit.....

So,

Ali: there seem to be a problem with your e-mail:
2008-08-25 13:07:42 1KXbnJ-0002ZL-TB <= -email is unavailable- H=cvs.savannah.gnu.org [199.232.41.69] P=esmtp S=1682 id=E1KXbnJ-0002ZI-Jn@cvs.savannah.gnu.org
2008-08-25 13:07:48 1KXbnJ-0002ZL-TB ** -email is unavailable- R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<www-commits@gnu.org>
: host mx10.gnu.org [199.232.76.166]: 550-Verification failed for <asd@pittle.org>\n550-Previous (cached) callout verification failure\n550 Sender verify fai
led
2008-08-25 13:07:48 1KXbnQ-0002ZO-2D <= <> R=1KXbnJ-0002ZL-TB U=Debian-exim P=local S=2691
2008-08-25 13:07:48 1KXbnQ-0002ZO-2D ** -email is unavailable- R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<asd@pittle.org>: host mx.
pittle.org [65.254.254.50]: 550 5.1.1 Host 199.232.41.3 error: B1.1.1
2008-08-25 13:07:48 1KXbnQ-0002ZO-2D Frozen (delivery error message)
2008-08-25 13:07:48 1KXbnJ-0002ZL-TB Completed


There are 7 frozen error messages that the system attemps to send you in the mail queue:

2008-08-24 14:52:52 Received from <> R=1KXGxV-0004fw-Gb U=Debian-exim P=local S=5855
2008-08-24 14:52:53 SMTP error from remote mail server after RCPT TO:<asd@pittle.org>: host mx.pittle.org [65.254.254.52]: 550 5.1.1 Host 199.232.41.3 error: B1.1.1
2008-08-24 14:52:53 -email is unavailable- R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<asd@pittle.org>: host mx.pittle.org [65.254.254.52]: 550 5.1.1 Host 199.232.41.3 error: B1.1.1
* Frozen (delivery error message)


So apparently there's something to check/fix at pittle.org.

If you can't figure out what, you may mail -email is unavailable- who may have additional information about the rejection.

Sylvain Beucler <Beuc>
Tue 26 Aug 2008 05:37:48 AM UTC, comment #4: 

He is committing to the web repository of the "www" project like any other webmaster, so there should be notification to www-commits for all check-ins.

Of course translation projects are different projects and should have nothing to do with www-commits.

Yavor Doganov <yavor>
Mon 25 Aug 2008 09:02:55 PM UTC, comment #3: 

Hi Yavor,

As translation projects are separate projects, they don't share project 'www' CVS configuration, so they don't get mail notifications by default.

Do you need to add notifications to 'www-commits' for all translation projects, or set them up separately per translation project?

Sylvain Beucler <Beuc>
Mon 25 Aug 2008 08:53:27 PM UTC, comment #2: 

This is news to me, and I think there's some misunderstanding.  Ali was complaining previously to trans-coord-discuss that his commits do not end up as notifications.  I can only confirm that, and this is no default; it's undesirable behavior that has no explanation.

Ideally, we'de want every commit to www to show up at -email is unavailable- (and so it happens, excpet Ali's and occasionally other's commits).  I certainly rely on the list most of the time (rather than digging into CVS history), and some translators depend on the notifications (for different purposes) as well.

Is it possible that because of Ali's Savannah registered full name has non-ASCII characters, log_accum.pl somehow doesn't manage to send  a message?  I think that's a bogus assumption, but I still can't explain myself why no notification is sent, especially because "...sent." is printed only upon success.

In my book this is certainly a bug; all commits should deliver to the designed address, no matter what.

Yavor Doganov <yavor>
Mon 25 Aug 2008 08:34:22 PM UTC, comment #1: 


> Summary says pretty everything though: "After committed
> to www project's (http://www.gnu.org) webpages repo,
> a commit message won't be sent on www-commits mailing list".


I think this is a safe default.  Yavor, do you have needs in this regard?

Sylvain Beucler <Beuc>
Mon 25 Aug 2008 01:09:45 PM UTC, original submission:  

Summary says pretty everything though: "After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list".

I'm using cvs version 1.12.13 to access, and here's a copy of an actual commit that I've made:

# BEGINQUOTE
$ cvs commit -m "Very little adjustment." po/home.tr.po
/web/www/www/po/home.tr.po,v  <--  po/home.tr.po
new revision: 1.9; previous revision: 1.8
Triggering webpages update...
Mailing notification to www-commits@gnu.org... sent.
# ENDQUOTE

...with commitid: KVKwPNRqCzzrCagt;

Thank for your support.

Best regards,
Ali Servet Dönmez
(www.gnu.org Turkish translation team leader)

Ali Servet Donmez <exalted>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #16462:  yeah added by exalted (4KiB - application/octet-stream)
file #16363:  aliarch.txt.gz added by karl (4KiB - application/x-gzip)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by karl (Updated the item)
  • -email is unavailable- added by yavor (Posted a comment)
  • -email is unavailable- added by Beuc (Posted a comment)
  • -email is unavailable- added by exalted (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2008-12-01 yavor StatusNone Done
        Open/ClosedOpen Closed
    2008-09-11 exalted Attached File- Added yeah, #16462
    2008-08-26 karl Attached File- Added aliarch.txt.gz, #16363
    2008-08-25 Beuc Assigned toNone yavor

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code