#musicbrainz

hey, the quick search ist online. Thanks djce!

oops

djce is update happy...

ok, hope it works ;-) Dinner time.

ahhh, just the person I needed to talk to.

Scott's email verification bounces because of:

(reason: 550 rejected: there is no valid sender in any header line (envelope sender is <noreply@musicbrainz.org>))

ok....

RFC 822 specifies that a Sender: line is not needed unless its different from the From line.

Its discouraged if its the same as the from line.

But Scott's mail system rquires it.

so is Scott's mail system incorrect when it says that the noreply address is invalid?

From what I am reading, yes.

When a mail is sent out from Zim to Scott, does his mail server connect back to Zim to check up on the sender address?

ruaok: RFC 822 is obsolete. Perhaps there are some changes in 2822?

Ah. THanks for the clue by four.

mailbox of the agent responsible for the actual transmission of the

message. For example, if a secretary were to send a message for

another person, the mailbox of the secretary would appear in the

"Sender:" field and the mailbox of the actual author would appear in

the "From:" field. If the originator of the message can be indicated

by a single mailbox and the author and transmitter are identical, the

"Sender:" field SHOULD NOT be used. Otherwise, both fields SHOULD

appear.

Seems like Scoot's mailer should not bounce mail based on that criteria.

What is even more strange is that the mail I sent from Evolution to scott does not have a sender line and it gets delievered ok.

djce: I don't know.

I doubt it.

The error message it gives is a bit odd.

Indeed,

It claims there is no valid sender "in any header line", which presumably means "From", "Sender", "Reply-To" etc.

I'm wondering if I am improperly formatting something and that everyone but Scott's mailer is flexible in accepting it.

then it cites the envelope sender - which is of course completely different.

Where can I find scott's address?

on sec.

It must be in my mail somewhere, but I can't see it yet.

ok thanks

Does the order of From and To make a difference?

OHHH. I think I get it.

No. What do you "get"?

If To: line reads:

To: ScottM87 <scott@smartblob.com>;

ScottM87 is a moderator name, not a mailbox nam,e

I wonder if we used:

To: scott <scott@smartblob.com>;

If that would work?

Actually I was thinking it probably doesn't like the non-existent "From" address at "users.musicbrainz.org".

Hmmm. That makes more sense.

Maybe we should say "From: foo@users.mb.org"; and "Sender: webserver@mb.org";

Hmmm. Worth a try.

Lemme tinker.

in fact, I can pretty much guarantee that's it.

Because "users.musicbrainz.org" probably doesn't have any DNS MX records

therefore anything at that domain is trivially invalid.

I believe we have a blanket MX record that should cover that.

Regardless that it is good thing to try.

I checked the sources of exim 3.36 (the one that smartblob.com uses). It seems the option headers_sender_verify is on

See http://www.exim.org/exim-html-3.30/doc/html/spe...

ok, I've fixed it and I'm about to send him a verification mail by hand. Lets see if it comes back.

Good research yalaforge. Looks like it should be easy to fix now we understand it.

djce: can you do me a favor and check out my utf-8 encoding on test.mb.org and verify your email again?

yalaforge: you too, please?

ok

The mail went out and no bounces so far.

you want me to check your code, ruaok?

sure.

Lemme check it in.

But I was more concerned about the headers.

mail is here

yeay!

The "Mime-Version: 1.0" is missing, AFAICS

You should remove the encode("utf-8",...) bit. All our internal data is already utf8-encoded.

damn. You're fast.

So encode_qp is all we need then?

Yes. And not even that in the "confirmation" email, since there is nothing to encode.

MIME::QuotedPrint is that standard perl?

i.e. remove the Content-Transfer-Encoding from SendVerificationEmail

perl 5.8.0 standard, I think yes.

ruaok: is ruaok.net your domain? I don't get it via whois.

yes. I let it lapse. I'm too poor to affort too many domains.

(oh, I see, you're encoding it all at the end. Oh, leave it in then).

In SendVerificationEmail the utf-8/QP encoding is ok, but over the top, since the text of the message is guaranteed to be all standard US-ASCII stuff anyway.

Moderator names could have UTF-8 chars in them.

yes, indeed.

Do I need to add the Mime-Version: 1.0 header?

yes.

wait a minute, please

I think so. I always forget it, but it should be added.

ruaok: missing utf8/qp encoding here: "If you would like to send mail to moderator $from,"

ok got it.

ok, mime version is in there, server restarted.

Do you guys want to try it one more time?

sure

djce: is it safe to update UserStuff.pm on the main server once we're happy here?

Yes, as long as the changes are small and isolated. Best to do a "cvs diff -r HEAD" on zim to check.

My changes are, I was wondering if there was something else.

is your stuff fully committed now?

djce: Do you know if MIME::QuotedPrint is standard perl? I wanna add it to the proper section in INSTAL

RFC-2045 states: "Messages composed in accordance with this document MUST include such a header field, with the following verbatim text: MIME-Version: 1.0" See section 4.

MIME::QuotedPrint is part of "G/GA/GAAS/MIME-Base64-2.20.tar.gz" - not vanilla Perl 5.8.0, but usually one of the first add-ons people install :-) Best to list it in the INSTALL file, it can't hurt.

btw there is a really nice, slick, much more Perl-y way of doing all that e-mail generation stuff. I'll see if I can refer to an example some time to remember the slick way to do it.

let me commit the next version now.

I'll send you a mail with some examples.

ruaok: The MessageId is still '@cranky.ruaok.net';. I'd change that to mb.org. The rest is ok.

yes, the Message-ID is generated by sendmail on each server, not by the MusicBrainz code.

i.e. That will be automatically correct when it goes live.

yeah, people won't be using it on this machine much.

ah, ok

My spam filter gives it a -.3 rating.

Does the code handle moderator names with non-ascii characters?

Nice.

Yes.

cool

then I'd go to bed if there's nothing more to test ;-)

unless you want to test the main server when I make it go live in about 2 minutes. :-)

any objections djce?

ok

sorry, was away then... wait a mo.

lemme check the diffs

only UserStuff.pm, yes?

yes

use Encoding; is still in there and is not needed anymore.

Is "webserver@mb.org"; a valid address?

It will be when I do the update.

looks good to me.

it is now.

ok

ok, what is the preferred way of restarting the server to pick up this new module?

apachectl restart?

on apache 1?

cvs update cgi-bin/UserStuff.pm ; touch /usr/local/perl58/reload_modules

no restart required.

really? wow.

so then it should be live now.

cool.

How do you tell? :-)

send each other a mail I suppose.

works. I got the mail

looks good to me.

thanks for testing.

np. Good night

night!

Rob, you should get a mail from me with a few foreign characters in it.

Yup, and the URL at the bottom is no bueno.