Re: smtproutes and virtualdomains
Andy Abshagen [EMAIL PROTECTED] wrote: We are in the process of moving one our clients mail from our server to their own exchange server. What I need to know though is which takes precedence. The virtualdomains control file or the smtproutes control file. virtualdomains will take precedence; if it's in there, qmail knows it has to deliver messages locally rather than remotely. If you remove their domain from virtualdomains and put an smtproutes entry for them in, all mail for them which gets queued in the future will be forwarded to them -- messages which are currently queued and awaiting local delivery will not be affected, I think. Note that you'll still need to have their domain in rcpthosts if you want qmail-smtpd to accept mail destined for that domain. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: smtproutes and mail still in queue
On Fri, Jul 06, 2001 at 06:36:19AM +, Subba Rao wrote: Hi, My mail client is Mutt. Few days ago I have subscribed to their mailing list. Their list server is at gbnet.net. The list server attempts to authenticate my server by calling to identd. I have opened up ipchains to access identd for the gbnet.net domain and the mail is still the mail queue. Since my initial subscription (sometime ago) to Mutt list, I have added the gbnet.net in the /var/qmail/control/smtproutes file. The relaying server is my ISP's mail server. In this case, this mail should have left my system long time ago but it still remains in the mail queue. Why is it trying to authenticate my system via identd when the smtproutes has been defined for this domain? What do the logs say? Has qmail-send tried any deliveries to gbnet.net since you altered smtproutes?
Re: smtproutes and mail still in queue
On 0, Alex Pennace [EMAIL PROTECTED] wrote: On Fri, Jul 06, 2001 at 06:36:19AM +, Subba Rao wrote: Hi, My mail client is Mutt. Few days ago I have subscribed to their mailing list. Their list server is at gbnet.net. The list server attempts to authenticate my server by calling to identd. I have opened up ipchains to access identd for the gbnet.net domain and the mail is still the mail queue. Since my initial subscription (sometime ago) to Mutt list, I have added the gbnet.net in the /var/qmail/control/smtproutes file. The relaying server is my ISP's mail server. In this case, this mail should have left my system long time ago but it still remains in the mail queue. Why is it trying to authenticate my system via identd when the smtproutes has been defined for this domain? What do the logs say? Has qmail-send tried any deliveries to gbnet.net since you altered smtproutes? --- Jun 29 22:15:54 myhost qmail: 993852954.669066 starting delivery 65: msg 197156 to remote [EMAIL PROTECTED] Jun 29 22:15:54 myhost qmail: 993852954.670044 status: local 0/10 remote 1/20 Jun 29 22:15:55 myhost qmail: 993852955.514653 delivery 65: deferral: Connected_to_194.70.126.10_but_connection_died._(#4.4.2)/ Jun 29 22:15:55 myhost qmail: 993852955.515821 status: local 0/10 remote 0/20 Jun 29 22:22:35 myhost qmail: 993853355.538097 starting delivery 66: msg 197156 to remote [EMAIL PROTECTED] Jun 29 22:22:35 myhost qmail: 993853355.538447 status: local 0/10 remote 1/20 Jun 29 22:22:36 myhost qmail: 993853356.268755 delivery 66: deferral: Connected_to_194.70.126.10_but_connection_died._(#4.4.2)/ Jun 29 22:22:36 myhost qmail: 993853356.269908 status: local 0/10 remote 0/20 --- The following is from this morning. --- Jul 6 06:22:35 myhost qmail: 994400555.804312 starting delivery 59: msg 197156 to remote [EMAIL PROTECTED] Jul 6 06:22:35 myhost qmail: 994400555.804480 status: local 0/10 remote 1/20 Jul 6 06:22:45 myhost qmail: 994400565.356285 delivery 59: deferral: Connected_to_194.70.126.10_but_connection_died._(#4.4.2)/ Jul 6 06:22:45 myhost qmail: 994400565.356445 status: local 0/10 remote 0/20 --- The mail is still in the queue. Here is the output of mailq, 29 Jun 2001 22:15:54 GMT #197156 621 [EMAIL PROTECTED] remote [EMAIL PROTECTED] The smtproutes has the following entry: gbnet.net:mail.home.com I have tried the following too: .gbnet.net:mail.home.com -- Subba Rao [EMAIL PROTECTED] http://members.home.net/subba9/ GPG public key ID 27FC9217 Key fingerprint = 2B4C 498E 1860 5A2B 6570 5852 7527 882A 27FC 9217
RE: smtproutes and mail still in queue
My mail client is Mutt. Few days ago I have subscribed to their mailing list. Their list server is at gbnet.net. The list server attempts to authenticate my server by calling to identd. I have opened up ipchains to access identd for the gbnet.net domain and the mail is still the mail queue. Since my initial subscription (sometime ago) to Mutt list, I have added the gbnet.net in the /var/qmail/control/smtproutes file. The relaying server is my ISP's mail server. In this case, this mail should have left my system long time ago but it still remains in the mail queue. Why is it trying to authenticate my system via identd when the smtproutes has been defined for this domain? Thank you in advance for any help. -- Look at the recipients of mutt list messages. You subscribe to gbnet.net but the message recipients are @mutt.org You can post to @mutt.org too hope this help ~edu
Re: smtproutes and mail still in queue
On Fri, Jul 06, 2001 at 06:36:41AM +, Subba Rao wrote: Hi, My mail client is Mutt. Few days ago I have subscribed to their mailing list. Their list server is at gbnet.net. The list server attempts to authenticate my server by calling to identd. I have opened up ipchains to access identd for the gbnet.net domain and the mail is still the mail queue. Since my initial subscription (sometime ago) to Mutt list, I have added the gbnet.net in the /var/qmail/control/smtproutes file. The relaying server is my ISP's mail server. In this case, this mail should have left my system long time ago but it still remains in the mail queue. Why is it trying to authenticate my system via identd when the smtproutes has been defined for this domain? qmail does not ignore control files. Verify that /var/qmail/control/smtproutes contains the correct information (and is named correctly), restart qmail, send qmail-send an ALRM signal to retry all queued mail, and watch the mail fly off to your ISP. Thank you in advance for any help. NP. :) -- Greg White
Re: smtproutes
On Fri, Jan 26, 2001 at 08:31:49AM -0500, Steve Woolley wrote: I am planning to use smtproutes to route email from a qmail server to an internal Microsoft Exchange 5.5 server. If the Exchange server goes down for a period of time, will the qmail server cache (for lack of a better word) the routed emails locally until the Exchange server comes back up? or will the qmail server bounce the email back (after a given amount of time)? It will keep retrying for upto a week (with growing intervals). After that week, it will bounce the mail. Read up on queuelifetime in man qmail-send to see how to increase that period even more. Greetz, Peter.
RE: smtproutes
I have a redhat 7 \ qmail installation. I want to use this as a smtp frontend to send all messages to our exchange server. I have set smtproutes to smtp:exchange. When I send a message it gets delivered locally to me Make sure that the domain you are sending mail to is not listed in locals or virtualdomains, only rcpthosts and smtproutes. -- gowen -- Greg Owen -- [EMAIL PROTECTED] SoftLock.com is now DigitalGoods!
Re: smtproutes
Am Mittwoch, 3. Januar 2001 21:48 schrieben Sie: Hi, I have a redhat 7 \ qmail installation. I want to use this as a smtp frontend to send all messages to our exchange server. I have set smtproutes to smtp:exchange. When I send a message it gets delivered locally 1) Do NOT add the affected domain to locals, only to rcpthosts 2) your smtproutes-syntax is nonsens, use domain:host -- Henning Brauer | BS Web Services Hostmaster BSWS| Roedingsmarkt 14 [EMAIL PROTECTED] | 20459 Hamburg www.bsws.de| Germany
Re: smtproutes
In the previous episode (03.01.2001), Steve Hammond [EMAIL PROTECTED] said: I have set smtproutes to smtp:exchange. the syntax to send all mail (except for locals) to one host is: :that.one.host wolfgang
Re: smtproutes
Am Donnerstag, 4. Januar 2001 00:47 schrieb Wolfgang Zeikat: In the previous episode (03.01.2001), Steve Hammond [EMAIL PROTECTED] said: I have set smtproutes to smtp:exchange. the syntax to send all mail (except for locals) to one host is: :that.one.host Right, but this was not his intention. wolfgang -- Henning Brauer | BS Web Services Hostmaster BSWS| Roedingsmarkt 14 [EMAIL PROTECTED] | 20459 Hamburg www.bsws.de| Germany
Re: smtproutes - smtp server needs authenication
"CHIU, Jonathan" [EMAIL PROTECTED] writes: Originally I use smtproutes to route all outgoing messages to my isp smtp server. However, now, they set up rules to control email relaying. They implement smtp after pop. I need to login first before I can send out mail. Can anybody share with me your experiences? If they do that even when you're coming from their own network, my first suggestion would be to change to a better ISP. My second suggestion is to write a perl script which logs in to their POP server every time you connect, or run the script via cron every fifteen minutes or so. There are good examples in the documentation for the Net::POP3 module. Or you could use fetchmail for the same purpose. -- "I live in the heart of the machine. We are one."
Re: smtproutes
On Fri, 8 Dec 2000, Wolfgang Zeikat wrote: is it possible to have more than one smtproute for the same destination for the case that the first relay cannot be reached? if so, how? No. smtproutes is read in a "last best match wins" fashion. So if you have the entries: domain1.com:hosta.somewhere domain1.com:otherhost.elsewhere The first line will NEVER be used. If you really want the fallback behaviour, then use MX records - that's what they're for. Of course if you don't have control over the DNS entries, then you can't control the MX records. You could use a load balancing dns server such as Dan's pickdns from his djbdns package. -- Regards Peter -- Peter Samuel[EMAIL PROTECTED] http://www.e-smith.org (development)http://www.e-smith.com (corporate) Phone: +1 613 368 4398 Fax: +1 613 564 7739 e-smith, inc. 1500-150 Metcalfe St, Ottawa, ON K2P 1P1 Canada "If you kill all your unhappy customers, you'll only have happy ones left"
Re: smtproutes?
* Ed Weinberg [EMAIL PROTECTED] [001204 10:47]: Where is the format for entries in smtproutes defined? man qmail-remote /pg -- Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED] --- If you lived in the Dark Ages and you were a catapult operator, I bet the most common question people would ask is: Can't you make it shoot farther? 'No, I'm sorry. That's as far as it shoots.' (Jack Handey)
Re: smtproutes examples ?
On Sun, Sep 03, 2000 at 08:05:43AM +0200, mailing wrote: Hello, Could someone possibly send a few control/smtproutes examples, I haven't been able to find much info in the docs. man 8 qmail-remote Is it possible to forward all mail for adomain.com to mailserver.domain.com using this ? Yes, it is. RC -- +--- | Ricardo Cerqueira | PGP Key fingerprint - B7 05 13 CE 48 0A BF 1E 87 21 83 DB 28 DE 03 42 | Novis - Engenharia ISP / Rede Técnica | Pç. Duque Saldanha, 1, 7º E / 1050-094 Lisboa / Portugal | Tel: +351 21 010 - Fax: +351 21 011 PGP signature
Re: smtproutes not working!
J [EMAIL PROTECTED] wrote: I have an smtproutes file that contains the following: smtproutes: chatfish.org:barbuda.chatfish.com chatfish.net:barbuda.chatfish.com I've also tried to use the ip address: chatfish.org:[216.7.16.196] chatfish.net:[216.7.16.196] Both of these methods are being ignored by qmail. Qmail is taking the MX record before it looks at smtproutes. Any idea what I'm doing wrong? Note the smtproutes entries you have are for "chatfish.org" and "chatfish.net" _only_. If mail comes for anyone at "host.chatfish.org" or similar, MX records will be looked up as usual. Or perhaps you didn't restart qmail after making the changes? Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: smtproutes not working!
On Mon, Aug 14, 2000 at 12:12:37PM -0700, J wrote: I have an smtproutes file that contains the following: smtproutes: chatfish.org:barbuda.chatfish.com chatfish.net:barbuda.chatfish.com I've also tried to use the ip address: chatfish.org:[216.7.16.196] chatfish.net:[216.7.16.196] Both of these methods are being ignored by qmail. Qmail is taking the MX record before it looks at smtproutes. Any idea what I'm doing wrong? Show us some logs and qmail-showctl. qmail-remote is known to work as advertised wrt smtproutes. Regards.
Re: smtproutes not working!
Note the smtproutes entries you have are for "chatfish.org" and "chatfish.net" _only_. If mail comes for anyone at "host.chatfish.org" or similar, MX records will be looked up as usual. That's a good point. Or perhaps you didn't restart qmail after making the changes? That's a bad point. Each invocation of qmail-remote looks at this file so restarting qmail will not change a thing. Mark.
Re: smtproutes not working!
On Mon, Aug 14, 2000 at 01:17:45PM -0600, Charles Cazabon wrote: J [EMAIL PROTECTED] wrote: I have an smtproutes file that contains the following: smtproutes: chatfish.org:barbuda.chatfish.com chatfish.net:barbuda.chatfish.com I've also tried to use the ip address: chatfish.org:[216.7.16.196] chatfish.net:[216.7.16.196] Both of these methods are being ignored by qmail. Qmail is taking the MX record before it looks at smtproutes. Any idea what I'm doing wrong? Note the smtproutes entries you have are for "chatfish.org" and "chatfish.net" _only_. If mail comes for anyone at "host.chatfish.org" or similar, MX records will be looked up as usual. Or perhaps you didn't restart qmail after making the changes? You don't need to. qmail-remote reads smtproutes for every invocation. Chris
Re: smtproutes not working!
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Or perhaps you didn't restart qmail after making the changes? That's a bad point. Each invocation of qmail-remote looks at this file so restarting qmail will not change a thing. My bad. I can never recall offhand the exact configuration changes which require a restart of qmail. In this case, it's unnecessary -- but it won't hurt him, either. It's not like rebooting the machine :). Thanks for the correction. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: smtproutes
On Tue, Aug 01, 2000 at 11:05:18AM -0700, Jacob Scott wrote: I would like to bounce all mail incoming to my qmail machine (which is qmail.domain.com) for domain.com to mail.domain.com while i set up my server. What would this look like in smtproutes? I don't see this file in my control files, and I didnt see it in the install docs. Can anyone point me towards the answer/tell me which M to RTF? man qmail-control This man page tells you which man page each file in /var/qmail/control is referenced under. This is mentioned in the install, but is generally not absorbed during the initial learning curve. John
Re: smtproutes and From-Address
* Moritz Jodeit [EMAIL PROTECTED] writes: Is there a way, how I could change the From-address from [EMAIL PROTECTED] to [EMAIL PROTECTED]? The From-address should only be changed for mail to the internet. Local mail should still be delivered as [EMAIL PROTECTED] ,[ /var/qmail/doc/FAQ ] | 2.4. How do I set up a separate queue for a SLIP/PPP link? | | Answer: Use serialmail (http://pobox.com/~djb/serialmail.html). ` Then read about masquerading. -- Robin S. Socha http://socha.net/
Re: smtproutes
Martin Roest [EMAIL PROTECTED] wrote: Is it possible to create user-based smtproutes like: [EMAIL PROTECTED]:foo I need to route every mailaddr in the domain to another mailserver except one. No, but you can get the same effect using virtualdomains. In control/virtualdomains, put: [EMAIL PROTECTED]:alias-someaddr In control/smtproutes, put: somedomain.com:foo In ~alias/.qmail-someaddr, put: |forward someaddr@[IP of somedomain.com] -Dave
Re: SMTProutes - how to use them?
On Mon, Jan 31, 2000 at 02:40:51PM +0800, Michael Boman wrote: man qmail-remote How do I use SMTPRoutes? Please advice Michael Boman -- See complete headers for more info
Re: smtproutes and MX aliases
Matt, If you can get them to give you an IP address you're set. Use the IP address in smtproutes instead of the name. -Martin On 24 Nov, Matthew Harrell wrote: : : Hi, : I'm working on a mail system for a company and AOL has agreed to give : them access through a backdoor to avoid the AOL filter rules. I know it's : kind of a shady thing but you wouldn't believe the general stupidity I've seen : with filter rules. Anyway, AOL would like all their email to go to : partner.aol.com instead of the usual aol.com. The problem with setting it : up in smtproutes like : : aol.com:partner.aol.com : : is that partner.aol.com has only MX records and no A records so it bounces. : I'm sure someone has asked this before but is there any way I can get it to : use partner.aol.com or am I forced to edit the code and make it check for MX : records also? : : Thanks : -- Martin A. Brown --- SecurePipe Communications --- [EMAIL PROTECTED]
Re: smtproutes and MX aliases
: If you can get them to give you an IP address you're set. Use the IP : address in smtproutes instead of the name. Actually, I should have mentioned something about this. The MX address actually points to four addresses and knowing how frequently AOL machines go down I'm hesitant to force all my mail through one of them. It would be fine if I could do aol.com:mx1.aol.com,mx2.aol.com and I haven't tried it but I haven't see anything written about it. -- Matthew Harrell Programmer - a red-eyed mumbling Bit Twiddlers, Inc. mammal capable of conversing with [EMAIL PROTECTED] inanimate objects.
Re: smtproutes and MX aliases
Anyway, AOL would like all their email to go to partner.aol.com instead of the usual aol.com. The problem with setting it up in smtproutes like aol.com:partner.aol.com is that partner.aol.com has only MX records and no A records so it bounces. I'm confused. Is the mail supposed to go to [EMAIL PROTECTED] rather than [EMAIL PROTECTED], or are you just supposed to route the mail through the partner MXes but leave the RCPT TO addresses unchanged? In the latter case, unless you plan to send a truly stupendous amount of mail, I'd just pick one of the partner MXes and put that in SMTProutes. In the former case, you put aol.com in your local virtualdomains file and write a little .qmail-default that remails everything to "$[EMAIL PROTECTED]". Regards, John Levine, [EMAIL PROTECTED], Primary Perpetrator of "The Internet for Dummies", Information Superhighwayman wanna-be, http://iecc.com/johnl, Sewer Commissioner Finger for PGP key, f'print = 3A 5B D0 3F D9 A0 6A A4 2D AC 1E 9E A6 36 A3 47 PS: Can we all do that to get around AOL's filters, too?
Re: smtproutes and MX aliases
: I'm confused. Is the mail supposed to go to [EMAIL PROTECTED] rather : than [EMAIL PROTECTED], or are you just supposed to route the mail through the : partner MXes but leave the RCPT TO addresses unchanged? : In the latter case, unless you plan to send a truly stupendous amount of : mail, I'd just pick one of the partner MXes and put that in SMTProutes. Well, it will be bunches of 200K recipient messages going out and I've know AOL's mail routers so go down for over a day. Since this is time sensitive material I can't really get away with waiting for a machine to come back up. I would much rather prefer to have at least two of them available. Maybe I'll just dig out the source to qmail-remote (?) and see if I can get it to check for a MX record if an A record doesn't exist. Yes, BTW, the mail will be routed to partner.aol.com but will still have the form [EMAIL PROTECTED] : PS: Can we all do that to get around AOL's filters, too? No, according to them they need the IP's of the machines which will be sending mail. Of course I haven't actually tested that so I don't know what it does. -- Matthew Harrell Another Month's End: Bit Twiddlers, Inc. All Targets Met [EMAIL PROTECTED]All Systems Working All Customers Satisfied All Staff Enthusiastic All Pigs Fed And Ready To Fly
Re: smtproutes and MX aliases
In a message dated 11/24/99 3:49:46 PM Eastern Standard Time, [EMAIL PROTECTED] writes: : PS: Can we all do that to get around AOL's filters, too? No, according to them they need the IP's of the machines which will be sending mail. Of course I haven't actually tested that so I don't know what it does. What filters is it "getting past"? ___ --Mike "Life moves pretty quickly, if you don't stop and look around you might miss it" - Ferris Buler ___
Re: smtproutes and MX aliases
: : No, according to them they need the IP's of the machines which will be sending : : mail. Of course I haven't actually tested that so I don't know what it does. : What filters is it "getting past"? My contact there claims it gets past the internal ones the users set up - not the ones that AOL sets up. I've been given this stuff by the company I'm working for but it sounds like they have a partnership agreement which, for some reason, allows bypassing these rules. I haven't actually tried it yet due to this smtproutes problem and I don't have an AOL account to test it on that side. It would be nice for the inordinately large number of people who complain that they aren't getting our daily messages but yet have their filters so restrictive that we can't even reply to them. -- Matthew Harrell "Think of it as evolution in action" Bit Twiddlers, Inc. [EMAIL PROTECTED]
Re: smtproutes and MX aliases
On Wed, Nov 24, 1999 at 02:20:53PM -0500, Matthew Harrell wrote: : If you can get them to give you an IP address you're set. Use the IP : address in smtproutes instead of the name. Actually, I should have mentioned something about this. The MX address actually points to four addresses and knowing how frequently AOL machines go down I'm hesitant to force all my mail through one of them. It would be fine if I could do aol.com:mx1.aol.com,mx2.aol.com and I haven't tried it but I haven't see anything written about it. Why don't you set up a name like aolmail.bittwiddlers.com pointing round-robin-wise at all four of the IP addresses, and stick that name in smtproutes? Chris
Re: smtproutes and MX aliases
: Why don't you set up a name like aolmail.bittwiddlers.com pointing : round-robin-wise at all four of the IP addresses, and stick that name in : smtproutes? Good idea. I hadn't thought of that one. Hopefully they won't change the addresses often but it should work until I can think of something else I might want to try. Thanks -- Matthew Harrell To err is human, Bit Twiddlers, Inc. to purr feline. [EMAIL PROTECTED]
Re: smtproutes per user
Yes. My smtproutes file looks like this. ieee.org:gemini.ieee.org lists.io.com:lists.io.com suse.com:mail.suse.com :mail.texas.net Note the default address at the end (empty string on the left hand side of the colon matches anything. I route solely by domain, nothing user-specific though certainly you can do that. These are not prefixes, but patterns. HTH, Jeff Quoting A.Y. Sjarifuddin [EMAIL PROTECTED]: Dear All, Does smtproutes could route specific email to a specific server: email for user with prefix ~a.. to ~p... will be delivered to mail server A. email for user with prefix ~q.. to ~z... will be delivered to mail server B. so it will be something like: a-p@domain:[IP Address] q-z@domain:[IP Address] Thanks in advance Ayip.
Re: smtproutes per user
On Wed, 27 Oct 1999, A.Y. Sjarifuddin wrote:
Does smtproutes could route specific email to a specific server:
[...]
a-p@domain:[IP Address]
q-z@domain:[IP Address]
You cannot do this, because control/smtproutes is handled by
qmail-remote(8). It checks the first argument against control/smtproutes'
first column. Here's the excerpt from the appropriate man page:
SYNOPSIS
qmail-remote host sender recip [ recip ... ]
You have to use control/virtualdomains and a selector script like this:
control/virtualdomains:
domain:domainprocessor
~alias/.qmail-domain-default:
domain/
~alias/.qmail-domainprocessor-default:
|qsmhook -x domainprocessor- -lnP /var/qmail/bin/qmail-inject
`/var/qmail/bin/sforwarder %u %h`
/var/qmail/bin/sforwarder:
#!/usr/bin/perl
($user, $domain) = @ARGV;
open(I,"/var/qmail/alias/domains-$domain");
while(I) {
s/^([^#]*)#.*$/$1/;
next unless ($rx, $host) =~ (/^(.+) ([a-zA-Z.-]+)\s*$/);
if ($user =~ /${rx}/) {
print "$user\@$host\n";
close I;
exit;
}
}
print "$domain-$user\n";
close I;
/var/qmail/alias/domains-domain:
^albert$ mail.albert.com # albert wants his own mail
^[a-k].+ ahost.domain.com # ahost does users a-k
#^z.+ zone.domain.com # this zone is currently down
.+ masshost.domain.com # for old users
Ps: Iam curious if it works IRL (in the real life). I tested just the perl
module.
--
Regards: Kevin (Balazs) @ synergon
Re: smtproutes - possible without DNS ?
"Olivier M." [EMAIL PROTECTED] wrote: HOST1 = SCO Unix with qmail and a few scripts that are sending emails to the realworld via a relay. No dns access, subnet. IP = 192.168.0.50 In /var/qmail/control/smtproutes, I have : :[192.168.0.10] HOST2 = linux server, with normal qmail configuration, allowing relaying for 192.*. World acces. Should act as relay. IP = 192.168.0.10 Now, when I try to send a mail to [EMAIL PROTECTED] from the Host1, I get this in syslog : Jul 21 21:38:50 qmail qmail: 932593130.64 new msg 50584 Jul 21 21:38:50 qmail qmail: 932593130.64 info msg 50584: bytes 265 from [EMAIL PROTECTED] qp 840 uid 0 Jul 21 21:38:50 qmail qmail: 932593130.84 starting delivery 13: msg 50584 to remote [EMAIL PROTECTED] It's not using your smtproutes file. Check the spelling and permissions. If you still don't see a problem, try running qmail-remote under your system call tracing tool (trace/truss/strace/par/etc.) There is a connexion made to the relay, because in the log of Host2,I see : Jul 21 23:39:05 webima smtpd: 932593145.632655 tcpserver: status: 13/40 Jul 21 23:39:05 webima smtpd: 932593145.640848 tcpserver: pid 3890 from 192.168.0.90 192.168.0.90 isn't HOST1, is it? -Dave
Re: smtproutes failover
On the qmail list [EMAIL PROTECTED] wrote: On Mon, May 10, 1999 at 05:09:25PM -0400, Jason wrote: [...] if it fails trying to send to the first host (10.1.1.1), qmail will try sending it to the second host (10.1.1.2) No. Could be useful ... wouldn't it be easy, though, since MXs already work like that ? In the code that looks for MXs, you'd just have to consider smtproutes if there exists one for the destination, with a value related to its position in the file. Disclaimer: haven't looked at the code. -- #include std_disclaim.h Lorens Kockum
Re: smtproutes
On Mon, Mar 08, 1999 at 05:39:48PM +0100, Harald Hanche-Olsen wrote: - Mate Wierdl [EMAIL PROTECTED]: | Suppose I have a box running qmail on a home network without DNS. | How can I route all remote messages to another box on the home | network? | | Would putting | | :[1.2.3.4] | | in smtproutes work, where 1.2.3.4. is the remote box's IP on the | home network. I think you would need to patch qmail-remote to skip the CNAME lookups, or provide a fake dns_cname() that does no actual lookup. So with stock qmail, I *must* have DNS? -- --- Mate Wierdl | Dept. of Math. Sciences | University of Memphis
Re: smtproutes
On Mon, Mar 08, 1999 at 10:38:12PM +0530, Sameer Vijay wrote: Hi! I would suggest that you put the name and ip (1.2.3.4) in /etc/hosts and put the name in the smtproutes :remote.host I am not sure whether putting brackets there will help. just the IP should suffice, if you want to put ip there. If what you suggest is supposed to work, then I am confused: having :remote.host in smtproutes does not require a DNS lookup of remote.host? -- --- Mate Wierdl | Dept. of Math. Sciences | University of Memphis
Re: smtproutes
Mate Wierdl writes: So with stock qmail, I *must* have DNS? Correct. If you don't have DNS running, your network must be so small that putting a few lines into control/smtproutes shouldn't be much of a hassle. -- Sam
Re: smtproutes
On Mon, Mar 08, 1999 at 10:47:01PM +, Sam wrote: Mate Wierdl writes: So with stock qmail, I *must* have DNS? Correct. If you don't have DNS running, your network must be so small that putting a few lines into control/smtproutes shouldn't be much of a hassle. This is exzactly my question: suppose I have only two machines, box1.home, and box2.home. Can I just put :box2.home in smtproutes on box1.home to direct all remote mail to box2---though box2.home is in only /etc/hosts? Also, is the syntax :[1.2.3.4] valid, if 1.2.3.4 is the IP of box2.home? Thx Mate
Re: smtproutes
Mate Wierdl wrote/schrieb/scribsit: Also, is the syntax :[1.2.3.4] valid, if 1.2.3.4 is the IP of box2.home? Yes. No need for DNS here. Stefan
Re: smtproutes
Mate Wierdl writes: This is exzactly my question: suppose I have only two machines, box1.home, and box2.home. Can I just put :box2.home in smtproutes on box1.home to direct all remote mail to box2---though box2.home is in only /etc/hosts? No - you must use the IP address. Also, is the syntax :[1.2.3.4] valid, if 1.2.3.4 is the IP of box2.home? That's it. Actually: box1.home:[1.2.3.4] is probably better. -- Sam
