Feature request - Subtree checkouts
Heya,
I'm trying to dig at various issues that are potential holdups for migrating the Gentoo CVS tree into Git.
Since shallow checkouts are now available, there's just one more thing that's missing: subtree checkouts. Not to be confused with sub-projects.
If the master tree has this as some example contents:
/foo
/abc/...
/bar/example
/bar/baz/some-content
We need to be able to check out arbitrary subtrees. So I might want to check out everything (as the CVS administrator), while one of the more focused developers just wants to check out /bar/baz/.
P.S. Does this list do some weird spam-blocking? I've tried 3 times now to use git-send-email to send an unrelated minor patch set (--subject-prefix for git-format-patch), and it has never shown up on the list :-(.
Signature · 4 lines
Robin Hugh Johnson Gentoo Linux Developer & Council Member E-Mail : [email protected] GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
Quoted 4 lines · Robin H. Johnson
P.S. Does this list do some weird spam-blocking? I've tried 3 times now to use git-send-email to send an unrelated minor patch set (--subject-prefix for git-format-patch), and it has never shown up on the list :-(.
Yes. It has cut down on our spam, but it has also caused some things to be blocked, almost without good reason. ;-)
I send a fair number of patches to this list (at times anyway) and am also unable to use git-send-email. If I have the email also CC back to me it does make it through a number of SMTP server hops, including my own spam filters, but it never makes it through the Git mailing list. So I dump the patches to an mbox with --stdout, open them up in mutt and resend them there. I've bound shift-G to resend-message for that purpose...
Signature · 1 line
Shawn.
Quoted 9 lines · Shawn O. Pearce
Quoted 4 lines · Robin H. Johnson
P.S. Does this list do some weird spam-blocking? I've tried 3 times now to use git-send-email to send an unrelated minor patch set (--subject-prefix for git-format-patch), and it has never shown up on the list :-(.Yes. It has cut down on our spam, but it has also caused some things to be blocked, almost without good reason. ;-)
Quoted 7 lines
I send a fair number of patches to this list (at times anyway) and am also unable to use git-send-email. If I have the email also CC back to me it does make it through a number of SMTP server hops, including my own spam filters, but it never makes it through the Git mailing list. So I dump the patches to an mbox with --stdout, open them up in mutt and resend them there. I've bound shift-G to resend-message for that purpose...
Well, we need to do something about this. I haven't seen Robin's patch neither on the list nor in my mailbox (if they were CC'ed to me).
One thing that people need to be careful about is which SMTP server they use. I had an impression (I do not use send-email myself) that it defaulted to local MTA, so the mail trail would look like your local MTA receives from the MUA (which is send-email), which forwards it to whereever destination (or intermediaries). On the other hand, I suspect many people use their ISP's SMTP server when using their usual MUA, so the mail trail would look different. I do not know what filtering vger does, but if it is filtering based on the MTA address (dul.dnsbl.sorbs filtering comes to mind), that would make a difference.
Quoted 3 lines · Junio C Hamano
Well, we need to do something about this. I haven't seen Robin's patch neither on the list nor in my mailbox (if they were CC'ed to me).
They definitely were CC'd to you Junio.
Quoted 11 lines
One thing that people need to be careful about is which SMTP server they use. I had an impression (I do not use send-email myself) that it defaulted to local MTA, so the mail trail would look like your local MTA receives from the MUA (which is send-email), which forwards it to whereever destination (or intermediaries). On the other hand, I suspect many people use their ISP's SMTP server when using their usual MUA, so the mail trail would look different. I do not know what filtering vger does, but if it is filtering based on the MTA address (dul.dnsbl.sorbs filtering comes to mind), that would make a difference.
No, it's not SMTP path differences.
I _know_ that my mail path is identical for git-send-email as well as my MUA, because I had problems with GIT and whitespace in email addresses initially ;-).
Since I have access to all the mail servers in my path (home -> AUTH SMTP @ work -> wherever), I dug at the logs, and found that vger did indeed accept my email to the list, but the messages never turned up on the list.
The only weirdness I saw in that, is that the envelope sender did not appear to be set correct from git-send-email. Give me a moment to explore down that path.
Signature · 5 lines
Robin Hugh Johnson E-Mail : [email protected] Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 ICQ# : 30269588 or 41961639 GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
Envelope sender patches for git-send-email
This patch set is both a testcase, and a useful addition. Some mailing lists (git@vger included) use the envelope sender to determine is posts are allowed, and depending how use git-send-email, the envelope sender might not be the address that you are subscribed with!
PATCH 1/1 Add sendmail -f support to git-send-email.
Some mailing lists use the envelope sender instead of the actual from address, and this can be broken in git-send-email. This patch sets the -f argument to the sendmail binary, using the address of the patch author.
--- git-send-email.perl | 14 +++++++++----- 1 files changed, 9 insertions(+), 5 deletions(-)
git-send-email.perl +9 -5
@@ -34,7 +34,6 @@ sub readline { } package main; - sub usage { print <<EOT; git-send-email [options] <file | directory>...
@@ -446,6 +445,7 @@ sub send_message my ($name, $addr) = ($from =~ /^(.*?)(\s+<.*)/); $from = "\"$name\"$addr"; } + my ($author_addr) = ($from =~ /^.*?\s+<(.*?)>/); my $header = "From: $from To: $to Cc: $cc
@@ -462,16 +462,15 @@ X-Mailer: git-send-email $gitversion if (@xh) { $header .= join("\n", @xh) . "\n"; } - + + my @sendmail_args = ('-f',$author_addr,'-i', map { extract_valid_address($_) } @recipients); if ($dry_run) { # We don't want to send the email. } elsif ($smtp_server =~ m#^/#) { my $pid = open my $sm, '|-'; defined $pid or die $!; if (!$pid) { - exec($smtp_server,'-i', - map { extract_valid_address($_) } - @recipients) or die $!; + exec($smtp_server, @sendmail_args) or die $!; } print $sm "$header\n$message"; close $sm or die $?;
@@ -493,6 +492,11 @@ X-Mailer: git-send-email $gitversion print "Server: $smtp_server\n"; } else { print "Sendmail: $smtp_server\n"; + my $s = ""; + foreach my $a (@sendmail_args) { + $s .= " \'".$a."\'"; + } + print "Args:$s\n"; } print "From: $from\nSubject: $subject\nCc: $cc\nTo: $to\n\n"; if ($smtp) {
Signature · 1 line
1.5.1
PATCH 1/1 Make envelope-sender fully configurable.
From: Robin H. Johnson <[email protected]>
This patch makes envelope sender fully configurable, and also allows it to be use with Net::SMTP instead of just the sendmail binary.
--- git-send-email.perl | 30 ++++++++++++++++++------------ 1 files changed, 18 insertions(+), 12 deletions(-)
git-send-email.perl +18 -12
@@ -76,6 +76,8 @@ Options: --quiet Make git-send-email less verbose. One line per email should be all that is output. + --envelope-sender Specify the sender address used for the email envelope. + EOT exit(1); }
@@ -130,7 +132,8 @@ my $compose_filename = ".msg.$$"; # Variables we fill in automatically, or via prompting: my (@to,@cc,@initial_cc,@bcclist,@xh, - $initial_reply_to,$initial_subject,@files,$from,$compose,$time); + $initial_reply_to,$initial_subject,@files,$from,$compose,$time, + $envelope_sender); # Behavior modification variables my ($chain_reply_to, $quiet, $suppress_from, $no_signed_off_cc,
@@ -169,6 +172,7 @@ my $rc = GetOptions("from=s" => \$from, "bcc=s" => \@bcclist, "chain-reply-to!" => \$chain_reply_to, "smtp-server=s" => \$smtp_server, + "envelope-sender=s" => \$envelope_sender, "compose" => \$compose, "quiet" => \$quiet, "suppress-from" => \$suppress_from,
@@ -445,7 +449,10 @@ sub send_message my ($name, $addr) = ($from =~ /^(.*?)(\s+<.*)/); $from = "\"$name\"$addr"; } - my ($author_addr) = ($from =~ /^.*?\s+<(.*?)>/); + if(!defined $envelope_sender or -z $envelope_sender) { + $from =~ /^.*?\s+<(.*?)>/; + $envelope_sender = $1; + } my $header = "From: $from To: $to Cc: $cc
@@ -463,9 +470,10 @@ X-Mailer: git-send-email $gitversion $header .= join("\n", @xh) . "\n"; } - my @sendmail_args = ('-f',$author_addr,'-i', map { extract_valid_address($_) } @recipients); + my @sendmail_args = ('-f',$envelope_sender,'-i', map { extract_valid_address($_) } @recipients); if ($dry_run) { # We don't want to send the email. + $smtp = !($smtp_server =~ m#^/#); } elsif ($smtp_server =~ m#^/#) { my $pid = open my $sm, '|-'; defined $pid or die $!;
@@ -477,7 +485,7 @@ X-Mailer: git-send-email $gitversion } else { require Net::SMTP; $smtp ||= Net::SMTP->new( $smtp_server ); - $smtp->mail( $from ) or die $smtp->message; + $smtp->mail( $envelope_sender ) or die $smtp->message; $smtp->to( @recipients ) or die $smtp->message; $smtp->data or die $smtp->message; $smtp->datasend("$header\n$message") or die $smtp->message;
@@ -489,17 +497,15 @@ X-Mailer: git-send-email $gitversion } else { print "OK. Log says:\nDate: $date\n"; if ($smtp) { - print "Server: $smtp_server\n"; + print "SMTP Server: $smtp_server\n"; + print "SMTP MAIL FROM: $envelope_sender\n"; + print "SMTP RCPT TO: ".join(', ',@recipients)."\n"; } else { print "Sendmail: $smtp_server\n"; - my $s = ""; - foreach my $a (@sendmail_args) { - $s .= " \'".$a."\'"; - } - print "Args:$s\n"; + print "Args: '".join("' '",@sendmail_args)."'\n"; } print "From: $from\nSubject: $subject\nCc: $cc\nTo: $to\n\n"; - if ($smtp) { + if ($smtp and not $dry_run) { print "Result: ", $smtp->code, ' ', ($smtp->message =~ /\n([^\n]+\n)$/s), "\n"; } else {
@@ -616,7 +622,7 @@ sub cleanup_compose_files() { } -$smtp->quit if $smtp; +$smtp->quit if ($smtp and not $dry_run); sub unique_email_list(@) { my %seen;
Signature · 1 line
1.5.1
Re: [PATCH] Add sendmail -f support to git-send-email.
In reply to Robin H. JohnsonWeird mail header here:
"Cc: [email protected], [email protected], [email protected], [email protected]"
Looks like git-send-email didn't put the quotation marks around the CC address, so my MTA broke it up (and tried to expand each part locally).
Signature · 5 lines
Robin Hugh Johnson E-Mail : [email protected] Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 ICQ# : 30269588 or 41961639 GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
Re: [PATCH] Add sendmail -f support to git-send-email.
In reply to Robin H. JohnsonQuoted 3 lines · Robin H. Johnson
Some mailing lists use the envelope sender instead of the actual from address, and this can be broken in git-send-email. This patch sets the -f argument to the sendmail binary, using the address of the patch author.
At least some MTAs (exim is the one I know for sure) can restrict -f usage to some users and deny it for others. Don't know how much this would really be a problem, but using -f unconditionally might be a bad idea none-the-less.
Gruesse,
Signature · 2 lines
Frank Lichtenheld <[email protected]> www: http://www.djpig.de/
Re: [PATCH] Add sendmail -f support to git-send-email.
Quoted 4 lines · Frank Lichtenheld
At least some MTAs (exim is the one I know for sure) can restrict -f usage to some users and deny it for others. Don't know how much this would really be a problem, but using -f unconditionally might be a bad idea none-the-less.
In those cases, the sendmail binary should fail gracefully, and then you know that at least your email isn't lost into the ether.
Signature · 4 lines
Robin Hugh Johnson Gentoo Linux Developer & Council Member E-Mail : [email protected] GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
Re: [PATCH] Add sendmail -f support to git-send-email.
In reply to Frank LichtenheldQuoted 9 lines · Frank Lichtenheld
Quoted 3 lines · Robin H. Johnson
Some mailing lists use the envelope sender instead of the actual from address, and this can be broken in git-send-email. This patch sets the -f argument to the sendmail binary, using the address of the patch author.
At least some MTAs (exim is the one I know for sure) can restrict -f usage to some users and deny it for others. Don't know how much this would really be a problem, but using -f unconditionally might be a bad idea none-the-less.
I thought I saw the '-f' patch somewhere on the list in the last several weeks and there was a discussion on this topic that followed the patch. Am I hallucinating, or was it not applied because there were some issues?
Re: [PATCH] Add sendmail -f support to git-send-email.
Quoted 12 lines · Junio C Hamano
Quoted 9 lines · Frank Lichtenheld
Quoted 3 lines · Robin H. Johnson
Some mailing lists use the envelope sender instead of the actual from address, and this can be broken in git-send-email. This patch sets the -f argument to the sendmail binary, using the address of the patch author.
At least some MTAs (exim is the one I know for sure) can restrict -f usage to some users and deny it for others. Don't know how much this would really be a problem, but using -f unconditionally might be a bad idea none-the-less.
Quoted 4 lines
I thought I saw the '-f' patch somewhere on the list in the last several weeks and there was a discussion on this topic that followed the patch. Am I hallucinating, or was it not applied because there were some issues?
Can't find anything in the archives. So either I completly suck at searching, or it is at least several months old, or you are hallucinating :)
Gruesse,
Signature · 2 lines
Frank Lichtenheld <[email protected]> www: http://www.djpig.de/
Re: [PATCH] Add sendmail -f support to git-send-email.
Quoted 7 lines · Frank Lichtenheld
Quoted 5 lines · Junio C Hamano
Frank Lichtenheld <[email protected]> writes:
I thought I saw the '-f' patch somewhere on the list in the last several weeks and there was a discussion on this topic that followed the patch. Am I hallucinating, or was it not applied because there were some issues?
Quoted 5 lines
Can't find anything in the archives. So either I completly suck at searching, or it is at least several months old, or you are hallucinating :)
Gruesse,
Se the thread starting with the mail
Message-ID: <[email protected]>
http://thread.gmane.org/gmane.comp.version-control.git/42927/
The discussion was about hooks--update, not git-send-mail.
/Lukas
Re: [PATCH] Add sendmail -f support to git-send-email.
In reply to Frank LichtenheldQuoted 8 lines · Frank Lichtenheld
Quoted 4 lines
I thought I saw the '-f' patch somewhere on the list in the last several weeks and there was a discussion on this topic that followed the patch. Am I hallucinating, or was it not applied because there were some issues?
Can't find anything in the archives. So either I completly suck at searching, or it is at least several months old, or you are hallucinating :)
It was the thread about update-hook that sends e-mail; the discussion ends here:
http://thread.gmane.org/gmane.comp.version-control.git/42927/focus=42996
The patch was from Jim Meyering that made the script to unconditionally pass -f '$envelope_sender'; it was not applied because the whole e-mail sending business was removed from the update hook.
We seem to do a "-f '$envelope_sender'" in the example 'post-receive' hook only when the configuration tells it to, so probably it is a good idea to follow suit in this program.
Quoted 3 lines · Robin H. Johnson
The only weirdness I saw in that, is that the envelope sender did not appear to be set correct from git-send-email. Give me a moment to explore down that path.
Ok, see my patch series for envelope sender, that is the source of the problem.
Signature · 5 lines
Robin Hugh Johnson E-Mail : [email protected] Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 ICQ# : 30269588 or 41961639 GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
Quoted 11 lines · Junio C Hamano
One thing that people need to be careful about is which SMTP server they use. I had an impression (I do not use send-email myself) that it defaulted to local MTA, so the mail trail would look like your local MTA receives from the MUA (which is send-email), which forwards it to whereever destination (or intermediaries). On the other hand, I suspect many people use their ISP's SMTP server when using their usual MUA, so the mail trail would look different. I do not know what filtering vger does, but if it is filtering based on the MTA address (dul.dnsbl.sorbs filtering comes to mind), that would make a difference.
I'm pretty sure the last time I tried git-send-email I had the MTA path exactly the same. My mutt sends to localhost, which forwards over an SSL channel to my colo'd spearce.org mail server, and that relays to the final destination. Hence spearce.org mail always originates from spearce.org.
Now I ran git-send-email on a different system, but had it connect over SMTP to port 25 of the same system mutt runs on, so the initial Received line was different, but othewrise the mail path was the same.
I also have a few other addresses that I can send to that will go out the spearce.org colo'd box to another SMTP system, then bounce back, and the round-trip was the same for anything from mutt and from git-send-email.
I marked the whole mess up to some mail header difference that git-send-email wasn't sending the same way mutt was, and that vger cared about. I didn't see the difference easily. I just gave up. ;-)
Signature · 1 line
Shawn.
Quoted 3 lines · Junio C Hamano
One thing that people need to be careful about is which SMTP server they use.
ABSOLUTELY!
There are a ton of spam blockers that simply *refuse* to accept email from people who just randomly send to port 25.
For example, I will personally never see email that comes directly to my email address though an open mail relay *or* from something that appears to be just a random botnet PC (I forget the exact rule, since I'm hapily ignorant of MIS, but I think it boils down to requiring a good reverse DNS lookup).
That's getting much more common. Most spam is done through botnets, and they still try to do the direct-to-port-25 thing, exactly because if you go through a *real* SMTP host, your ISP will generally shut you down pretty quickly if you're spamming.
So special spammers with their own machines will work with ISP's that don't care (they make money off the spammers), but botnets depend on cracked Windows machines, and those often have ISP's that *do* care, because they get complaints and it costs them money if they don't.
Quoted 4 lines
I had an impression (I do not use send-email myself) that it defaulted to local MTA, so the mail trail would look like your local MTA receives from the MUA (which is send-email), which forwards it to whereever destination (or intermediaries).
A lot of people configure their MUA to send specially, and never even configure their MTA at all apart from whatever default configuration it has.
For example, I may have sendmail installed on my machine, but its only purpose in life is to do *local* email delivery (using fetchmail -> sendmail). It wouldn't know how to send an email outside of the machine.
Instead, my MUA is configured to do this:
# List of SMTP servers for sending mail. If blank: Unix Pine uses sendmail. smtp-server=localhost:10025
where localhost port 10025 is just a ssh tunnel to inside the osdl network. If I tried to send email any other way, people would often not accept it, because various SMTP servers will simply *refuse* to forward emails that claim to be coming from a point that isn't somethign that they actually *receive* email for.
And I don't think my setup is at all unusual. I may be unusual in my choice of MUA, but most MUA's will have configuration for where to send the mail, and I think very few people actually configure sendmail to do it right.
So no, I don't think people should assume that "sendmail" magically knows how to send emails other than to the local machine (ie use it to send problem reports to "root", or let fetchmail deliver to it for local emails, but that's about it)
Linus
Quoted 9 lines · Linus Torvalds
Quoted 3 lines · Junio C Hamano
One thing that people need to be careful about is which SMTP server they use.
ABSOLUTELY!
Quoted 8 lines
There are a ton of spam blockers that simply *refuse* to accept email from people who just randomly send to port 25.
For example, I will personally never see email that comes directly to my email address though an open mail relay *or* from something that appears to be just a random botnet PC (I forget the exact rule, since I'm hapily ignorant of MIS, but I think it boils down to requiring a good reverse DNS lookup).
Depending on your definition of "good".
I run my mail server off my DSL line. I prefer having control over my mail server instead of being chained to what my ISP provides. (The problems of having been a sysadmin for way too many years.) I don't have control over the reverse ip address, but I do over my DNS resolution. (Well, most of it. A couple domains are sitting on really old dns servers from years past.)
Quoted 4 lines
That's getting much more common. Most spam is done through botnets, and they still try to do the direct-to-port-25 thing, exactly because if you go through a *real* SMTP host, your ISP will generally shut you down pretty quickly if you're spamming.
Which makes Greylisting a useful tool. However, some people define a "real SMTP host" as being the one your ISP provides and no other. No matter how good your OS or how stringent your rulesets for sending mail are.
Quoted 4 lines
So special spammers with their own machines will work with ISP's that don't care (they make money off the spammers), but botnets depend on cracked Windows machines, and those often have ISP's that *do* care, because they get complaints and it costs them money if they don't.
And the various RBL lists will just nuke everyone in the same class c. (I have seen it happen for people at colos. Someone on the class c get compromised, sends spam and the whole address space gets blocked. Sometimes I think the anti-spam methods are as obnoxious as the spammers. Almost.)
Quoted 8 lines
Quoted 4 lines
I had an impression (I do not use send-email myself) that it defaulted to local MTA, so the mail trail would look like your local MTA receives from the MUA (which is send-email), which forwards it to whereever destination (or intermediaries).
A lot of people configure their MUA to send specially, and never even configure their MTA at all apart from whatever default configuration it has.
But the people who use git are probably the exceptions. (At least I hope so...)
A number of programs assume that the local MTA can send mail. (The bug handling software for Gnome is an example of that.)
This sounds more like a distro problem though. The MTA configuration should be a proper part of an install, not something that you have to uncover and piece together later.
Of course I also believe that Sendmail configuration was designed by an organic chemistry major as part of an "experiment" in ergot derivitives.
Signature · 2 lines
"Invoking the supernatural can explain anything, and hence explains nothing."
- University of Utah bioengineering professor Gregory ClarkQuoted 8 lines · alan
Quoted 6 lines
For example, I will personally never see email that comes directly to my email address though an open mail relay *or* from something that appears to be just a random botnet PC (I forget the exact rule, since I'm hapily ignorant of MIS, but I think it boils down to requiring a good reverse DNS lookup).
Depending on your definition of "good".
Well, the most common case (and the thing I *think* our spam software does here) is to just confirm that the reverse DNS lookup (that you want to do *anyway* for the "Received" headers for the email) will resolve back to the same IP (aka "FCrDNS").
It's also possible to just not accept mail if the reverse lookup indicates that the sending IP address is a dynamic address, which you can sometimes see from the hostname. I would suggest you *not* name your hosts to contain a lot of numbers and the string "dhcp", for example ;)
Quoted 2 lines
Sometimes I think the anti-spam methods are as obnoxious as the spammers. Almost.)
I'll take strict anti-spam methods any day. I get about 10 pieces of spam a day, that I can handle easily without worrying about it. I shudder to even just think about what it used to be like before aggressive spam filtering.
So I'm personally *solidly* in the camp that says "if you want to send me email, it's worth making a conscious effort to not look like spam".
Linus
Quoted 17 lines · Linus Torvalds
Quoted 8 lines · alan
Quoted 6 lines
For example, I will personally never see email that comes directly to my email address though an open mail relay *or* from something that appears to be just a random botnet PC (I forget the exact rule, since I'm hapily ignorant of MIS, but I think it boils down to requiring a good reverse DNS lookup).
Depending on your definition of "good".
Well, the most common case (and the thing I *think* our spam software does here) is to just confirm that the reverse DNS lookup (that you want to do *anyway* for the "Received" headers for the email) will resolve back to the same IP (aka "FCrDNS").
Quoted 4 lines
It's also possible to just not accept mail if the reverse lookup indicates that the sending IP address is a dynamic address, which you can sometimes see from the hostname. I would suggest you *not* name your hosts to contain a lot of numbers and the string "dhcp", for example ;)
I actually have a fixed IP address.
Quoted 7 lines
Quoted 2 lines
Sometimes I think the anti-spam methods are as obnoxious as the spammers. Almost.)
I'll take strict anti-spam methods any day. I get about 10 pieces of spam a day, that I can handle easily without worrying about it. I shudder to even just think about what it used to be like before aggressive spam filtering.
Greylisting dropped my spam level by at least 90%. RBLs have, for the most part, had far too many false positives to be useful. (If it was just me, it would not be so bad, but my wife gets mail on this server as well. She is not so forgiving.)
Quoted 2 lines
So I'm personally *solidly* in the camp that says "if you want to send me email, it's worth making a conscious effort to not look like spam".
I try pretty hard. However, some anti-spam methods share some of the same methods with dowsing and other witchcraft. What "looks like spam" seems pretty subjective at times.
I do have a reason for being a bit negative about it. I once ran a very large development list back in the last century. A piece of spam got past my spam filters and onto the list. Some idiot got offended and reported me as a spammer (because my ip was the first thing he saw) and reported me to my isp and to my isp's upstream feed. Took me a couple days to get everyone calmed down. Excessive anti-spammers still get on my nerves after that incident.
Signature · 2 lines
"Invoking the supernatural can explain anything, and hence explains nothing."
- University of Utah bioengineering professor Gregory ClarkQuoted 4 lines · Linus Torvalds
It's also possible to just not accept mail if the reverse lookup indicates that the sending IP address is a dynamic address, which you can sometimes see from the hostname. I would suggest you *not* name your hosts to contain a lot of numbers and the string "dhcp", for example ;)
That would be a very bad idea I think. Doing that would lose quite a lot of small companies and individuals such as me that run a mail server but are unable to get the ISP to change the reverse DNS. For example I do have a fixed IP, but have an reverse DNS pointer which looks like 1-2-3-4-5a.foo.bar.bostream.se.
Forcing everybody to send mail through their ISP (and I'm not even sure if my ADSL subscription includes such a service) would be a big loss. First of all its a philosophical thing, I think that it's very important that small shops or individuals should be able to control the services they need, the internet is supposed to be peer to peer. Second because the ISP's mess up a lot more often than I do, for example Telia, one of the largest ISPs in Sweden have been having massive mail server problems during the last week which I'm happily unaffected by.
/Christer
Signature · 3 lines
"Just how much can I get away with and still go to heaven?" Christer Weinigel <[email protected]> http://www.weinigel.se
Quoted 7 lines · Christer Weinigel
Quoted 4 lines · Linus Torvalds
It's also possible to just not accept mail if the reverse lookup indicates that the sending IP address is a dynamic address, which you can sometimes see from the hostname. I would suggest you *not* name your hosts to contain a lot of numbers and the string "dhcp", for example ;)
Quoted 5 lines
That would be a very bad idea I think. Doing that would lose quite a lot of small companies and individuals such as me that run a mail server but are unable to get the ISP to change the reverse DNS. For example I do have a fixed IP, but have an reverse DNS pointer which looks like 1-2-3-4-5a.foo.bar.bostream.se.
I am in the same situation. I also have three domains. Which one do I pick? I can't afford to get an individual ip address for each. Virtual servers on a single ip also will have similar problems.
Quoted 9 lines
Forcing everybody to send mail through their ISP (and I'm not even sure if my ADSL subscription includes such a service) would be a big loss. First of all its a philosophical thing, I think that it's very important that small shops or individuals should be able to control the services they need, the internet is supposed to be peer to peer. Second because the ISP's mess up a lot more often than I do, for example Telia, one of the largest ISPs in Sweden have been having massive mail server problems during the last week which I'm happily unaffected by.
My ISP only reciently started to think about using greylisting. They route all their mail through a filter service that I do not trust. (Too many false positives. I also expect that all this talk about "forking children" would get me on some list somewhere.)
I have more experience running mail servers than the people at my ISP. (Not their fault. They are young.)
Signature · 2 lines
"Invoking the supernatural can explain anything, and hence explains nothing."
- University of Utah bioengineering professor Gregory ClarkQuoted 10 lines · alan
Quoted 7 lines · Christer Weinigel
Quoted 4 lines · Linus Torvalds
It's also possible to just not accept mail if the reverse lookup indicates that the sending IP address is a dynamic address, which you can sometimes see from the hostname. I would suggest you *not* name your hosts to contain a lot of numbers and the string "dhcp", for example ;)
Quoted 7 lines
Quoted 5 lines
That would be a very bad idea I think. Doing that would lose quite a lot of small companies and individuals such as me that run a mail server but are unable to get the ISP to change the reverse DNS. For example I do have a fixed IP, but have an reverse DNS pointer which looks like 1-2-3-4-5a.foo.bar.bostream.se.
I am in the same situation. I also have three domains. Which one do I pick? I can't afford to get an individual ip address for each. Virtual servers on a single ip also will have similar problems.
this isn't a problem. as long as you can lookup 1-2-3-4-5a.foo.bar.bostream.se. and get your IP address you pass this test.
David Lang
Quoted 21 lines · alan
Quoted 6 lines
For example, I will personally never see email that comes directly to my email address though an open mail relay *or* from something that appears to be just a random botnet PC (I forget the exact rule, since I'm hapily ignorant of MIS, but I think it boils down to requiring a good reverse DNS lookup).
Depending on your definition of "good".
I run my mail server off my DSL line. I prefer having control over my mail server instead of being chained to what my ISP provides. (The problems of having been a sysadmin for way too many years.) I don't have control over the reverse ip address, but I do over my DNS resolution. (Well, most of it. A couple domains are sitting on really old dns servers from years past.)
Quoted 4 lines
That's getting much more common. Most spam is done through botnets, and they still try to do the direct-to-port-25 thing, exactly because if you go through a *real* SMTP host, your ISP will generally shut you down pretty quickly if you're spamming.
Quoted 5 lines
Which makes Greylisting a useful tool. However, some people define a "real SMTP host" as being the one your ISP provides and no other. No matter how good your OS or how stringent your rulesets for sending mail are.
greylisting unfortunately requires "some maintenance" to keep it going well, and it also breaks some mail appliances and probably some MTA's that are completely compliant in retrying to send mails.
another tactic which is probably just as good if not better than greylisting is "nolisting", that is to have your primary mx point to a non-existant machine with a real ip-address and dns entries (or even a machine with a firewall that runs iptables that blackholes or does funky stuff to anything coming in on port 25 and then just drops the connections).
if the remote end is a compliant MTA it will failover to the secondary mx which is a real machine that receives mail. but it probably suffers from the same problem of mail appliances not being completely compliant to the specs on how MTA's should work.
nolisting offers almost as good effects as greylisting without the hassle of maintaining a list.
Jimmy.
Signature · 4 lines
Jimmy Tang Trinity Centre for High Performance Computing, Lloyd Building, Trinity College Dublin, Dublin 2, Ireland. http://www.tchpc.tcd.ie/ | http://www.tchpc.tcd.ie/~jtang
Hi,
Quoted 2 lines · Robin H. Johnson
Since shallow checkouts are now available, there's just one more thing that's missing: subtree checkouts. Not to be confused with sub-projects.
It should not be _that_ difficult. If I'm correct, it should touch exactly the same code as the commit v1.3.0~263^2~6 ("Assume unchanged" git).
ATM I have no time to do anything about it, so feel free to give it a try.
Ciao,
Dscho