[Mailman-Users] discard messages to 'mailman' list
Hi, I have problems to find the answer to this question: how can I discard messages that were posted to the 'mailman' list? When I visit the URL in the message with subject 30 Mailman moderator request(s) waiting, which ends in /mailman/admindb/mailman, I'm being redirected to the listinfo page. Is there a command line tool for this? Thank you, Arjen van Drie. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] discard messages to 'mailman' list
arjen van drie wrote: how can I discard messages that were posted to the 'mailman' list? When I visit the URL in the message with subject 30 Mailman moderator request(s) waiting, which ends in You may want to at least glance through the messages in there, since that is where users send messages when they are having trouble with the server. (Or set it so that messages from non-members are not held, but accepted.) /mailman/admindb/mailman, I'm being redirected to the listinfo page. Is there a command line tool for this? It sounds like you have an Apache rewrite rule that is matching too generously. If you want to use a rewrite rule to redirect visitors to http://www.example.com/mailman on to the listinfo page, make sure it doesn't also match /mailman/admindb/mailman. Try something like: RedirectMatch ^/mailman[/]*$ http://www.example.com/mailman/listinfo -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Has anyone successfully installed Mailman onFedora Core 2?
Brad == Brad Knowles [EMAIL PROTECTED] writes: At 1:03 PM +0900 2004-11-30, Stephen J. Turnbull wrote: AC_CHECK_HEADER(Python.h, , got_python_h=yes)]) if test $got_python_h != yes -a $os = linux; then echo 'If you're on Linux, you have the binary distro no -devel rpm bug!' echo 'Switch to an Industrial-Strength OS such as NetBSD immediately!' echo 'Gentoo Linux will do, too.' Brad But then you have to do this for every OS in Brad existence. You'd have to wrap a conditional of this sort Brad around every single file that building Mailman might Brad require, but which is not included as part of Mailman Brad itself. Of course you don't. The point is to test for one specific kind of brain damage that is well-known, very common, and even bites people who know what they're doing, not to mention being very confusing for newbies. You can leave out the test for Linux, and simply say If you don't even have Python.h, you probably are missing many, many files required to build Mailman. Perhaps your OS has separate 'development' packages? The problem is not to build a fool-proof safety net; I'll put my money on the fool, every time. The point is to forestall one particular FAQ. Brad I'm sorry, but this is a totally non-scalable Brad suggestion. If all we had to do was to support a single OS, Brad that would be fine. But we can't do everyone's job for Brad them, and if the RPM builders want to have multiple Brad different versions of Python (or whatever else Mailman might Brad depend on), then they need to take the responsibility of Brad dealing with the resulting issues. Wishful thinking. By allocating the headers to the devel packages, they've already indicated that in their opinion it's somebody else's problem. I dunno what Messrs. Warsaw et cie. think, but in my experience this kind of hacking pays of in noticably reduced user frustration and somewhat reduced FAQmeister effort. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of TsukubaTennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can do free software business; ask what your business can do for free software. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] discard messages to 'mailman' list
Jim Tittsler wrote: arjen van drie wrote: how can I discard messages that were posted to the 'mailman' list? When I visit the URL in the message with subject 30 Mailman moderator request(s) waiting, which ends in You may want to at least glance through the messages in there, since that is where users send messages when they are having trouble with the server. (Or set it so that messages from non-members are not held, but accepted.) /mailman/admindb/mailman, I'm being redirected to the listinfo page. Is there a command line tool for this? It sounds like you have an Apache rewrite rule that is matching too generously. If you want to use a rewrite rule to redirect visitors to http://www.example.com/mailman on to the listinfo page, make sure it doesn't also match /mailman/admindb/mailman. Try something like: RedirectMatch ^/mailman[/]*$ http://www.example.com/mailman/listinfo Of course, I never thought of this, I was looking at mailman internals, not at the webserver that handles the URLs. Thanks a lot, it works now. Arjen. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Unknown user- what am I missing?
At 6:48 PM -0800 2004-11-30, Zain Memon wrote: The log entry for the speakeasy one looks like this: to=speakeasy.net, relay=virtual, delay=0, status=bounced (unknown user: speakeasy.net) This means that the e-mail address is not valid. Either that, or the speakeasy.net mail servers are screwed up and rejecting messages that they should be accepting. Either way, this isn't your problem. Now I think I'm missing some critical concept here. How did my mail server know what the gmail relay was? And why doesn't it know the relay for speakeasy? Mail servers for a given domain are advertised in the DNS using a mechanism called MX Resource Records, sometimes known as MX RRs or just plain MXes. In theory, every server or domain that is supposed to accept mail should have advertised MXes in their DNS. If you want to go to their web pages, you look up www.gmail.com in the DNS (or whatever their webserver name is), if you want to send them mail, you look up their MXes. Here's what the mail servers look like for gmail.com: % dig gmail.com. mx ; DiG 9.2.2 gmail.com. mx ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 30055 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 7 ;; QUESTION SECTION: ;gmail.com. IN MX ;; ANSWER SECTION: gmail.com. 2633IN MX 20 gsmtp57.google.com. gmail.com. 2633IN MX 10 gsmtp171.google.com. gmail.com. 2633IN MX 10 gsmtp185.google.com. ;; AUTHORITY SECTION: gmail.com. 10750 IN NS ns1.google.com. gmail.com. 10750 IN NS ns2.google.com. gmail.com. 10750 IN NS ns3.google.com. gmail.com. 10750 IN NS ns4.google.com. ;; ADDITIONAL SECTION: gsmtp57.google.com. 1848IN A 216.239.57.27 gsmtp171.google.com.1663IN A 64.233.171.27 gsmtp185.google.com.6233IN A 64.233.185.27 ns1.google.com. 181084 IN A 216.239.32.10 ns2.google.com. 8284IN A 216.239.34.10 ns3.google.com. 181084 IN A 216.239.36.10 ns4.google.com. 181084 IN A 216.239.38.10 ;; Query time: 228 msec ;; WHEN: Wed Dec 1 10:45:35 2004 ;; MSG SIZE rcvd: 292 This says that gmail.com has two advertised primary MXes (gsmtp171.google.com and gsmtp185.google.com, each with a cost of 10), one secondary MX (gsmtp57.google.com with a cost of 20), four advertised nameservers, and then for convenience they also go ahead and give you the IP addresses for each of the machines. If you were to try to send e-mail to gmail.com, your server should do the same type of DNS query, and assuming it got back the same answer, then it should try to contact either gsmtp171 or gsmtp185, and it should randomly choose which one to try first. If it failed to contact either of the primary MXes, then it should fall back to the secondary. The integer numbers between the host/domain name and IN is the Time To Live, a.k.a., the TTL. This basically says how long the nameserver should cache this information before it re-queries from the appropriate nameservers for gmail.com/google.com. Note that the MX records shown have a low TTL of 2633 seconds (43 minutes and 53 seconds), while the NS records have a higher TTL of 10750 seconds (2 hours, 59 minutes, 10 seconds), and there are a wide range of TTLs for the various IP addresses. Some domains choose to have low TTLs for their advertised MXes as a crude way of load balancing across a large number of machines. Now, here's the MX records for speakeasy.net: % dig speakeasy.net. mx ; DiG 9.2.2 speakeasy.net. mx ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 10978 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 3 ;; QUESTION SECTION: ;speakeasy.net. IN MX ;; ANSWER SECTION: speakeasy.net. 3600IN MX 5 mx01.speakeasy.net. speakeasy.net. 3600IN MX 5 mx02.speakeasy.net. ;; AUTHORITY SECTION: speakeasy.net. 1344IN NS ns-noc.speakeasy.net. speakeasy.net. 1344IN NS ns-sea.speakeasy.net. ;; ADDITIONAL SECTION: mx01.speakeasy.net. 1344IN A 216.254.0.195 ns-noc.speakeasy.net. 7922IN A 216.254.0.173 ns-sea.speakeasy.net. 7922IN A 66.93.87.8 ;; Query time: 212 msec ;; WHEN: Wed Dec 1 10:56:38 2004 ;; MSG SIZE rcvd: 176 Summary: two mail servers of equal cost (mx01 and mx02), two nameservers (ns-noc and ns-sea), but the system currently only knows the IP addresses of three of these machines. If it wanted to talk to the fourth one, it would have to do another DNS query to get that information. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up
Re: [Mailman-Users] Has anyone successfully installed Mailman onFedora Core 2?
At 6:04 PM +0900 2004-12-01, Stephen J. Turnbull wrote: Of course you don't. The point is to test for one specific kind of brain damage that is well-known, very common, and even bites people who know what they're doing, not to mention being very confusing for newbies. That's a slippery slope. Today, it's python.h. Tomorrow it may be resolv.conf. At what point do you say that you can't possibly check for every single thing on which Mailman depends, and let people who have horribly b0rken machines find out the hard way? Wishful thinking. By allocating the headers to the devel packages, they've already indicated that in their opinion it's somebody else's problem. If that's the way they want to do business, they can get the same treatment as cPanel or MacOS X Server. I dunno what Messrs. Warsaw et cie. think, but in my experience this kind of hacking pays of in noticably reduced user frustration and somewhat reduced FAQmeister effort. Mailman is an open-source project. Feel free to post patches to the tracker on SourceForge. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Has anybody installed mailman on Solaris 9?
I have to install mailman on Solaris 9. Can anybody help me out? Yahoo! India Matrimony: Find your life partneronline. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Has anyone successfully installed Mailman onFedora Core 2?
Brad == Brad Knowles [EMAIL PROTECTED] writes: Wishful thinking. By allocating the headers to the devel packages, they've already indicated that in their opinion it's somebody else's problem. Brad If that's the way they want to do business, they can Brad get the same treatment as cPanel or MacOS X Server. Please, let's not. This is a case of difference of opinion on how to organize a distribution, not of cheating on the social contract. Brad Mailman is an open-source project. Feel free to post Brad patches to the tracker on SourceForge. I do feel free to do so, but it's unlikely to happen in this particular case. I don't understand the Mailman install process, so I'd have to work quite hard boning up. Somebody who already knows could probably write the patch in the same 60 seconds it took me to scratch out that autoconf stuff, though. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of TsukubaTennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can do free software business; ask what your business can do for free software. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Mailman on separate web and smtp load balanced farms.
On 11/30/2004 16:45, Brad Knowles [EMAIL PROTECTED] wrote: At 5:10 PM -0700 2004-11-30, Matt Ruzicka wrote: 1. How are people handling incoming mail to an SMTP server separate from the web server? MX records direct the mail traffic somewhere else. Or, the MX directs incoming mail to the farm, and the farm is configured to virus scan and spam-reduce it, then ship it off to a mail server on the Mailman machine. This works well for us (although I recently lost some of the spam reduction due to a configuration improvement which I think I fixed last night). The Mailman machine has the Mailman web server, as well. (The web server has another specialty task as well.) (I don't think we've used NFS since our founding as an ISP in 1993.) Thus, although we present the same sort of face to the world that you're talking about, the mailing list machine is in fact a normal, self-contained Mailman installation. For outbound list mail, the Mailman machine attempts delivery, and usually succeeds...for most temporary errors it forwards the message over to the mail server farm for retry handling (on the basis that some servers might like our regular servers but not the list server, which seems to be the case in practice). Note that we're a smaller operation than you are, Matt. --John -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Unknown user- what am I missing?
On 12/1/2004 1:58, Brad Knowles [EMAIL PROTECTED] wrote: The integer numbers between the host/domain name and IN is the Time To Live, a.k.a., the TTL. This basically says how long the nameserver should cache this information before it re-queries from the appropriate nameservers for gmail.com/google.com. Note that the MX records shown have a low TTL of 2633 seconds (43 minutes and 53 seconds), while the NS records have a higher TTL of 10750 seconds (2 hours, 59 minutes, 10 seconds), and there are a wide range of TTLs for the various IP addresses. Some domains choose to have low TTLs for their advertised MXes as a crude way of load balancing across a large number of machines. Note that these TTLs are local in the sense that they reflect the time the record has left to dwell in the cache of the name server that provided the answer, which usually isn't the authoritative server for an active domain (unless one never talks to gmail). (Try doing several dig commands a few minutes apart.) For example, a dig I did on one of our servers showed shorter times for the mail servers (I'm not including the whole result): ;; ADDITIONAL SECTION: gsmtp171.google.com.809 IN A 64.233.171.27 gsmtp185.google.com.809 IN A 64.233.185.27 gsmtp57.google.com. 809 IN A 216.239.57.27 (Just before sending this, the 809 times are down to 476.) --John -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Deleting a list
Hello, We just did a Linux version and Mailman version upgrade today. I had to copy over all my lists and configurations. I have lost the delete this list choice on the Mailman list administration page. I know by default this does not appear. I forget what the command or process is to activate this. I cannot find it in FAQs or documentation. Does anybody know the answer? Thanks, Bruce -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Deleting a list
rmlist --- Bruce N. Audie [EMAIL PROTECTED] wrote: Hello, We just did a Linux version and Mailman version upgrade today. I had to copy over all my lists and configurations. I have lost the delete this list choice on the Mailman list administration page. I know by default this does not appear. I forget what the command or process is to activate this. I cannot find it in FAQs or documentation. Does anybody know the answer? Thanks, Bruce -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Ok, I goofed.
I installed mailman on my company's mail server so we could manage our bulk outgoing mail with it. No problem, except one. I didn't notice I mis-spelled the domain name before I ran update. So now all messages are going out with that wrong domain. Is there a way I can go into the mailman config and find where it stored the domain wrong and fix it? i tried updating mm_cfg.py and running update again but it says there are no updates. Help? -- -- Dan -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Deleting a list
Hello, We just did a Linux version and Mailman version upgrade today. I had to copy over all my lists and configurations. I have lost the delete this list choice on the Mailman list administration page. I know by default this does not appear. I forget what the command or process is to activate this. I cannot find it in FAQs or documentation. Does anybody know the answer? Thanks, Bruce Hi again, I found this out only last week or the one before during my first ever setup of Mailman - add this to the bottom of mm_cfg.py: OWNERS_CAN_DELETE_THEIR_OWN_LISTS = Yes This will bring the option of list deletion up. -- Bye for now, Terry Allen ___ hEARd Postal Address: hEARd, 26B Glenning Rd, Glenning Valley, NSW 2261, Australia Internet - WWW: http://heard.com.au http://itavservices.com EMAIL: [EMAIL PROTECTED] Phone: Australia - 02 4388 1400 / International - + 61 2 43881400 Mobile: Australia - 04 28881400 / International - 61 4 28881400 --- Non profit promotion for new music - since 1994 --- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] sending mail to members in batches
Hi I'm wondering if there is a setting in mailman to send mail out to members of a list in batches - for example send 100, wait 30 seconds, send to the next 100, wait 30 seconds, and so on. The problem is we've got a list with 1000+ members, but there is a per-hour outgoing mail limit of 600 (and we'd rather not change it). This is a cPanel install (and from what I've heard, they distribute a custom version of mailman), but they don't have any settings I can change. I've seen the Exim tweaks and will be looking at implementing them, but I'm not sure if it'll be enough. I've had a look through all of the archives, and googled until my fingers bled (ok, not really), and the only thing I've found was a reference to what I think is another customised version of mailman or something completely different (it mentioned settings that I can't find anywhere). Any help appreciated, and if this is in an FAQ somewhere, then I do apologise. Thanks in advance Darryl -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Ok, I goofed.
Dan Egli wrote: I didn't notice I mis-spelled the domain name before I ran update. So now all messages are going out with that wrong domain. Is there a way I can go into the mailman config and find where it stored the domain wrong and fix it? i tried updating mm_cfg.py and running update again but it says there are no updates. Now that you've fixed mm_cfg.py, you have to run fix_url.py to fix your existing lists. See the following for help bin/fix_url.py bin/withlist --help -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] HTML Tokens
Peter Gysegem wrote: When editing the HTML for a MailMan web page, there are many tokens such as MM-List-Name. Is there a list anywhere of these tokens and what they do? I'm not aware of any list per se of the MM-* definitions, but the standard ones are defined in Mailman/HTMLFormatter.py and other specific ones are in Mailman/Cgi/listinfo.py, options.py, roster.py and subscribe.py. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Language options
Hello, Recently I set up a mailing list with members from many countries. My question is: if someone from France sets their messages to display in French, would a post from a subscriber in Brazil in Portuguese be automatically translated into French? Any information about this would be appreciated. Thanks, Marioca -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] sending mail to members in batches
At 11:00 AM +1300 2004-12-02, Darryl Hamilton wrote: I'm wondering if there is a setting in mailman to send mail out to members of a list in batches - for example send 100, wait 30 seconds, send to the next 100, wait 30 seconds, and so on. Nope. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.051.htp. This is a cPanel install (and from what I've heard, they distribute a custom version of mailman), but they don't have any settings I can change. Well, cPanel is rather problematic. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.011.htp. I've had a look through all of the archives, and googled until my fingers bled (ok, not really), and the only thing I've found was a reference to what I think is another customised version of mailman or something completely different (it mentioned settings that I can't find anywhere). Did you search the FAQ Wizard at http://www.python.org/cgi-bin/faqw-mm.py? If so, can you tell us what terms you used to search, but failed to turn up the entry mentioned above? If we're not putting the right keywords into the description, then we need to fix that. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Unknown user- what am I missing?
Thanks for the detailed info. I figured MXes were something like that. I ran the same command as you did, dig speakeasy.net. mx, and I got an output similar to yours. Still, I'm getting the same message in my maillog... Speakeasy.net is bouncing. If it was being bounced back by Speakeasy servers since the email isn't right, I would expect the maillog entry to at least have a speakeasy relay. I know for sure that the speakeasy email address is correct. I can get regular email on it. Since this is a production server, I can't really have some addresses that don't work; what can I do to get mail through to speakeasy? On Wed, 1 Dec 2004 10:58:20 +0100, Brad Knowles [EMAIL PROTECTED] wrote: At 6:48 PM -0800 2004-11-30, Zain Memon wrote: The log entry for the speakeasy one looks like this: to=speakeasy.net, relay=virtual, delay=0, status=bounced (unknown user: speakeasy.net) This means that the e-mail address is not valid. Either that, or the speakeasy.net mail servers are screwed up and rejecting messages that they should be accepting. Either way, this isn't your problem. Now I think I'm missing some critical concept here. How did my mail server know what the gmail relay was? And why doesn't it know the relay for speakeasy? Mail servers for a given domain are advertised in the DNS using a mechanism called MX Resource Records, sometimes known as MX RRs or just plain MXes. In theory, every server or domain that is supposed to accept mail should have advertised MXes in their DNS. If you want to go to their web pages, you look up www.gmail.com in the DNS (or whatever their webserver name is), if you want to send them mail, you look up their MXes. Here's what the mail servers look like for gmail.com: % dig gmail.com. mx ; DiG 9.2.2 gmail.com. mx ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 30055 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 7 ;; QUESTION SECTION: ;gmail.com. IN MX ;; ANSWER SECTION: gmail.com. 2633IN MX 20 gsmtp57.google.com. gmail.com. 2633IN MX 10 gsmtp171.google.com. gmail.com. 2633IN MX 10 gsmtp185.google.com. ;; AUTHORITY SECTION: gmail.com. 10750 IN NS ns1.google.com. gmail.com. 10750 IN NS ns2.google.com. gmail.com. 10750 IN NS ns3.google.com. gmail.com. 10750 IN NS ns4.google.com. ;; ADDITIONAL SECTION: gsmtp57.google.com. 1848IN A 216.239.57.27 gsmtp171.google.com.1663IN A 64.233.171.27 gsmtp185.google.com.6233IN A 64.233.185.27 ns1.google.com. 181084 IN A 216.239.32.10 ns2.google.com. 8284IN A 216.239.34.10 ns3.google.com. 181084 IN A 216.239.36.10 ns4.google.com. 181084 IN A 216.239.38.10 ;; Query time: 228 msec ;; WHEN: Wed Dec 1 10:45:35 2004 ;; MSG SIZE rcvd: 292 This says that gmail.com has two advertised primary MXes (gsmtp171.google.com and gsmtp185.google.com, each with a cost of 10), one secondary MX (gsmtp57.google.com with a cost of 20), four advertised nameservers, and then for convenience they also go ahead and give you the IP addresses for each of the machines. If you were to try to send e-mail to gmail.com, your server should do the same type of DNS query, and assuming it got back the same answer, then it should try to contact either gsmtp171 or gsmtp185, and it should randomly choose which one to try first. If it failed to contact either of the primary MXes, then it should fall back to the secondary. The integer numbers between the host/domain name and IN is the Time To Live, a.k.a., the TTL. This basically says how long the nameserver should cache this information before it re-queries from the appropriate nameservers for gmail.com/google.com. Note that the MX records shown have a low TTL of 2633 seconds (43 minutes and 53 seconds), while the NS records have a higher TTL of 10750 seconds (2 hours, 59 minutes, 10 seconds), and there are a wide range of TTLs for the various IP addresses. Some domains choose to have low TTLs for their advertised MXes as a crude way of load balancing across a large number of machines. Now, here's the MX records for speakeasy.net: % dig speakeasy.net. mx ; DiG 9.2.2 speakeasy.net. mx ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 10978 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 3 ;; QUESTION SECTION: ;speakeasy.net. IN MX ;; ANSWER SECTION: speakeasy.net. 3600IN MX 5 mx01.speakeasy.net. speakeasy.net. 3600
