Re: Relay IP address ranges - NEWBIE
Thanks for your help - all of you. Based on your advice, I nixed xinetd and tcpserver is happy as a clam - so it is reading its config files and forwarding is working. If/when I need ssh, I'll set that up with tcpserver.
Re: Relay IP address ranges - NEWBIE
On Fri, Jun 15, 2001 at 03:24:05PM -0500, Technology Strategic Planning, Inc. wrote: > OK, so both xinetd and tcpserver are running. I get the feeling that I > should pull xinetd out of the startup scripts. How will this effect apache > and other services (most epically bind)? > > I assume the two don't coexist well? (A logical push-me-pull-you?) They can coexist but not bind to the same port. > I have two instances of tcp server, both called with the command: > /usr/local/bin/tcpserver -H -R -v -p -x /etc/tcp.smtp.cdb -u 502 -g 501 0 > smtp /var/qmail/bin/qmail-smptd Two identical instances of tcpserver?? one them changing PID all the time?? There's most probably a problem with your start scripts and something (svscan?) tries to start it twice. If you want to control relay check /etc/tcp.smtp and the documentation for tcprules[1]. > xinetd is also running (one process). It's fine unless it doesn't try to bind to the same ports as tcpserver. Jörgen [1] http://cr.yp.to/ucspi-tcp/tcprules.html
Re: Relay IP address ranges - NEWBIE
For Apache and Bind do not care, they are stand alone servers, if you have an FTP, Telnet, or other service you have 2 options: disable it (safest), make a run script and run it from tcpsefver. Nazghul Microsoft is not the answer, its the question. And the answer is no. www.badran.co.uk - Original Message - From: "Technology Strategic Planning, Inc." <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, June 15, 2001 3:24 PM Subject: Re: Relay IP address ranges - NEWBIE > OK, so both xinetd and tcpserver are running. I get the feeling that I > should pull xinetd out of the startup scripts. How will this effect apache > and other services (most epically bind)? > > I assume the two don't coexist well? (A logical push-me-pull-you?) > > I have two instances of tcp server, both called with the command: > /usr/local/bin/tcpserver -H -R -v -p -x /etc/tcp.smtp.cdb -u 502 -g 501 0 > smtp /var/qmail/bin/qmail-smptd > > xinetd is also running (one process). > > The other services can go; (I'd like the ability to run a web server in a > pinch, however, the Mac can actually take care of that on an emergency basis > (which is all I want locally).), however I need DNS on the mail box for the > internal (NAT) DNS configuration. > > - Original Message - > From: "Charles Cazabon" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, June 15, 2001 2:04 PM > Subject: Re: Relay IP address ranges - NEWBIE > > > > Stephen Froehlich <[EMAIL PROTECTED]> wrote: > > > Config: > > > RedHat 7.1 > > > qmail - 1.0.3 > > > daemontools-0.70 > > > dot-forward-0.71 > > > ucspi-tcp-0.88 > > > > > > I'm having a helluva time figuring out how to allow my local hosts to > relay > > > mail through the server. I put the proper line in hosts.allow (per the > > > FAQ), however, I'm not familiar enough with xinetd to do the other edit > in > > > 5.4. > > > > Skip hosts.allow and xinetd altogether. You've already got ucspi-tcp and > > daemontools installed, which is far superior in any case. Then go to > > lifewithqmail.org and set up tcpserver/tcprules controls to allow > relaying. > > > > 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: Relay IP address ranges - NEWBIE
"Technology Strategic Planning, Inc." wrote: > > OK, so both xinetd and tcpserver are running. I get the feeling that I > should pull xinetd out of the startup scripts. How will this effect apache > and other services (most epically bind)? > > I assume the two don't coexist well? (A logical push-me-pull-you?) > > I have two instances of tcp server, both called with the command: > /usr/local/bin/tcpserver -H -R -v -p -x /etc/tcp.smtp.cdb -u 502 -g 501 0 > smtp /var/qmail/bin/qmail-smptd > > xinetd is also running (one process). > > The other services can go; (I'd like the ability to run a web server in a > pinch, however, the Mac can actually take care of that on an emergency basis > (which is all I want locally).), however I need DNS on the mail box for the > internal (NAT) DNS configuration. Just remove any e-mail related protocols from xinetd's conf files and send it a reload signal (SIGUSR1 if I remember correctly from my darker experiences with it). -- Nick (Keith) Fish Network Engineer Triton Technologies, Inc.
Re: Relay IP address ranges - NEWBIE
OK, so both xinetd and tcpserver are running. I get the feeling that I should pull xinetd out of the startup scripts. How will this effect apache and other services (most epically bind)? I assume the two don't coexist well? (A logical push-me-pull-you?) I have two instances of tcp server, both called with the command: /usr/local/bin/tcpserver -H -R -v -p -x /etc/tcp.smtp.cdb -u 502 -g 501 0 smtp /var/qmail/bin/qmail-smptd xinetd is also running (one process). The other services can go; (I'd like the ability to run a web server in a pinch, however, the Mac can actually take care of that on an emergency basis (which is all I want locally).), however I need DNS on the mail box for the internal (NAT) DNS configuration. - Original Message - From: "Charles Cazabon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, June 15, 2001 2:04 PM Subject: Re: Relay IP address ranges - NEWBIE > Stephen Froehlich <[EMAIL PROTECTED]> wrote: > > Config: > > RedHat 7.1 > > qmail - 1.0.3 > > daemontools-0.70 > > dot-forward-0.71 > > ucspi-tcp-0.88 > > > > I'm having a helluva time figuring out how to allow my local hosts to relay > > mail through the server. I put the proper line in hosts.allow (per the > > FAQ), however, I'm not familiar enough with xinetd to do the other edit in > > 5.4. > > Skip hosts.allow and xinetd altogether. You've already got ucspi-tcp and > daemontools installed, which is far superior in any case. Then go to > lifewithqmail.org and set up tcpserver/tcprules controls to allow relaying. > > 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: Relay IP address ranges - NEWBIE
Stephen Froehlich <[EMAIL PROTECTED]> wrote: > Config: > RedHat 7.1 > qmail - 1.0.3 > daemontools-0.70 > dot-forward-0.71 > ucspi-tcp-0.88 > > I'm having a helluva time figuring out how to allow my local hosts to relay > mail through the server. I put the proper line in hosts.allow (per the > FAQ), however, I'm not familiar enough with xinetd to do the other edit in > 5.4. Skip hosts.allow and xinetd altogether. You've already got ucspi-tcp and daemontools installed, which is far superior in any case. Then go to lifewithqmail.org and set up tcpserver/tcprules controls to allow relaying. 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: Relay IP address ranges - NEWBIE
On Fri, Jun 15, 2001 at 12:43:24PM -0500, Stephen Froehlich wrote: > Config: > RedHat 7.1 > qmail - 1.0.3 > daemontools-0.70 > dot-forward-0.71 > ucspi-tcp-0.88 > > I'm having a helluva time figuring out how to allow my local hosts to relay > mail through the server. I put the proper line in hosts.allow (per the > FAQ), however, I'm not familiar enough with xinetd to do the other edit in > 5.4. > > In other words, I'm lost - help? You mentioned both xinetd and ucspi-tcp, which one are you using?? Try: $ ps axw | tcpserver If you get an output post it, if not check the xinetd FAQ. Jörgen
Relay IP address ranges - NEWBIE
Config: RedHat 7.1 qmail - 1.0.3 daemontools-0.70 dot-forward-0.71 ucspi-tcp-0.88 I'm having a helluva time figuring out how to allow my local hosts to relay mail through the server. I put the proper line in hosts.allow (per the FAQ), however, I'm not familiar enough with xinetd to do the other edit in 5.4. In other words, I'm lost - help?
Re: binding qmail to a specific ip address
Leni Mayo writes: > I'm thinking along the lines of the apache "BindAddress" keyword, > so qmail would only use a specific ip address when listening and > as a source address for outbound connections. Sean showed how you can use tcpserver for listening. For outbound, you need to use the following patch. http:[EMAIL PROTECTED]">Markus Stumpf has a http://www.lamer.de/maex/creative/software/qmail/">pair of qmail patches, one to cause qmail-smtpd to log its disposition of mail, and another to convince qmail-remote to use a fixed IP address other than the one you get without binding to an address. Andy Repton has ported the fixed IP address patch to qmail 1.03. Damir Cifer has better instructions for his http://tycho.edico.si/linuxtnt/#qmail-patch">port. -- -russ nelson will be speaking at http://www.osdn.com/conferences/brie/ Crynwr sells support for free software | PGPok | Watch out! He's got an 521 Pleasant Valley Rd. | +1 315 268 1925 voice | opinion, and he's not Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | afraid to share it!
Re: binding qmail to a specific ip address
Check out tcpserver. Here's a run file that should be a start for 'ya: #!/bin/sh # Using tcpserver to listen to the internet exec env - PATH="/var/qmail/bin:$PATH" tcpserver -v -u 1003 -g 1002 192.168.1.1 smtp /var/qmail/bin/qmail-smtpd 2>&1 | /var/qmail/bin/splogger smtpd 3 -sc On Sat, Mar 31, 2001 at 09:05:16AM +1000, Leni Mayo wrote: > Delivered-To: [EMAIL PROTECTED] > Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm > Precedence: bulk > Delivered-To: mailing list [EMAIL PROTECTED] > Date: Sat, 31 Mar 2001 09:05:16 +1000 > From: Leni Mayo <[EMAIL PROTECTED]> > X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) > X-Accept-Language: en > To: [EMAIL PROTECTED] > Subject: binding qmail to a specific ip address > > I'm qmail running on a box with 2 network interface cards and want > to bind qmail to a specific IP address in order to simplify > firewall rules. > > I'm thinking along the lines of the apache "BindAddress" keyword, > so qmail would only use a specific ip address when listening and > as a source address for outbound connections. > > If anyone has a hack for qmail 1.03 along these lines, I'd love to > see a copy of the source. > > Leni. -- Sean Chittenden PGP signature
binding qmail to a specific ip address
I'm qmail running on a box with 2 network interface cards and want to bind qmail to a specific IP address in order to simplify firewall rules. I'm thinking along the lines of the apache "BindAddress" keyword, so qmail would only use a specific ip address when listening and as a source address for outbound connections. If anyone has a hack for qmail 1.03 along these lines, I'd love to see a copy of the source. Leni.
Re: IP ADDRESS
Cleiton L. Siqueira <[EMAIL PROTECTED]> wrote: > > The difference than the standart is that I have many different domains in my > server. And I check them through the SQL database (Postgres). I organize > different directories for each domain in the /home directory. For example, > if I have this domains in my system: example.com and sample.com I will have > two directories in /home directory like this: /home/example.com/ and > /home/sample.com/ and into these directories there will be the account of my > users. This sounds exactly like what vmailmgr does. It also sounds very similar to what vpopmail does. vmailmgr doesn't need an external database, either. > The script uses this information to delivery in the right directory, > depending on the domain. vmailmgr does this. > I'd like to know once more information. About the IP ADDRESS of SENDER. I > need to know what enviroment variable is responsible to keep the IP ADDRESS > of SENDER. Well, at delivery time, the sender's domain is set in an environment variable, but not the IP address. The IP address is of course available in the Received: line that qmail adds when it accepts the message. Your script could simply look at the last (i.e. topmost) Received: line which begins with the exact string "Received: from". 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: IP ADDRESS
Cleiton L. Siqueira writes: > I need to know what enviroment variable is responsible to keep the IP > ADDRESS of SENDER. $TCPREMOTEIP. You should look into tcpservers -x option and http://cr.yp.to/ucspi-tcp/tcprules.html> If I understand you correctly, it will do what you want. Vince.
Re: IP ADDRESS
Dear Charles, The difference than the standart is that I have many different domains in my server. And I check them through the SQL database (Postgres). I organize different directories for each domain in the /home directory. For example, if I have this domains in my system: example.com and sample.com I will have two directories in /home directory like this: /home/example.com/ and /home/sample.com/ and into these directories there will be the account of my users. When the script gets a email, it splits From: [EMAIL PROTECTED] To: account: example domain: example.com The script uses this information to delivery in the right directory, depending on the domain. I'd like to know once more information. About the IP ADDRESS of SENDER. I need to know what enviroment variable is responsible to keep the IP ADDRESS of SENDER. Regards Cleiton Charles Cazabon gravada: > Cleiton L. Siqueira <[EMAIL PROTECTED]> wrote: > > > > I make a perl script called deliverator. > > This script uses safecat program to delivery the messages > > in the Maildir. > > My actual script split the account and domain of the RECIPIENT > > and check where it must delivery the message. If case it doesn't > > find the account or domain my script return a message to the SENDER > > notifying that the email wasn't found. > > How is this different than the standard qmail delivery method with a > qmail-start invocation specifying "./Maildir/" as the default delivery > target? > > > I would like to implement in this script, the possibitity of avoiding the > > local users in my network to send anonymous messages to the others. But I > > need to know once more information like RECIPIENT or SENDER. I need to know > > What the IP address of the SENDER is. Because this way I can check if he > > belongs in my network and avoiding he to send anonymous messages. To do this > > I'd match the SENDER and IP ADDRESS and if they are right I would permit if > > they wouldn't match I' deny. Of course that remote e-mail I will permit to > > send any e-mail. My email server is protected against relay. > > qmail helpfully sets various environment variables for programs run from > .qmail files -- see the manual page for qmail-command for details. > > 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. > ---
IP ADDRESS
Hi people, I'd like to know if someone could help me with this doubt. I make a perl script called deliverator. This script uses safecat program to delivery the messages in the Maildir. My actual script split the account and domain of the RECIPIENT and check where it must delivery the message. If case it doesn't find the account or domain my script return a message to the SENDER notifying that the email wasn't found. I would like to implement in this script, the possibitity of avoiding the local users in my network to send anonymous messages to the others. But I need to know once more information like RECIPIENT or SENDER. I need to know What the IP address of the SENDER is. Because this way I can check if he belongs in my network and avoiding he to send anonymous messages. To do this I'd match the SENDER and IP ADDRESS and if they are right I would permit if they wouldn't match I' deny. Of course that remote e-mail I will permit to send any e-mail. My email server is protected against relay. If someone can give me this information about how I can get to catch IP address of the SENDER I would thank. Regards Cleiton
Re: IP ADDRESS
Cleiton L. Siqueira <[EMAIL PROTECTED]> wrote: > > I make a perl script called deliverator. > This script uses safecat program to delivery the messages > in the Maildir. > My actual script split the account and domain of the RECIPIENT > and check where it must delivery the message. If case it doesn't > find the account or domain my script return a message to the SENDER > notifying that the email wasn't found. How is this different than the standard qmail delivery method with a qmail-start invocation specifying "./Maildir/" as the default delivery target? > I would like to implement in this script, the possibitity of avoiding the > local users in my network to send anonymous messages to the others. But I > need to know once more information like RECIPIENT or SENDER. I need to know > What the IP address of the SENDER is. Because this way I can check if he > belongs in my network and avoiding he to send anonymous messages. To do this > I'd match the SENDER and IP ADDRESS and if they are right I would permit if > they wouldn't match I' deny. Of course that remote e-mail I will permit to > send any e-mail. My email server is protected against relay. qmail helpfully sets various environment variables for programs run from .qmail files -- see the manual page for qmail-command for details. 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. ---
IP ADDRESS
Hi people, I'd like to know if someone could help me with this doubt. I make a perl script called deliverator. This script uses safecat program to delivery the messages in the Maildir. My actual script split the account and domain of the RECIPIENT and check where it must delivery the message. If case it doesn't find the account or domain my script return a message to the SENDER notifying that the email wasn't found. I would like to implement in this script, the possibitity of avoiding the local users in my network to send anonymous messages to the others. But I need to know once more information like RECIPIENT or SENDER. I need to know What the IP address of the SENDER is. Because this way I can check if he belongs in my network and avoiding he to send anonymous messages. To do this I'd match the SENDER and IP ADDRESS and if they are right I would permit if they wouldn't match I' deny. Of course that remote e-mail I will permit to send any e-mail. My email server is protected against relay. If someone can give me this information about how I can get to catch IP address of the SENDER I would thank. Regards Cleiton
Re: How can I get IP address of mail sender?
You can't. Only the IP for the server which is relaying or delivering mail to you, but that's trivial right? On Tue, Mar 06, 2001 at 08:52:44AM +0800, [EMAIL PROTECTED] wrote: > There, I want to get IP address of mail sender, so I can add some choiced IPs to >/etc/tcp.smtp.cdb. But how can I get it? > Thanks! > -- > »¶ÓʹÓà 21CN µç×ÓÓʼþϵͳ http://www.21cn.com > Thank you for using 21cn.com Email system > -- Jose AP Celestino <[EMAIL PROTECTED]> || SAPO / PT Multimedia Administração de Sistemas / Operações || http://www.sapo.pt --
How can I get IP address of mail sender?
There, I want to get IP address of mail sender, so I can add some choiced IPs to /etc/tcp.smtp.cdb. But how can I get it? Thanks! -- »¶ÓʹÓà 21CN µç×ÓÓʼþϵͳ http://www.21cn.com Thank you for using 21cn.com Email system
Re: I couldn't find a mail exchanger or IP address
On Sat, 3 Mar 2001, Steve Marks wrote: > I'm receiving the "I couldn't find a mail exchanger or IP address" error > when sending email to a specific domain, savvy.com. ups ..sorry.. that was my fault :-(... no clue what it could be otherwisehmmm... ; <<>> DiG 9.1.0 <<>> -tmx savvy.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55032 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;savvy.com. IN MX ;; ANSWER SECTION: savvy.com. 900 IN MX 10 pop.e-it.com. ;; AUTHORITY SECTION: savvy.com. 900 IN NS ns1.dnswiz.com. savvy.com. 900 IN NS ns2.dnswiz.com. savvy.com. 900 IN NS ns3.dnswiz.com. savvy.com. 900 IN NS ns4.dnswiz.com. ;; ADDITIONAL SECTION: ns1.dnswiz.com. 900 IN A 207.91.131.30 ns2.dnswiz.com. 900 IN A 207.91.131.31 ns3.dnswiz.com. 900 IN A 216.119.149.100 ns4.dnswiz.com. 900 IN A 216.119.149.101 ;; Query time: 244 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sun Mar 4 02:06:56 2001 ;; MSG SIZE rcvd: 198 greets Martin -- http://www.kos.li/ [EMAIL PROTECTED] +41-76-384-93-33 ICQ# 13556143 Say NO to HTML in mail and news Proudly running Debian GNU/Linux. See http://www.debian.org/
Re: I couldn't find a mail exchanger or IP address
On Sat, 3 Mar 2001, Steve Marks wrote: > I'm receiving the "I couldn't find a mail exchanger or IP address" error > when sending email to a specific domain, savvy.com. i couldn't find an mx-entry for this domain ?? ; <<>> DiG 9.1.0 <<>> -tany savvy.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6989 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;savvy.com. IN ANY ;; ANSWER SECTION: savvy.com. 172800 IN NS NS1.DNSWIZ.COM. savvy.com. 172800 IN NS NS2.DNSWIZ.COM. savvy.com. 172800 IN NS NS4.DNSWIZ.COM. savvy.com. 172800 IN NS NS3.DNSWIZ.COM. ;; AUTHORITY SECTION: savvy.com. 172800 IN NS NS1.DNSWIZ.COM. savvy.com. 172800 IN NS NS2.DNSWIZ.COM. savvy.com. 172800 IN NS NS4.DNSWIZ.COM. savvy.com. 172800 IN NS NS3.DNSWIZ.COM. ;; ADDITIONAL SECTION: NS1.DNSWIZ.COM. 172800 IN A 207.91.131.30 NS2.DNSWIZ.COM. 172800 IN A 207.91.131.31 NS4.DNSWIZ.COM. 172800 IN A 216.119.149.101 NS3.DNSWIZ.COM. 172800 IN A 216.119.149.100 ;; Query time: 144 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sun Mar 4 02:05:51 2001 ;; MSG SIZE rcvd: 229 greets Martin -- http://www.kos.li/ [EMAIL PROTECTED] +41-76-384-93-33 ICQ# 13556143 Say NO to HTML in mail and news Proudly running Debian GNU/Linux. See http://www.debian.org/
I couldn't find a mail exchanger or IP address
I'm receiving the "I couldn't find a mail exchanger or IP address" error when sending email to a specific domain, savvy.com. I've seen this question asked before by searching the qmail mailing list archive. The answer has always been that the MX record points to an IP address instead which is not RFC compliant. However, when I do an nslookup on the MX record for savvy.com I see this: > set type=mx > savvy.com Server: 216-119-149-101.ipset29.wt.net Address: 216.119.149.101 savvy.com preference = 10, mail exchanger = pop.e-it.com savvy.com nameserver = ns1.dnswiz.com savvy.com nameserver = ns2.dnswiz.com savvy.com nameserver = ns3.dnswiz.com savvy.com nameserver = ns4.dnswiz.com ns1.dnswiz.com internet address = 207.91.131.30 ns2.dnswiz.com internet address = 207.91.131.31 ns3.dnswiz.com internet address = 216.119.149.100 ns4.dnswiz.com internet address = 216.119.149.101 So I don't believe the typical response applies to this case since pop.e-it.com is not an IP address. Is there another reason for this error? Am I just missing something? Could the problem be on my end? This appears to be the only domain I have problems with (I receive mail from them, I just can't reply). Thanks for any info, Steve Marks [EMAIL PROTECTED]
Re: I need to block IP Address
On Fri, Feb 16, 2001 at 11:33:12AM +0400, Antonio Ferri Charbone wrote: > I need urgently to block IP Address in qmail, anybody knows what is the > manner of make it ? use tcpservers functionality (1.2.3.4:deny). Regards, Uwe
Re: I need to block IP Address
> I need urgently to block IP Address in qmail, anybody knows what is the > manner of make it ? "man tcpserver" if you are running qmail-smtpd under tcpserver. -x is the switch that helps you. Your operating system may also be able to block packets from defined IP addresses. Regards, Frank
Re: I need to block IP Address
Antonio Ferri Charbone <[EMAIL PROTECTED]> wrote: > > I need urgently to block IP Address in qmail, anybody knows what is the > manner of make it ? If you invoke qmail-smtpd with tcpserver, add a rule like 1.2.3.4:deny somewhere in the appropriate tcprules file. Then recompile the rules to the appropriate .cdb file. 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: I need to block IP Address
Hello, * Antonio Ferri Charbone <[EMAIL PROTECTED]> [010216 16:40] wrote: > Hi, > > I need urgently to block IP Address in qmail, anybody knows what is the > manner of make it ? Block the domain in /var/qmail/badmailfrom or use firewall tool for block 25 port for this ip. in qmail afik you can't block ip. cheers, p. -- pawel garbowski [EMAIL PROTECTED]
I need to block IP Address
Hi, I need urgently to block IP Address in qmail, anybody knows what is the manner of make it ? thanks begin:vcard n:Ferri Charbone;Antonio x-mozilla-html:TRUE org:Telcel Celular C.A.;Gerencia de Operaciones adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Administrador de Sistemas x-mozilla-cpt:;-19088 fn:Antonio Ferri Charbone end:vcard
Re: invisible IP address
[EMAIL PROTECTED] <[EMAIL PROTECTED]> writes on 16 December 2000 at 23:36:34 +0100 > Hello, > > how can i define my IP-address and hostname to invisible when i send my > email via smtp to the world ? You can't; the line giving your IP is put in by the next server in the chain, and you can't control it. -- David Dyer-Bennet / Welcome to the future! / [EMAIL PROTECTED] SF: http://www.dd-b.net/dd-b/ Minicon: http://www.mnstf.org/minicon/ Photos: http://dd-b.lighthunters.net/
invisible IP address
Hello, how can i define my IP-address and hostname to invisible when i send my email via smtp to the world ? I've seen the variable TCPLOCALIP and TCPLOCALHOST. I want only, that other email systems the MX record of the DNS server see and use. Thanks for the help best regards Gustav -- Sent through GMX FreeMail - http://www.gmx.net
Re: couldn't find a mail exchanger or IP address
Am Mittwoch, 6. Dezember 2000 03:02 schrieb David Geller: > I've setup my assign file in /var/qmail/users so that it includes the > following line (group and uid redacted): > > +ken:ken:XXX:XX:/home/ken::: > > Interestingly, when I send mail from Yahoo to the following address > > ken|cook%40cooking.com|[EMAIL PROTECTED] > > it works, but won't work when I send from one of my other systems, which > also runs qmail. Here's the error message I receive: > > Hi. This is the qmail-send program at arta.com. > I'm afraid I wasn't able to deliver your message to the following > addresses. > This is a permanent error; I've given up. Sorry it didn't work out. > > : > Sorry, I couldn't find a mail exchanger or IP address. (#5.4.4) > > Why would this work from Yahoo but not my own system? Thanks in advance for > any help you can shed on the problem. looks like there's a problem with your resolver (yes, DNS). You might want to have a look at djbdns.. (OK, that's OT). > > - David -- Henning Brauer | BS Web Services Hostmaster BSWS| Roedingsmarkt 14 [EMAIL PROTECTED] | 20459 Hamburg www.bsws.de| Germany
couldn't find a mail exchanger or IP address
I've setup my assign file in /var/qmail/users so that it includes the following line (group and uid redacted): +ken:ken:XXX:XX:/home/ken::: Interestingly, when I send mail from Yahoo to the following address ken|cook%40cooking.com|[EMAIL PROTECTED] it works, but won't work when I send from one of my other systems, which also runs qmail. Here's the error message I receive: Hi. This is the qmail-send program at arta.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : Sorry, I couldn't find a mail exchanger or IP address. (#5.4.4) Why would this work from Yahoo but not my own system? Thanks in advance for any help you can shed on the problem. - David
RE: How to hide the ip address of the client sender from the message header?
No, just like it was written 192.168.100.:allow,TCPREMOTEHOST="",TCPREMOTEIP="",RELAYCLIENT="" This essentially overrides the variables set by the connection and makes it look like this Received: (qmail 25666 invoked from network); 17 Oct 2000 20:26:18 - Received: from (HELO mensa) () by 192.168.100.10 with SMTP; 17 Oct 2000 20:26:18 - -Original Message- From: Mike A. Sauvain [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 17, 2000 4:34 PM To: Tim Hunter; [EMAIL PROTECTED] Subject: Re: How to hide the ip address of the client sender from the message header? 192.168.100.:allow,TCPREMOTEHOST="needed out ip?" ,TCPREMOTEIP="",RELAYCLIENT="" how i defined it ?. i was looking on different places, like site's and man's but nothing really specific found. Received: (qmail 391 invoked from network); 17 Oct 2000 08:43:48 - Received: from freesurf.ch (HELO freesurfmail.sunrise.ch) (194.230.0.32) by 192.168.1.20 with SMTP; 17 Oct 2000 08:43:48 - thanks, mike...
Re: How to hide the ip address of the client sender from the message header?
192.168.100.:allow,TCPREMOTEHOST="needed out ip?" ,TCPREMOTEIP="",RELAYCLIENT="" how i defined it ?. i was looking on different places, like site's and man's but nothing really specific found. Received: (qmail 391 invoked from network); 17 Oct 2000 08:43:48 - Received: from freesurf.ch (HELO freesurfmail.sunrise.ch) (194.230.0.32) by 192.168.1.20 with SMTP; 17 Oct 2000 08:43:48 - thanks, mike...
RE: How to hide the ip address of the client sender from the message header?
To quote an old message to the list On Fri, Sep 22, 2000 at 11:09:59AM +0800, Paul Tan wrote: > Hi guys, > >Is there a way to NOT show my internal email IPs and stuff, which > module must i add to filter those stuff out ?? If you're using tcpserver, put something like this in your rules file: 192.168.100.:allow,TCPREMOTEHOST="",TCPREMOTEIP="",RELAYCLIENT="" Chris -- Tim -Original Message- From: Mike A. Sauvain [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 17, 2000 7:12 AM To: [EMAIL PROTECTED] Subject: Re: How to hide the ip address of the client sender from the message header? How to hide the ip address of the client sender from the message header? mail source: Received: (qmail 391 invoked from network); 17 Oct 2000 08:43:48 - Received: from freesurf.ch (HELO freesurfmail.sunrise.ch) (194.230.0.32) by 192.168.1.20 with SMTP; 17 Oct 2000 08:43:48 - ~^~^~~~^~ ^~~~^^ how i can solve the problem ? thanks. mike - Original Message - From: "Chris Johnson" <[EMAIL PROTECTED]> To: "Francesco Munaretto" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, October 16, 2000 5:41 PM Subject: Re: How to hide the ip address of the client sender from the message header? On Mon, Oct 16, 2000 at 04:11:56PM +0200, Francesco Munaretto wrote: >194.194.194.194 LAN >|| > mail--INTERNET-Firewall-+--mail (192.168.0.2) > mydomain2.com +--mypc (192.168.0.3) > mydomain.com > > I'm using a pop3 server on mail.mydomain2.com. > I'have received a message from mail.mydomain.com and > in the header message there are the following text lines: > > Received: from mail.mydomain.com ([194.194.194.194]) > by www (8.10.2/8.10.2) with SMTP id e9G9FZq12616 > for <[EMAIL PROTECTED]>; Mon, 16 Oct 2000 11:15:35 +0200 > Received: (qmail 2553 invoked from network); 16 Oct 2000 09:09:58 - > Received: from unknown (HELO mypc) (192.168.0.3) > ^^^^^^^^^^^ > by 192.168.0.2 with SMTP; 16 Oct 2000 09:09:58 - > ^^ > ... > > In the header appears the host name and the ip address > of the client sender and the internal ip address of the > qmail server (either protected by firewall). > How to scrub the private ip addresses from the header? If you're using tcpserver, try putting this in your rules file: 192.168.0.:allow,TCPREMOTEHOST="",TCPREMOTEIP="",RELAYCLIENT="" Chris -- To unsubscribe, send mail to [EMAIL PROTECTED] with "unsubscribe" in the subject field of the message. Please read the documentation and the FAQ before posting a question -- chances are it's already been answered. http://www.proftpd.net -- The Official ProFTPD web site. http://bugs.proftpd.net -- Bug reporting and feature requests. http://www.proftpd.net/docs/ -- The latest ProFTPD documentation and FAQ.
Re: How to hide the ip address of the client sender from the message header?
How to hide the ip address of the client sender from the message header? mail source: Received: (qmail 391 invoked from network); 17 Oct 2000 08:43:48 - Received: from freesurf.ch (HELO freesurfmail.sunrise.ch) (194.230.0.32) by 192.168.1.20 with SMTP; 17 Oct 2000 08:43:48 - ~^~^~~~^~ ^~~~^^ how i can solve the problem ? thanks. mike - Original Message - From: "Chris Johnson" <[EMAIL PROTECTED]> To: "Francesco Munaretto" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, October 16, 2000 5:41 PM Subject: Re: How to hide the ip address of the client sender from the message header? On Mon, Oct 16, 2000 at 04:11:56PM +0200, Francesco Munaretto wrote: >194.194.194.194 LAN >|| > mail--INTERNET-Firewall-+--mail (192.168.0.2) > mydomain2.com +--mypc (192.168.0.3) > mydomain.com > > I'm using a pop3 server on mail.mydomain2.com. > I'have received a message from mail.mydomain.com and > in the header message there are the following text lines: > > Received: from mail.mydomain.com ([194.194.194.194]) > by www (8.10.2/8.10.2) with SMTP id e9G9FZq12616 > for <[EMAIL PROTECTED]>; Mon, 16 Oct 2000 11:15:35 +0200 > Received: (qmail 2553 invoked from network); 16 Oct 2000 09:09:58 - > Received: from unknown (HELO mypc) (192.168.0.3) > ^^^ > by 192.168.0.2 with SMTP; 16 Oct 2000 09:09:58 - > ^^ > ... > > In the header appears the host name and the ip address > of the client sender and the internal ip address of the > qmail server (either protected by firewall). > How to scrub the private ip addresses from the header? If you're using tcpserver, try putting this in your rules file: 192.168.0.:allow,TCPREMOTEHOST="",TCPREMOTEIP="",RELAYCLIENT="" Chris -- To unsubscribe, send mail to [EMAIL PROTECTED] with "unsubscribe" in the subject field of the message. Please read the documentation and the FAQ before posting a question -- chances are it's already been answered. http://www.proftpd.net -- The Official ProFTPD web site. http://bugs.proftpd.net -- Bug reporting and feature requests. http://www.proftpd.net/docs/ -- The latest ProFTPD documentation and FAQ.
Limiting simultaneous connections from an IP address
A while back somebody mentioned in passing an add-on that allowed connection limiting based on IP address. I can't find it at on the webpage at qmail.org, or in the FAQ or LWQ. I'm currently doing it with a patched version of tcpserver, but would rather do it the qmail way - anybody got a pointer? Thanks, Rick. -- Rick Lyons WebCentral
Re: How to hide the ip address of the client sender from the message header?
On Mon, Oct 16, 2000 at 04:11:56PM +0200, Francesco Munaretto wrote: >194.194.194.194 LAN >|| > mail--INTERNET-Firewall-+--mail (192.168.0.2) > mydomain2.com +--mypc (192.168.0.3) > mydomain.com > > I'm using a pop3 server on mail.mydomain2.com. > I'have received a message from mail.mydomain.com and > in the header message there are the following text lines: > > Received: from mail.mydomain.com ([194.194.194.194]) > by www (8.10.2/8.10.2) with SMTP id e9G9FZq12616 > for <[EMAIL PROTECTED]>; Mon, 16 Oct 2000 11:15:35 +0200 > Received: (qmail 2553 invoked from network); 16 Oct 2000 09:09:58 - > Received: from unknown (HELO mypc) (192.168.0.3) > ^^^ > by 192.168.0.2 with SMTP; 16 Oct 2000 09:09:58 - > ^^^^^^ > ... > > In the header appears the host name and the ip address > of the client sender and the internal ip address of the > qmail server (either protected by firewall). > How to scrub the private ip addresses from the header? If you're using tcpserver, try putting this in your rules file: 192.168.0.:allow,TCPREMOTEHOST="",TCPREMOTEIP="",RELAYCLIENT="" Chris
How to hide the ip address of the client sender from the message header?
194.194.194.194 LAN || mail--INTERNET-Firewall-+--mail (192.168.0.2) mydomain2.com +--mypc (192.168.0.3) mydomain.com I'm using a pop3 server on mail.mydomain2.com. I'have received a message from mail.mydomain.com and in the header message there are the following text lines: Received: from mail.mydomain.com ([194.194.194.194]) by www (8.10.2/8.10.2) with SMTP id e9G9FZq12616 for <[EMAIL PROTECTED]>; Mon, 16 Oct 2000 11:15:35 +0200 Received: (qmail 2553 invoked from network); 16 Oct 2000 09:09:58 - Received: from unknown (HELO mypc) (192.168.0.3) ^^^ by 192.168.0.2 with SMTP; 16 Oct 2000 09:09:58 - ^^ ... In the header appears the host name and the ip address of the client sender and the internal ip address of the qmail server (either protected by firewall). How to scrub the private ip addresses from the header? Thanks in advance for any help. francesco
Re: Specifying outgoing IP address of qmail-remote
I follow up myself.. > Hello all. I'm relatively new to qmail. > > I'm wondering if someone made newer version of following patch. (or like) > > http://www.ornl.gov/its/archives/mailing-lists/qmail/1996/12/msg00261.html > > I really need this kind of patch, since some mail servers are configured to > reject mail I finally find what I need in this list. http://www.ornl.gov/its/archives/mailing-lists/qmail/2000/05/msg01636.html http://www.ornl.gov/its/archives/mailing-lists/qmail/1999/02/msg00491.html look like both of them will do what I need. Yasuo
Specifying outgoing IP address of qmail-remote
Hello all. I'm relatively new to qmail. I'm wondering if someone made newer version of following patch. (or like) http://www.ornl.gov/its/archives/mailing-lists/qmail/1996/12/msg00261.html I really need this kind of patch, since some mail servers are configured to reject mail if source IP address does not match host name that qmail claimes. (I'm running qmail 1.03 with sevral IPs are assigned) If there is, please let me know where I can get it. Thank you for your information!! Yasuo
Re: sending e-mai to an ip address
The correct syntax is: to: user@[ip-address-of-hostB] the square brackets are required in this case. On Fri, 18 Aug 2000, Jeff Mangewala wrote: > Hello, > > Can I use qmail-inject on hostA to send e-mail to a user at hostB by doing > the following: > > > qmail-inject > to: user@ip-address-of-hostB > > > > I saw an RFC that states that DNS aliases cannot be used. > Does this mean that the "to:" line has to be to something with an "A" record > in DNS? > > ie to: [EMAIL PROTECTED] > > And how about if I configure qmail on hostB to receive e-mail for > "ip-address-of-hostB"? > > Will hostA still barf out with the message: > > CNAME_lookup_failed_temporarily. > > And, if it does, can I telnet to port 25 of hostB and send e-mail to > user@ip-address-of-hostB > > Thanks, > > Jeff Mangewala > > > > > > > > > > * > This email message is for the sole use of the intended recipients(s) > and may contain confidential and privileged information. > Any unauthorized review, use, disclosure or distribution is prohibited. > If you are not the intended recipient, please contact sender by > reply email and destroy all copies of original message. > > > - Timothy L. Mayo mailto:[EMAIL PROTECTED] Senior Systems Administrator localconnect(sm) http://www.localconnect.net/ The National Business Network Inc. http://www.nb.net/ One Monroeville Center, Suite 850 Monroeville, PA 15146 (412) 810- Phone (412) 810-8886 Fax
sending e-mai to an ip address
Hello, Can I use qmail-inject on hostA to send e-mail to a user at hostB by doing the following: qmail-inject to: user@ip-address-of-hostB I saw an RFC that states that DNS aliases cannot be used. Does this mean that the "to:" line has to be to something with an "A" record in DNS? ie to: [EMAIL PROTECTED] And how about if I configure qmail on hostB to receive e-mail for "ip-address-of-hostB"? Will hostA still barf out with the message: CNAME_lookup_failed_temporarily. And, if it does, can I telnet to port 25 of hostB and send e-mail to user@ip-address-of-hostB Thanks, Jeff Mangewala * This email message is for the sole use of the intended recipients(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact sender by reply email and destroy all copies of original message.
Re: tcprules, rcpthost, ip address problem
>> is the firewall doing NAT That was the problem exactly. I don't know how I missed it (I'm the guy who set up the firewall!!) but I did. Barry
Re: tcprules, rcpthost, ip address problem
Barry Dwyer writes: > My tcp.smtp file has proper settings to allow the local clients to work > as RELAYCLIENTS: > > 127.0.0.1:allow,RELAYCLIENT="" > 192.168.0.:allow,RELAYCLIENT="" > :allow Just a speculation, but is the firewall doing NAT? Does the mail server really see 192.168.0.n as client IP addresses? Anyway, I'd look into the tcpserver's activity log for the client IP addresses the mail server sees, and use tcprulescheck to check if /etc/tcp.smtp.cdb is set up as expected. -- Tetsu Ushijima
Re: tcprules, rcpthost, ip address problem
On Tue, Jul 04, 2000 at 05:00:11PM +0200, Giuliano Cocchi wrote: > Yes, i receive mail from outside for my local and virtual domain, > and only the listed networks can use my server to send mail to outside. Something's wrong then... That final :deny rule should reject any outside TCP connection to your port 25. Which means no mail. The last rule should be :allow (or nothing at all, which implies :allow) RC > > On Tue, 04 Jul 2000, you wrote: > > On Tue, Jul 04, 2000 at 04:36:22PM +0200, Giuliano Cocchi wrote: > > > Intruducing > > > 192.168.0.:allow,RELAYCLIENT="" > > > (and each other network managed by your server) > > > :deny > > > > Are you sure? It shouldn't! Are you getting any mail from the outside at all? > > > > RC > > > > > it's works correctly !! > > > > > > > > > On Tue, 04 Jul 2000, ertan payci wrote: > > > > Im afraid, i had a wrong view of the system. > > > > Well i must admit that my idea was not very accurate. It was a very easy > > > > way to > > > > make sure that it (somehow) works. But Adam McKenna ist absolutely > > > > right. > > > > Actually it ist not the right way. > > > > > > > > So i reproduced your configuration but had no problems. > > > > If your problem still exists, i can send you pieces of my local > > > > configuration files. > > > > > > > > Regards. > > > > > > > > > > > > > > > > Giuliano Cocchi wrote: > > > > > > > > > > Yes, deleting rcphosts the relay works correcly. But this pose the problem to > > > > > deny the relay to unwanted people. > > > > > Through the tcp.smtpd i can really manage the relay? > > > > > > > > > > On Tue, 04 Jul 2000, ertan payci wrote: > > > > > > Hello, > > > > > > > > > > > > Let me see if i got it right: you have users using your mailbox as > > > > > > mailhost,and want > > > > > > them to be able to use your mailhost as relay. Right ? > > > > > > IMHO you should just delete rcpthosts and manage your relaying stuff > > > > > > through > > > > > > your tcp.smtp.cdb stuff. Your tcp.smtp looks correct, so give it a > > > > > > trial. > > > > > > > > > > > > Regards > > > > > > > > > > > > Ertan > > > > > > > > > > > > Barry Dwyer wrote: > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > I've got qmail running properly on a system with a DMZ-firewall setup. > > > > > > > All the local clients are behind the firewall, addressed as 192.168.0.n. > > > > > > > The firewall (a debian box) and the mail server are connected to our > > > > > > > ADSL router and both have class-C addresses. The clients all have hosts > > > > > > > files referencing the mail server. > > > > > > > > > > > > > > My tcp.smtp file has proper settings to allow the local clients to work > > > > > > > as RELAYCLIENTS: > > > > > > > > > > > > > > 127.0.0.1:allow,RELAYCLIENT="" > > > > > > > 192.168.0.:allow,RELAYCLIENT="" > > > > > > > :allow > > > > > > > > > > > > > > (I've recompiled it just to be sure and, yes, the reference in the qmail > > > > > > > startup script points to the proper file '-x/etc/tcp.smtp.cdb') > > > > > > > > > > > > > > If I create a rcpthosts file with just the local domain in it (that's > > > > > > > all I want), then every local client that tries to send mail out to the > > > > > > > 'net gets a qmail error message saying the destination domain is not in > > > > > > > the list of receipt hosts (or something to that effect). > > > > > > > > > > > > > > Is the problem that qmail, running on a mail server, with it's class-C > > > > > > > address, doesn't like the "192" block addresses in tcp.smtp? I've set up > > > > > > > qmail servers before as multihomed systems with a class-C card *and* and > > > > > > > internal one. Must I do that here? > > > > > > > > > > > > > > Thanks > > > > > > > Barry Dwyer > > > > -- > > +--- > > | 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 3166730/00 (24h/dia) - Fax: +351 21 3166701 -- +--- | 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 3166730/00 (24h/dia) - Fax: +351 21 3166701
Re: tcprules, rcpthost, ip address problem
On Tue, Jul 04, 2000 at 04:36:22PM +0200, Giuliano Cocchi wrote: > Intruducing > 192.168.0.:allow,RELAYCLIENT="" > (and each other network managed by your server) > :deny Are you sure? It shouldn't! Are you getting any mail from the outside at all? RC > it's works correctly !! > > > On Tue, 04 Jul 2000, ertan payci wrote: > > Im afraid, i had a wrong view of the system. > > Well i must admit that my idea was not very accurate. It was a very easy > > way to > > make sure that it (somehow) works. But Adam McKenna ist absolutely > > right. > > Actually it ist not the right way. > > > > So i reproduced your configuration but had no problems. > > If your problem still exists, i can send you pieces of my local > > configuration files. > > > > Regards. > > > > > > > > Giuliano Cocchi wrote: > > > > > > Yes, deleting rcphosts the relay works correcly. But this pose the problem to > > > deny the relay to unwanted people. > > > Through the tcp.smtpd i can really manage the relay? > > > > > > On Tue, 04 Jul 2000, ertan payci wrote: > > > > Hello, > > > > > > > > Let me see if i got it right: you have users using your mailbox as > > > > mailhost,and want > > > > them to be able to use your mailhost as relay. Right ? > > > > IMHO you should just delete rcpthosts and manage your relaying stuff > > > > through > > > > your tcp.smtp.cdb stuff. Your tcp.smtp looks correct, so give it a > > > > trial. > > > > > > > > Regards > > > > > > > > Ertan > > > > > > > > Barry Dwyer wrote: > > > > > > > > > > Hi all, > > > > > > > > > > I've got qmail running properly on a system with a DMZ-firewall setup. > > > > > All the local clients are behind the firewall, addressed as 192.168.0.n. > > > > > The firewall (a debian box) and the mail server are connected to our > > > > > ADSL router and both have class-C addresses. The clients all have hosts > > > > > files referencing the mail server. > > > > > > > > > > My tcp.smtp file has proper settings to allow the local clients to work > > > > > as RELAYCLIENTS: > > > > > > > > > > 127.0.0.1:allow,RELAYCLIENT="" > > > > > 192.168.0.:allow,RELAYCLIENT="" > > > > > :allow > > > > > > > > > > (I've recompiled it just to be sure and, yes, the reference in the qmail > > > > > startup script points to the proper file '-x/etc/tcp.smtp.cdb') > > > > > > > > > > If I create a rcpthosts file with just the local domain in it (that's > > > > > all I want), then every local client that tries to send mail out to the > > > > > 'net gets a qmail error message saying the destination domain is not in > > > > > the list of receipt hosts (or something to that effect). > > > > > > > > > > Is the problem that qmail, running on a mail server, with it's class-C > > > > > address, doesn't like the "192" block addresses in tcp.smtp? I've set up > > > > > qmail servers before as multihomed systems with a class-C card *and* and > > > > > internal one. Must I do that here? > > > > > > > > > > Thanks > > > > > Barry Dwyer -- +--- | 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 3166730/00 (24h/dia) - Fax: +351 21 3166701
Re: tcprules, rcpthost, ip address problem
Intruducing 192.168.0.:allow,RELAYCLIENT="" (and each other network managed by your server) :deny it's works correctly !! On Tue, 04 Jul 2000, ertan payci wrote: > Im afraid, i had a wrong view of the system. > Well i must admit that my idea was not very accurate. It was a very easy > way to > make sure that it (somehow) works. But Adam McKenna ist absolutely > right. > Actually it ist not the right way. > > So i reproduced your configuration but had no problems. > If your problem still exists, i can send you pieces of my local > configuration files. > > Regards. > > > > Giuliano Cocchi wrote: > > > > Yes, deleting rcphosts the relay works correcly. But this pose the problem to > > deny the relay to unwanted people. > > Through the tcp.smtpd i can really manage the relay? > > > > On Tue, 04 Jul 2000, ertan payci wrote: > > > Hello, > > > > > > Let me see if i got it right: you have users using your mailbox as > > > mailhost,and want > > > them to be able to use your mailhost as relay. Right ? > > > IMHO you should just delete rcpthosts and manage your relaying stuff > > > through > > > your tcp.smtp.cdb stuff. Your tcp.smtp looks correct, so give it a > > > trial. > > > > > > Regards > > > > > > Ertan > > > > > > Barry Dwyer wrote: > > > > > > > > Hi all, > > > > > > > > I've got qmail running properly on a system with a DMZ-firewall setup. > > > > All the local clients are behind the firewall, addressed as 192.168.0.n. > > > > The firewall (a debian box) and the mail server are connected to our > > > > ADSL router and both have class-C addresses. The clients all have hosts > > > > files referencing the mail server. > > > > > > > > My tcp.smtp file has proper settings to allow the local clients to work > > > > as RELAYCLIENTS: > > > > > > > > 127.0.0.1:allow,RELAYCLIENT="" > > > > 192.168.0.:allow,RELAYCLIENT="" > > > > :allow > > > > > > > > (I've recompiled it just to be sure and, yes, the reference in the qmail > > > > startup script points to the proper file '-x/etc/tcp.smtp.cdb') > > > > > > > > If I create a rcpthosts file with just the local domain in it (that's > > > > all I want), then every local client that tries to send mail out to the > > > > 'net gets a qmail error message saying the destination domain is not in > > > > the list of receipt hosts (or something to that effect). > > > > > > > > Is the problem that qmail, running on a mail server, with it's class-C > > > > address, doesn't like the "192" block addresses in tcp.smtp? I've set up > > > > qmail servers before as multihomed systems with a class-C card *and* and > > > > internal one. Must I do that here? > > > > > > > > Thanks > > > > Barry Dwyer
Re: tcprules, rcpthost, ip address problem
Im afraid, i had a wrong view of the system. Well i must admit that my idea was not very accurate. It was a very easy way to make sure that it (somehow) works. But Adam McKenna ist absolutely right. Actually it ist not the right way. So i reproduced your configuration but had no problems. If your problem still exists, i can send you pieces of my local configuration files. Regards. Giuliano Cocchi wrote: > > Yes, deleting rcphosts the relay works correcly. But this pose the problem to > deny the relay to unwanted people. > Through the tcp.smtpd i can really manage the relay? > > On Tue, 04 Jul 2000, ertan payci wrote: > > Hello, > > > > Let me see if i got it right: you have users using your mailbox as > > mailhost,and want > > them to be able to use your mailhost as relay. Right ? > > IMHO you should just delete rcpthosts and manage your relaying stuff > > through > > your tcp.smtp.cdb stuff. Your tcp.smtp looks correct, so give it a > > trial. > > > > Regards > > > > Ertan > > > > Barry Dwyer wrote: > > > > > > Hi all, > > > > > > I've got qmail running properly on a system with a DMZ-firewall setup. > > > All the local clients are behind the firewall, addressed as 192.168.0.n. > > > The firewall (a debian box) and the mail server are connected to our > > > ADSL router and both have class-C addresses. The clients all have hosts > > > files referencing the mail server. > > > > > > My tcp.smtp file has proper settings to allow the local clients to work > > > as RELAYCLIENTS: > > > > > > 127.0.0.1:allow,RELAYCLIENT="" > > > 192.168.0.:allow,RELAYCLIENT="" > > > :allow > > > > > > (I've recompiled it just to be sure and, yes, the reference in the qmail > > > startup script points to the proper file '-x/etc/tcp.smtp.cdb') > > > > > > If I create a rcpthosts file with just the local domain in it (that's > > > all I want), then every local client that tries to send mail out to the > > > 'net gets a qmail error message saying the destination domain is not in > > > the list of receipt hosts (or something to that effect). > > > > > > Is the problem that qmail, running on a mail server, with it's class-C > > > address, doesn't like the "192" block addresses in tcp.smtp? I've set up > > > qmail servers before as multihomed systems with a class-C card *and* and > > > internal one. Must I do that here? > > > > > > Thanks > > > Barry Dwyer
Re: tcprules, rcpthost, ip address problem
On Tue, Jul 04, 2000 at 04:04:37AM -0500, Christopher Tolley wrote: > I'm not going to argue, but I HAVE had to kill and restart tcpserver for the > changes to take effect. If that's wrong, then I don't know how to make the > changes take and NOT restart tcpserver...perhaps you can enlighten me a bit > in that respect. I'm not out to perform disinformation...just speaking from > first-hand experience > > BTW, I run tcpserver stand-alone, without the extra wrappers to monitor it. > Is this the limitation or is it something else? There is no limitation. tcpserver reads the cdb given as the argument to -x every time a connection is made. >From the man page: -xrules.cdb Follow the rules compiled into rules.cdb by tcprules. These rules may specify setting environ ment variables or rejecting connections from bad sources. tcpserver does not read rules.cdb into memory; you can rerun tcprules to change tcpserver's behavior on the fly. --Adam
Re: tcprules, rcpthost, ip address problem
On Tue, Jul 04, 2000 at 09:22:24AM +0200, ertan payci wrote: > Hello, > > Let me see if i got it right: you have users using your mailbox as > mailhost,and want > them to be able to use your mailhost as relay. Right ? > IMHO you should just delete rcpthosts and manage your relaying stuff > through > your tcp.smtp.cdb stuff. Your tcp.smtp looks correct, so give it a > trial. What is this, disinformation day? You should NEVER delete your rcpthosts file as this will cause qmail to function as an OPEN RELAY, no matter what the rules say. --Adam
Re: tcprules, rcpthost, ip address problem
Yes, deleting rcphosts the relay works correcly. But this pose the problem to deny the relay to unwanted people. Through the tcp.smtpd i can really manage the relay? On Tue, 04 Jul 2000, ertan payci wrote: > Hello, > > Let me see if i got it right: you have users using your mailbox as > mailhost,and want > them to be able to use your mailhost as relay. Right ? > IMHO you should just delete rcpthosts and manage your relaying stuff > through > your tcp.smtp.cdb stuff. Your tcp.smtp looks correct, so give it a > trial. > > Regards > > Ertan > > Barry Dwyer wrote: > > > > Hi all, > > > > I've got qmail running properly on a system with a DMZ-firewall setup. > > All the local clients are behind the firewall, addressed as 192.168.0.n. > > The firewall (a debian box) and the mail server are connected to our > > ADSL router and both have class-C addresses. The clients all have hosts > > files referencing the mail server. > > > > My tcp.smtp file has proper settings to allow the local clients to work > > as RELAYCLIENTS: > > > > 127.0.0.1:allow,RELAYCLIENT="" > > 192.168.0.:allow,RELAYCLIENT="" > > :allow > > > > (I've recompiled it just to be sure and, yes, the reference in the qmail > > startup script points to the proper file '-x/etc/tcp.smtp.cdb') > > > > If I create a rcpthosts file with just the local domain in it (that's > > all I want), then every local client that tries to send mail out to the > > 'net gets a qmail error message saying the destination domain is not in > > the list of receipt hosts (or something to that effect). > > > > Is the problem that qmail, running on a mail server, with it's class-C > > address, doesn't like the "192" block addresses in tcp.smtp? I've set up > > qmail servers before as multihomed systems with a class-C card *and* and > > internal one. Must I do that here? > > > > Thanks > > Barry Dwyer
Re: tcprules, rcpthost, ip address problem
Hello, Let me see if i got it right: you have users using your mailbox as mailhost,and want them to be able to use your mailhost as relay. Right ? IMHO you should just delete rcpthosts and manage your relaying stuff through your tcp.smtp.cdb stuff. Your tcp.smtp looks correct, so give it a trial. Regards Ertan Barry Dwyer wrote: > > Hi all, > > I've got qmail running properly on a system with a DMZ-firewall setup. > All the local clients are behind the firewall, addressed as 192.168.0.n. > The firewall (a debian box) and the mail server are connected to our > ADSL router and both have class-C addresses. The clients all have hosts > files referencing the mail server. > > My tcp.smtp file has proper settings to allow the local clients to work > as RELAYCLIENTS: > > 127.0.0.1:allow,RELAYCLIENT="" > 192.168.0.:allow,RELAYCLIENT="" > :allow > > (I've recompiled it just to be sure and, yes, the reference in the qmail > startup script points to the proper file '-x/etc/tcp.smtp.cdb') > > If I create a rcpthosts file with just the local domain in it (that's > all I want), then every local client that tries to send mail out to the > 'net gets a qmail error message saying the destination domain is not in > the list of receipt hosts (or something to that effect). > > Is the problem that qmail, running on a mail server, with it's class-C > address, doesn't like the "192" block addresses in tcp.smtp? I've set up > qmail servers before as multihomed systems with a class-C card *and* and > internal one. Must I do that here? > > Thanks > Barry Dwyer
Re: tcprules, rcpthost, ip address problem
It may seem a bit stupid... have you tried to put a space between the -x and the path to the cdb file? If so, can you please post the relevant script line ? Armando
Re: tcprules, rcpthost, ip address problem
>> did you run tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtp after creating that /etc/tcp.smtp file? Yes. A bunch of times. Barry
Re: tcprules, rcpthost, ip address problem
That's an actual paste of the file. BD Adam McKenna wrote: > On Mon, Jul 03, 2000 at 04:43:52PM -0700, Barry Dwyer wrote: > > >> Either there is a typo in your tcp.smtp . > > > > My tcp.smtp is included, in its entirety, in my original post. Can > > *anyone* see any problems with it? Reproduced again: > > > > > 127.0.0.1:allow,RELAYCLIENT="" > > > 192.168.0.:allow,RELAYCLIENT="" > > > :allow > > > > >> or some other problem. > > > > OK, great, but WHAT OTHER PROBLEM!? This is making my (thinning ) hair > > go grey. I'd appreciate any suggestions as what the 'other problem' > > might be. > > Is that an actual paste of your tcp.smtp or did you copy it in by hand? > > --Adam
Re: tcprules, rcpthost, ip address problem
That's an actual paste of the file. BD Adam McKenna wrote: > On Mon, Jul 03, 2000 at 04:43:52PM -0700, Barry Dwyer wrote: > > >> Either there is a typo in your tcp.smtp . > > > > My tcp.smtp is included, in its entirety, in my original post. Can > > *anyone* see any problems with it? Reproduced again: > > > > > 127.0.0.1:allow,RELAYCLIENT="" > > > 192.168.0.:allow,RELAYCLIENT="" > > > :allow > > > > >> or some other problem. > > > > OK, great, but WHAT OTHER PROBLEM!? This is making my (thinning ) hair > > go grey. I'd appreciate any suggestions as what the 'other problem' > > might be. > > Is that an actual paste of your tcp.smtp or did you copy it in by hand? > > --Adam
Re: tcprules, rcpthost, ip address problem
On Mon, Jul 03, 2000 at 04:43:52PM -0700, Barry Dwyer wrote: > >> Either there is a typo in your tcp.smtp . > > My tcp.smtp is included, in its entirety, in my original post. Can > *anyone* see any problems with it? Reproduced again: > > > 127.0.0.1:allow,RELAYCLIENT="" > > 192.168.0.:allow,RELAYCLIENT="" > > :allow > > >> or some other problem. > > OK, great, but WHAT OTHER PROBLEM!? This is making my (thinning ) hair > go grey. I'd appreciate any suggestions as what the 'other problem' > might be. Is that an actual paste of your tcp.smtp or did you copy it in by hand? --Adam
Re: tcprules, rcpthost, ip address problem
On Mon, Jul 03, 2000 at 01:10:05PM -0700, Barry Dwyer wrote: > > 127.0.0.1:allow,RELAYCLIENT="" > 192.168.0.:allow,RELAYCLIENT="" > :allow did you run tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtp after creating that /etc/tcp.smtp file? -- wolfgang __ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com
Re: tcprules, rcpthost, ip address problem
>> Either there is a typo in your tcp.smtp . My tcp.smtp is included, in its entirety, in my original post. Can *anyone* see any problems with it? Reproduced again: > 127.0.0.1:allow,RELAYCLIENT="" > 192.168.0.:allow,RELAYCLIENT="" > :allow >> or some other problem. OK, great, but WHAT OTHER PROBLEM!? This is making my (thinning ) hair go grey. I'd appreciate any suggestions as what the 'other problem' might be. Barry
Re: tcprules, rcpthost, ip address problem
On Mon, Jul 03, 2000 at 01:10:05PM -0700, Barry Dwyer wrote: > Hi all, > > I've got qmail running properly on a system with a DMZ-firewall setup. > All the local clients are behind the firewall, addressed as 192.168.0.n. > The firewall (a debian box) and the mail server are connected to our > ADSL router and both have class-C addresses. The clients all have hosts > files referencing the mail server. > > My tcp.smtp file has proper settings to allow the local clients to work > as RELAYCLIENTS: > > 127.0.0.1:allow,RELAYCLIENT="" > 192.168.0.:allow,RELAYCLIENT="" > :allow > > (I've recompiled it just to be sure and, yes, the reference in the qmail > startup script points to the proper file '-x/etc/tcp.smtp.cdb') > > If I create a rcpthosts file with just the local domain in it (that's > all I want), then every local client that tries to send mail out to the > 'net gets a qmail error message saying the destination domain is not in > the list of receipt hosts (or something to that effect). > > Is the problem that qmail, running on a mail server, with it's class-C > address, doesn't like the "192" block addresses in tcp.smtp? I've set up > qmail servers before as multihomed systems with a class-C card *and* and > internal one. Must I do that here? No. qmail doesn't give special treatment to any IP addresses, AFAIK. Either there is a typo in your tcp.smtp or some other problem. --Adam
Re: tcprules, rcpthost, ip address problem
On Mon, Jul 03, 2000 at 06:12:26PM -0500, Christopher Tolley wrote: > Make sure you've used tcprules to hash your /etc/tcp.smtp file into > /etc/tcp.smtp.cdb and then RESTART your tcpserver -x > /etc/tcp.smtp/cdb...etc. The changes to tcp.smtp.cdb won't take effect > until you restart. It seems like there has been a surge in misinformation lately on this list. The above is COMPLETELY false. You do NOT need to "restart your tcpserver" for the changes to take effect. --Adam
Re: tcprules, rcpthost, ip address problem
Make sure you've used tcprules to hash your /etc/tcp.smtp file into /etc/tcp.smtp.cdb and then RESTART your tcpserver -x /etc/tcp.smtp/cdb...etc. The changes to tcp.smtp.cdb won't take effect until you restart. -CT - Original Message - From: "Barry Dwyer" <[EMAIL PROTECTED]> To: "QMAIL" <[EMAIL PROTECTED]> Sent: Monday, July 03, 2000 3:10 PM Subject: tcprules, rcpthost, ip address problem > Hi all, > > I've got qmail running properly on a system with a DMZ-firewall setup. > All the local clients are behind the firewall, addressed as 192.168.0.n. > The firewall (a debian box) and the mail server are connected to our > ADSL router and both have class-C addresses. The clients all have hosts > files referencing the mail server. > > My tcp.smtp file has proper settings to allow the local clients to work > as RELAYCLIENTS: > > 127.0.0.1:allow,RELAYCLIENT="" > 192.168.0.:allow,RELAYCLIENT="" > :allow > > (I've recompiled it just to be sure and, yes, the reference in the qmail > startup script points to the proper file '-x/etc/tcp.smtp.cdb') > > If I create a rcpthosts file with just the local domain in it (that's > all I want), then every local client that tries to send mail out to the > 'net gets a qmail error message saying the destination domain is not in > the list of receipt hosts (or something to that effect). > > Is the problem that qmail, running on a mail server, with it's class-C > address, doesn't like the "192" block addresses in tcp.smtp? I've set up > qmail servers before as multihomed systems with a class-C card *and* and > internal one. Must I do that here? > > Thanks > Barry Dwyer >
Re: tcprules, rcpthost, ip address problem
Barry Dwyer writes: > If I create a rcpthosts file with just the local domain in it (that's > all I want), then every local client that tries to send mail out to the > 'net gets a qmail error message saying the destination domain is not in > the list of receipt hosts (or something to that effect). Does rcpthosts contain `.domain.tld', or just `domain.tld'? If the latter, it will accept messages only from that host. Use the former to accept messages from all hosts in that domain. paul
tcprules, rcpthost, ip address problem
Hi all, I've got qmail running properly on a system with a DMZ-firewall setup. All the local clients are behind the firewall, addressed as 192.168.0.n. The firewall (a debian box) and the mail server are connected to our ADSL router and both have class-C addresses. The clients all have hosts files referencing the mail server. My tcp.smtp file has proper settings to allow the local clients to work as RELAYCLIENTS: 127.0.0.1:allow,RELAYCLIENT="" 192.168.0.:allow,RELAYCLIENT="" :allow (I've recompiled it just to be sure and, yes, the reference in the qmail startup script points to the proper file '-x/etc/tcp.smtp.cdb') If I create a rcpthosts file with just the local domain in it (that's all I want), then every local client that tries to send mail out to the 'net gets a qmail error message saying the destination domain is not in the list of receipt hosts (or something to that effect). Is the problem that qmail, running on a mail server, with it's class-C address, doesn't like the "192" block addresses in tcp.smtp? I've set up qmail servers before as multihomed systems with a class-C card *and* and internal one. Must I do that here? Thanks Barry Dwyer
Re: Change hostname & IP Address
Iman Budi Setiawan <[EMAIL PROTECTED]> wrote: >I have problem with qmail when changing my hostname and IP address. >Please, tell me the steps to set my qmail's configuration (like change the >files in /var/qmail/control directory). 1) stop qmail 2) for all files in /var/qmail/control change old hostname to new hostname 3) restart qmail -Dave
Change hostname & IP Address
Dear all, I have problem with qmail when changing my hostname and IP address. Please, tell me the steps to set my qmail's configuration (like change the files in /var/qmail/control directory). Regards, ~iman
Re: Virtual Domains Over 1 IP Address
also sprach jaybc1: > Hello all, > > What is the best route for handling multiple domains and associated things > like mail delivery / pop3 user logins over 1 ip address? Probably either vpopmail (<http://www.inter7.com/vpopmail/>) or vmailmgr (<http://www.vmailmgr.org/>). /pg -- Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED] --- > > Other than the fact Linux has a cool name, could someone explain why I > > should use Linux over BSD? > > No. That's it. The cool name, that is. We worked very hard on > creating a name that would appeal to the majority of people, and it > certainly paid off: thousands of people are using linux just to be able > to say "OS/2? Hah. I've got Linux. What a cool name". 386BSD made the > mistake of putting a lot of numbers and weird abbreviations into the > name, and is scaring away a lot of people just because it sounds too > technical. (Linus Torvalds' follow-up to a question about Linux)
Virtual Domains Over 1 IP Address
Hello all, What is the best route for handling multiple domains and associated things like mail delivery / pop3 user logins over 1 ip address? J > On Fri, Jun 23, 2000 at 06:53:06PM +0200, Robert Sander wrote: > > Hi! > > > > Where has this message gone? > Have you checked /var/qmail/alias/Mailbox or /var/qmail/alias/Maildir/ ? > If memory serves that's where messages end up with which qmail doesn't know > what to do... > The other alternative is the postmaster's mailbox > > > Jun 23 18:39:05 einstein qmail: 961778345.318647 new msg 16012 > > Jun 23 18:39:05 einstein qmail: 961778345.318807 info msg 16012: bytes 294 from <> qp 30890 uid 71 > > Jun 23 18:39:05 einstein qmail: 961778345.326744 starting delivery 27207: msg 16012 to local @einstein.epigenomics.de > > Jun 23 18:39:05 einstein qmail: 961778345.327033 status: local 1/10 remote 0/20 > > Jun 23 18:39:05 einstein qmail: 961778345.329393 delivery 27207: success: > > Jun 23 18:39:05 einstein qmail: 961778345.329472 status: local 0/10 remote 0/20 > > Jun 23 18:39:05 einstein qmail: 961778345.329529 end msg 16012 > > > > It came from me, speaking smtp over telnet and doing a mistake with mail from > > and rcpt to ;-)... > > > > Greetings > > -- > > Robert Sander > > Epigenomics GmbH www.epigenomics.de Kastanienallee 24 > > +493024345330 10435 Berlin > > -- > http://therookie.dyndns.org >
Changing the IP address
Hello, I have one Qmail Server with a few of domains (I use vpopmail). This server has got one Internal IP Address (192.168.0.x), and another Linux Server (with one internal IP address and one external IP address) use the portfw sentence for redirect the email traffic. The Qmail Server also has an invented name and domain that now only works in "internal mode" (with an Internal IP address 192.168.0.x). I must change this configuration. I need to change the IP address for one real IP address, and the name and domain name for another real name and domain. I must change the IP with ifconfig and the name in the file (/etc/hostname). What is the file for change the domain? How other files should I change (Qmail files, vpopmail files, etc)? Thanks for all.
Re: ip address
>thank you very much for the info about the ip address i will bring back the gateway. > >my real problem is this i can send mail successfully but the problem is when i check the mail i send their gone. > >sample i have a user vhernz in my qmail server. i configured my outlook my incoming mail and outgoing mail as 208.235.228.2 thats the ip add of my qmail server then i send mail to my self vhernz. then i got successful delivery like this > >Jun 23 15:10:18 qmail qmail: 961744218.845561 info msg 95445: bytes 1290 from <[EMAIL PROTECTED]> qp 378 uid 502 >Jun 23 15:10:18 qmail qmail: 961744218.982088 starting delivery 20: msg 95445 to remote [EMAIL PROTECTED] >Jun 23 15:10:18 qmail qmail: 961744218.985623 status: local 0/10 remote 1/20 >Jun 23 15:10:24 qmail qmail: 961744224.284874 delivery 20: success: 216.42.80.32_accepted_message./Remote_host_said:_250_ok_961742865_qp_39020/ >Jun 23 15:10:24 qmail qmail: 961744224.290795 status: local 0/10 remote 0/20 >Jun 23 15:10:24 qmail qmail: 961744224.293684 end msg 95445 > >but when i check my my mail in /home/vhernz i got no mail > >my /var/qmail/rc file is this > ># Bunch of comments here >exec env - PATH="/var/qmail/bin:$PATH" \ >qmail-start './Maildir/' splogger qmail > >i dont want to give up in using qmail please do help me > >hope you understand my problem now :) > >sorry for my first mail if its very confusing... > >thanks again in advance >
Re: ip address
Vince, i would love to help you out but i'm not sure i understand your problem. This message and the following message are very confusing... from what i gathered, when you remove your 'gateway' on the machine, your mails stop flowing? Is this correct? As for only seeing ip addresses in the logs, that's fine. Jun 23 01:14:02 ns1 qmail: 96172.203867 delivery 33995: success: 206.29.138.8_accepted_message./Remote_host_said:_250_ok_961744098_qp_7070/ Jun 23 01:20:52 ns1 qmail: 961744852.911494 delivery 33997: success: 206.29.138.8_accepted_message./Remote_host_said:_250_ok_961744509_qp_8059/ Jun 23 01:29:13 ns1 qmail: 961745353.594793 delivery 34005: success: 216.33.151.135_accepted_message./Remote_host_said:_250_Requested_mail_action_okay,_completed/ On Fri, 23 Jun 2000, Vince wrote: | | | why is that in my qmail/maillog when i send email the logs is like this | | "delivery 20: success: | 216.42.80.32_accepted_message./Remote_host_said:_250_ok_961742865_qp_39020/" | | | why there is an ip address 216.42.80.32 there may be thats the problem why | my mails are gone in my qmail machine but when i send to to other like | hotmail account i succesfully got the mail. | | | | -- ___ _ __ _ __ /___ ___ /__ John Gonzalez/Net.Tech __ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC! _ / / / `__/ /_ / / / / / / /_/ / / /__ (505)437-7600/fax-437-3052 /_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com [-[system info]---] 1:25am up 43 days, 7:28, 3 users, load average: 0.08, 0.11, 0.11
follow up to the previous message ip address
why is that in my qmail/maillog when i send email the logs is like this "delivery 20: success: 216.42.80.32_accepted_message./Remote_host_said:_250_ok_961742865_qp_39020/" why there is an ip address 216.42.80.32 there may be thats the problem why my mails are gone in my qmail machine but when i send to to other like hotmail account i succesfully got the mail. then when i try to remove the gateway of my machine here is my maillog Jun 23 15:29:48 qmail qmail: 961745388.327622 delivery 1: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/ Jun 23 15:29:48 qmail qmail: 961745388.332040 status: local 0/10 remote 0/20 plese help me...
ip address
why is that in my qmail/maillog when i send email the logs is like this "delivery 20: success: 216.42.80.32_accepted_message./Remote_host_said:_250_ok_961742865_qp_39020/" why there is an ip address 216.42.80.32 there may be thats the problem why my mails are gone in my qmail machine but when i send to to other like hotmail account i succesfully got the mail.
Re: Allowing relaying for selected users - NOT by IP address
On Mon, 22 May 2000, Ed Woodson wrote: > I have been scanning the list archives for hours, trying to figure out how I > can accomplish this: > > I have a qmail server up and running perfectly, doing selective relaying for > our internal network only. I would like to further limit this for selected > users, if possible. My ultimate goal is to have two classes of users, one > class which can use qmail for both "external" and "internal" mail, and > another class which is limited to "internal" mail only. > > Please correct me if I am wrong, but it appears that my choices are: > > 1) selectively relay based upon IP address > 2) control relaying by envelope sender (using the "relaymailfrom" patch) > > Is it possible to combine the two? For example, can I allow relaying from > my own network only with (1), and also use the "relaymailfrom" patch to > restrict this _further_ to messages with a certain envelope sender? > > I know that (2) is closer to what I am trying to do, but it seems to add to > those allowed to relay, not to further restrict it. Also, I know that it is > easy for a user to forge the envelope sender, but I am not worried about > that (as long as I can still be assured it is coming from our local > network). > > Please tell me if I am overlooking something obvious > i have never tried this, but if you are using secure workstations eg. Windows NT or Linux or any other multi-user OS then you might be able to install ident daemons on them. in the hosts.allow you can add username lookups to allow relaying. i'm not sure if this is possible with tcpserver. i'm sure that there's a better way and i'll wait for it too!
Re: Allowing relaying for selected users - NOT by IP address
On Mon, May 22, 2000 at 10:21:23AM -0500, Ed Woodson wrote:
> I have been scanning the list archives for hours, trying to figure out how I
> can accomplish this:
>
> I have a qmail server up and running perfectly, doing selective relaying for
> our internal network only. I would like to further limit this for selected
> users, if possible. My ultimate goal is to have two classes of users, one
> class which can use qmail for both "external" and "internal" mail, and
> another class which is limited to "internal" mail only.
>
> Please correct me if I am wrong, but it appears that my choices are:
>
> 1) selectively relay based upon IP address
> 2) control relaying by envelope sender (using the "relaymailfrom" patch)
>
> Is it possible to combine the two? For example, can I allow relaying from
> my own network only with (1), and also use the "relaymailfrom" patch to
> restrict this _further_ to messages with a certain envelope sender?
>
> I know that (2) is closer to what I am trying to do, but it seems to add to
> those allowed to relay, not to further restrict it. Also, I know that it is
> easy for a user to forge the envelope sender, but I am not worried about
> that (as long as I can still be assured it is coming from our local
> network).
Someone else asked for this a long time ago, and I whipped up the following
patch which should help you.
Chris
This patch lets you control SMTP relaying based on envelope sender address.
Note that this is not secure--it's trivial to forge a message's envelope
sender. But it's something that people have asked for, and combined with
tarpitting and running your SMTP daemon on a non-standard port, it may give you
an acceptable level of safety.
As with the unpatched version of qmail-smtpd, relaying is allowed whenever
RELAYCLIENT is set. This patch adds a control file called relaymailfrom;
envelope senders listed in the file will also be allowed to relay. Entries in
relaymailfrom can be e-mail addresses, or just the domain (with the @ sign). So
if I want [EMAIL PROTECTED] and anyone in domain2.com to be able to relay, my
control/relaymailfrom file would contain:
[EMAIL PROTECTED]
@domain2.com
RELAYBYADDRESS must be set in qmail-smtpd's environment in order for relaying
by envelope sender to be allowed. So, for example, if you wanted to allow
anyone at 192.168.15.* to relay through your server as long as his envelope
sender address was in your relaymailfrom file, you'd have the following in your
tcpserver rules file (assuming you're using tcpserver and not inetd):
192.168.15.:allow,RELAYBYADDRESS=""
--- qmail-smtpd.c.orig Mon Jun 15 06:53:16 1998
+++ qmail-smtpd.c Wed May 5 23:31:23 1999
@@ -81,6 +81,7 @@
char *remoteinfo;
char *local;
char *relayclient;
+char *relayok;
stralloc helohost = {0};
char *fakehelo; /* pointer into helohost, or 0 */
@@ -96,6 +97,9 @@
int bmfok = 0;
stralloc bmf = {0};
struct constmap mapbmf;
+int rmfok = 0;
+stralloc rmf = {0};
+struct constmap maprmf;
void setup()
{
@@ -117,6 +121,13 @@
if (bmfok)
if (!constmap_init(&mapbmf,bmf.s,bmf.len,0)) die_nomem();
+ if ( env_get("RELAYBYADDRESS") ) {
+rmfok = control_readfile(&rmf,"control/relaymailfrom",0);
+if (rmfok == -1) die_control();
+if (rmfok)
+ if (!constmap_init(&maprmf,rmf.s,rmf.len,0)) die_nomem();
+ }
+
if (control_readint(&databytes,"control/databytes") == -1) die_control();
x = env_get("DATABYTES");
if (x) { scan_ulong(x,&u); databytes = u; }
@@ -130,7 +141,7 @@
remotehost = env_get("TCPREMOTEHOST");
if (!remotehost) remotehost = "unknown";
remoteinfo = env_get("TCPREMOTEINFO");
- relayclient = env_get("RELAYCLIENT");
+ relayok = relayclient = env_get("RELAYCLIENT");
dohelo(remotehost);
}
@@ -208,6 +219,17 @@
return 0;
}
+int rmfcheck()
+{
+ int j;
+ if (!rmfok) return 0;
+ if (constmap(&maprmf,addr.s,addr.len - 1)) return 1;
+ j = byte_rchr(addr.s,addr.len,'@');
+ if (j < addr.len)
+if (constmap(&maprmf,addr.s + j,addr.len - j - 1)) return 1;
+ return 0;
+}
+
int addrallowed()
{
int r;
@@ -241,6 +263,7 @@
{
if (!addrparse(arg)) { err_syntax(); return; }
flagbarf = bmfcheck();
+ if (!relayok) if (rmfcheck()) relayclient = ""; else relayclient = 0;
seenmail = 1;
if (!stralloc_copys(&rcptto,"")) die_nomem();
if (!stralloc_copys(&mailfrom,addr.s)) die_nomem();
Allowing relaying for selected users - NOT by IP address
I have been scanning the list archives for hours, trying to figure out how I can accomplish this: I have a qmail server up and running perfectly, doing selective relaying for our internal network only. I would like to further limit this for selected users, if possible. My ultimate goal is to have two classes of users, one class which can use qmail for both "external" and "internal" mail, and another class which is limited to "internal" mail only. Please correct me if I am wrong, but it appears that my choices are: 1) selectively relay based upon IP address 2) control relaying by envelope sender (using the "relaymailfrom" patch) Is it possible to combine the two? For example, can I allow relaying from my own network only with (1), and also use the "relaymailfrom" patch to restrict this _further_ to messages with a certain envelope sender? I know that (2) is closer to what I am trying to do, but it seems to add to those allowed to relay, not to further restrict it. Also, I know that it is easy for a user to forge the envelope sender, but I am not worried about that (as long as I can still be assured it is coming from our local network). Please tell me if I am overlooking something obvious
Re: ip address scheme
Thanks . Actually i made a mistake writing this mail. I will make it 255.255.255.0. Any other issue or should I finalize this scheme. I want it for Intranet that means it should not contain any internet IP address. Thank you kapil Anton Pirnat wrote: > >>>>>>>>>>>>>>>>>> Ursprüngliche Nachricht <<<<<<<<<<<<<<<<<< > > Am 19.05.00, 01:54:23, schrieb kapil sharma <[EMAIL PROTECTED]> > zum Thema ip address scheme: > > > Hi, > > I am implementing a fresh Intranet for our organization. i am > assigning > > the following IP scheme: > > IP address range: 192.168.254.1- 192.168.254.254 > > netmask : 254.254.254.0 > > Is there any mistake in this scheme. Please help!! > > yep.. the netmsak (as most other things at computers do) start its > counting at 0 til 255 (256 possible values) . So it must be an > 255.255.255.0 in your case. > > hth > > Anton Pirnat > > Does it belong to qmail? (is there a given trademark for that > sentence, Dave?)
Re: ip address scheme
>>>>>>>>>>>>>>>>>> Ursprüngliche Nachricht <<<<<<<<<<<<<<<<<< Am 19.05.00, 01:54:23, schrieb kapil sharma <[EMAIL PROTECTED]> zum Thema ip address scheme: > Hi, > I am implementing a fresh Intranet for our organization. i am assigning > the following IP scheme: > IP address range: 192.168.254.1- 192.168.254.254 > netmask : 254.254.254.0 > Is there any mistake in this scheme. Please help!! yep.. the netmsak (as most other things at computers do) start its counting at 0 til 255 (256 possible values) . So it must be an 255.255.255.0 in your case. hth Anton Pirnat Does it belong to qmail? (is there a given trademark for that sentence, Dave?)
ip address scheme
Hi, I am implementing a fresh Intranet for our organization. i am assigning the following IP scheme: IP address range: 192.168.254.1- 192.168.254.254 netmask : 254.254.254.0 Is there any mistake in this scheme. Please help!!
Re: Changing the IP address used by qmail....
On Wed, May 17, 2000 at 10:40:03AM +0100, James Raftery wrote: > To generalise the previous question a little, is there a simple way of > getting qmail-rspawn/qmail-remote to bind to a particular local > interface for sending outgoing mail? I would like to have a particular > virtual interface used for SMTP alone. Getting tcpserver to listen on > that interface is a doddle, but confining outgoing SMTP traffic (and > leaving other services unaffected, hence not using routing) to using > that interface seems non-trivial. I have ported the patch to qmail 1.01 from the qmail.org web page to qmail 1.03 and incorporated it into an RPM for my system (the RPM is basically the memphis rpm with the patch applied). If you want a copy then email me and I'll either send you the patch or the RPM - your choice. It allows you to do just what you requested. Andy -- BoomerangDomains support - [EMAIL PROTECTED] domain registration, email and web forwarding for just $25 a year
Re: Changing the IP address used by qmail....
On Tue, May 16, 2000 at 05:48:04PM -0400, Adam McKenna wrote: > This has nothing to do with qmail-smtpd (or any other part of qmail for that > matter). Check your routing table. To generalise the previous question a little, is there a simple way of getting qmail-rspawn/qmail-remote to bind to a particular local interface for sending outgoing mail? I would like to have a particular virtual interface used for SMTP alone. Getting tcpserver to listen on that interface is a doddle, but confining outgoing SMTP traffic (and leaving other services unaffected, hence not using routing) to using that interface seems non-trivial. james -- James Raftery (JBR54) - Programmer Hostmaster - IE TLD Hostmaster IE Domain Registry - www.domainregistry.ie - (+353 1) 706 2375 "Managing 4000 customer domains with BIND has been a lot like herding cats." - Mike Batchelor, on [EMAIL PROTECTED]
Re: Changing the IP address used by qmail....
This has nothing to do with qmail-smtpd (or any other part of qmail for that matter). Check your routing table. --Adam On Tue, May 16, 2000 at 03:44:13PM -0600, Steve Wolfe wrote: > > Today, I bound another IP address to our ethernet card. Eth0 is > 209.90.117.130, eth0:1 is 209.90.117.144, and now, eth0:2 is 209.90.117.140 > . > > The first two IP's were running jim-dandy for some time, now that I've > added the third address, outgoing mail is sent from 209.90.117.140, not > .130, as it should be. > > qmail-smtpd is being started as follows: > > /usr/local/bin/tcpserver -v -x /etc/tcp.smtp.cdb -u 80 -g 80 -c100 0 smt > p /var/qmail/bin/qmail-smtpd 2>&1 | /var/qmail/bin/splogger smtpd 3 & > > Am I correct in assuming that it should be started like this: > > /usr/local/bin/tcpserver -v -x /etc/tcp.smtp.cdb -u 80 -g 80 -c100 > 209.90.117.130 0 > smtp /var/qmail/bin/qmail-smtpd 2>&1 | /var/qmail/bin/splogger smtpd 3 & > > ? > > steve >
Changing the IP address used by qmail....
Today, I bound another IP address to our ethernet card. Eth0 is 209.90.117.130, eth0:1 is 209.90.117.144, and now, eth0:2 is 209.90.117.140 . The first two IP's were running jim-dandy for some time, now that I've added the third address, outgoing mail is sent from 209.90.117.140, not .130, as it should be. qmail-smtpd is being started as follows: /usr/local/bin/tcpserver -v -x /etc/tcp.smtp.cdb -u 80 -g 80 -c100 0 smt p /var/qmail/bin/qmail-smtpd 2>&1 | /var/qmail/bin/splogger smtpd 3 & Am I correct in assuming that it should be started like this: /usr/local/bin/tcpserver -v -x /etc/tcp.smtp.cdb -u 80 -g 80 -c100 209.90.117.130 0 smtp /var/qmail/bin/qmail-smtpd 2>&1 | /var/qmail/bin/splogger smtpd 3 & ? steve
Adding local IP address to ipme
I have a farm of qmail servers sitting behind a load balancer. I'm having a problem with being a secondary MX for a domain, because the individual qmail servers in the farm don't realize that the IP address of the load balancer actually points to them. They keep trying to re-deliver to the load balancer's address, which connects them back to a different mail server within the farm, which does the same thing, until the message bounces because of too many hops. Is there a patch that will let me add addresses to the ipme structure that qmail uses to determine whether the MX record for a host is actually itself? Reading back over that, it's a little confusing. Here's an example. I have 25 qmail servers, 10.0.0.1 through 10.0.0.25. The load balancer, which will semi-randomly select one of the actual servers to pass the connection on to, has an address of 1.2.3.4. Domains for which we are a secondary MX have a less preferred MX record that points to 1.2.3.4. When a message comes in to be queued, it comes in to 1.2.3.4, which is redirected to (for example) 10.0.0.5. The domain is in its rcpthosts, but not its locals, so 10.0.0.5 tries to forward it on to the next best-preference MX. It tries to connect to the primary MX, fails, and then tries to connect to the secondary, 1.2.3.4. It doesn't realize that it is already handling mail for 1.2.3.4, so it opens up another connection to 1.2.3.4, which redirects it to (for example) 10.0.0.16. This process repeats until the message bounces. I'm looking at patching ipme.c and giving it a config file, but it seems to me that somebody must have already done this. Can anybody point me in the right direction? I'm using qmail-1.0.3+ldap. Thanks, --ScottG.
Looking for a patch to bind outgoing IP address depending on sender domain
Hi, I'm new to qmail and I want to use it for virtual domain mailing on a host who has an IP address per domain (doing accounting per IP address): Example: Host serves DomainA on IpA (MX entry in DNS) DomainB on IpB (MX entry in DNS) Local bind for outgoing e-mail depending on sender domain Unlike http://qmail.mirrors.Space.Net/local-bind do that for receipent domain i.e. a client of DomainA has already send an e-mail to the virtual SMTP host. Now this e-mail is send out somewhere to the Internet. qmail-remote should bind IpA to send this e-mail IpA given by table or taken from DNS/MX resolving Thank you very much for help, Peter
RE: Sending to an IP address
I disagreed too but I couldn't be bothered replying. I'm using it at the moment for testing because our current domain is handled by another server I don't want to change the MX records until I've tested it a bit. Wilson -- From: Scott D. Yelich[SMTP:[EMAIL PROTECTED]] Sent: Thursday, 3 February 2000 2:51 To: Bruno Wolff III Cc: Sam; '[EMAIL PROTECTED]' Subject: Re: Sending to an IP address -BEGIN PGP SIGNED MESSAGE- On Wed, 2 Feb 2000, Bruno Wolff III wrote: > On Wed, Feb 02, 2000 at 12:29:03AM -0500, > Sam <[EMAIL PROTECTED]> wrote: > > On Wed, 2 Feb 2000, Wilson Fletcher wrote: > > > I ried to send to wilson@[203.26.11.154] but it failed. Can someone tell me why ? > > Because this form of addressing is obsolete and deprecated. Once upon a > > time MX records were few and far between. That is no longer the case, so > > there's no need for this nonsense. I disagree. I find this very useful when forwarding email. Scott -BEGIN PGP SIGNATURE- Version: 2.6.2 iQCVAwUBOJhSmR4PLs9vCOqdAQE2ygQApy1LjtORSD/asso2wE1iL7lsO9uETg5w n8e/ApIxQwMaN0NcIrk2l5+uKcgsLo+SaW++De/uAeaifwSnWSc2SlVHVxZR+cGn 17LDnQeXsgnBmRPw24XXZtGsFI8AjhYAGwwFY9yfM55WaFxXVSqMF9rHyOBOlMFR O905dE2M4Do= =bhsV -END PGP SIGNATURE-
Re: Sending to an IP address
-BEGIN PGP SIGNED MESSAGE- On Wed, 2 Feb 2000, Bruno Wolff III wrote: > On Wed, Feb 02, 2000 at 12:29:03AM -0500, > Sam <[EMAIL PROTECTED]> wrote: > > On Wed, 2 Feb 2000, Wilson Fletcher wrote: > > > I ried to send to wilson@[203.26.11.154] but it failed. Can someone tell me why ? > > Because this form of addressing is obsolete and deprecated. Once upon a > > time MX records were few and far between. That is no longer the case, so > > there's no need for this nonsense. I disagree. I find this very useful when forwarding email. Scott -BEGIN PGP SIGNATURE- Version: 2.6.2 iQCVAwUBOJhSmR4PLs9vCOqdAQE2ygQApy1LjtORSD/asso2wE1iL7lsO9uETg5w n8e/ApIxQwMaN0NcIrk2l5+uKcgsLo+SaW++De/uAeaifwSnWSc2SlVHVxZR+cGn 17LDnQeXsgnBmRPw24XXZtGsFI8AjhYAGwwFY9yfM55WaFxXVSqMF9rHyOBOlMFR O905dE2M4Do= =bhsV -END PGP SIGNATURE-
Re: Sending to an IP address
On Wed, Feb 02, 2000 at 12:29:03AM -0500, Sam <[EMAIL PROTECTED]> wrote: > On Wed, 2 Feb 2000, Wilson Fletcher wrote: > > > I ried to send to wilson@[203.26.11.154] but it failed. Can someone tell me why ? > > Because this form of addressing is obsolete and deprecated. Once upon a > time MX records were few and far between. That is no longer the case, so > there's no need for this nonsense. Except when you are trying to get email through when DNS is broken. I remember getting ticked off at the people who wrote send mail, because it insisted on doing reverse lookups of IP addresses before sending email on to an address with a domain litteral. Trying to send the messages with telnet was a pain.
RE: Sending to an IP address
BRILLIANT ! that's it. So a summary. All I needed to do is put mclachlan.com.au in localiphost. qmail replaces the ip with the FQDN & then we go onto rcpthosts etc. Thankyou everyone for your contributions I really appreciate it. Wilson Fletcher -- From: Anand Buddhdev[SMTP:[EMAIL PROTECTED]] Sent: Wednesday, 2 February 2000 17:40 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject:Re: Sending to an IP address On Wed, Feb 02, 2000 at 04:42:55PM +1100, Wilson Fletcher wrote: > OK added [203.26.11.154] to both control/locals & control/rcpthosts > still not luck (yes I restarted qmail) That's because it's the wrong way of doing things. Read the qmail-smtpd man page, and see the section about the control file "localiphost". -- See complete headers for more info
Re: Sending to an IP address
On Wed, Feb 02, 2000 at 04:42:55PM +1100, Wilson Fletcher wrote: > OK added [203.26.11.154] to both control/locals & control/rcpthosts > still not luck (yes I restarted qmail) That's because it's the wrong way of doing things. Read the qmail-smtpd man page, and see the section about the control file "localiphost". -- See complete headers for more info
Re: Sending to an IP address
On Wed, Feb 02, 2000 at 05:01:02PM +1100, Wilson Fletcher wrote: > hmmm no square brackets I might try removing them. All this bracket talk is nonsense. And you don't have to restart anything after making a change to rcpthosts--it's reread for every incoming smtp connection. If the bracketed IP address in the e-mail address is one of the computer's IP addresses, then the contents of control/localiphost (which defaults to control/me) is the domain that's checked for in control/rcpthosts. So whatever's in control/me (or control/localiphost if you have it) needs to be in control/rcpthosts in order for this to work for you. Chris
Re: Sending to an IP address
hmmm... I'm pretty sure you have to kill qmail-send. killproc is a handy tool if you have it around. you can just do a: killproc -HUP `which qmail-send` (assuming qmail-send is in your path; else give it the path to qmail-send) - Original Message - From: "Wilson Fletcher" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: 02 February 2000, Wednesday 00:59 Subject: RE: Sending to an IP address | I did this: | | # Stop qmail. | set $(/bin/ps aux | /bin/grep qmail-lspawn) | PID=$2 | echo -n "Killing qmail process: " | echo $PID | kill -9 $PID | rm -f /var/lock/subsys/qmail | echo "done" | ;; | | | -- | From: Keith Warno[SMTP:[EMAIL PROTECTED]] | Sent: Wednesday, 2 February 2000 17:01 | To: [EMAIL PROTECTED] | Subject: Re: Sending to an IP address | | I tried sending a message to wilson@[203.26.11.154]. | | The response I received is: | | Hi. This is the qmail-send program at mailbox.muao-inc.net. | I'm afraid I wasn't able to deliver your message to the following addresses. | This is a permanent error; I've given up. Sorry it didn't work out. | | : | 203.26.11.154 does not like recipient. | Remote host said: 553 sorry, that domain isn't in my list of allowed | rcpthosts ( | Giving up on 203.26.11.154. | | | hmmm did you just kill -HUP `pidof qmail-send` or did you shut down and | restart qmail completely? If you didn't do the latter, try it. | | - Original Message - | From: "Wilson Fletcher" <[EMAIL PROTECTED]> | To: <[EMAIL PROTECTED]> | Sent: 02 February 2000, Wednesday 00:42 | Subject: RE: Sending to an IP address | | | | | | OK added [203.26.11.154] to both control/locals & control/rcpthosts still | not luck (yes I restarted qmail) | |
RE: Sending to an IP address
hmmm no square brackets I might try removing them. -- From: Tim Hunter[SMTP:[EMAIL PROTECTED]] Sent: Wednesday, 2 February 2000 16:55 To: [EMAIL PROTECTED] Subject:RE: Sending to an IP address I just tested this with my qmail config with my ip in rcpthosts and locals I received mail sent to my ip from an outside SMTP server [root@mail control]# cat rcpthosts mail.cimx.com cimx.com 206.112.223.188 [root@mail control]# cat locals mail.cimx.com cimx.com 206.112.223.188 [root@mail control]# Mail delivers like normal. here are my headers Return-Path: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] Received: (qmail 24970 invoked by uid 500); 2 Feb 2000 05:47:06 - Delivered-To: [EMAIL PROTECTED] Received: (qmail 24966 invoked from network); 2 Feb 2000 05:47:05 - Received: from fe2.rdc-kc.rr.com (HELO mail2.cinci.rr.com) (24.94.163.49) by mail.cimx.com with SMTP; 2 Feb 2000 05:47:05 - Received: from alcatraz ([24.29.20.43]) by mail2.cinci.rr.com with Microsoft SMTPSVC(5.5.1877.197.19); Tue, 1 Feb 2000 23:48:03 -0600 Message-Id: <[EMAIL PROTECTED]> X-Sender: [EMAIL PROTECTED] X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 02 Feb 2000 00:51:01 -0500 To: [EMAIL PROTECTED] From: Tim Hunter <[EMAIL PROTECTED]> Subject: test Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Return-Path: [EMAIL PROTECTED] X-UID: 113 I suggest you do a little more research before spitting off at the wrong people At 04:28 PM 2/2/00 +1100, you wrote: >hmmm. I don't think so. Here is my rcpthosts file: > > mclachlan.com.au > mclachlanlister.com.au > 203.26.11.154
RE: Sending to an IP address
I did this: # Stop qmail. set $(/bin/ps aux | /bin/grep qmail-lspawn) PID=$2 echo -n "Killing qmail process: " echo $PID kill -9 $PID rm -f /var/lock/subsys/qmail echo "done" ;; -- From: Keith Warno[SMTP:[EMAIL PROTECTED]] Sent: Wednesday, 2 February 2000 17:01 To: [EMAIL PROTECTED] Subject: Re: Sending to an IP address I tried sending a message to wilson@[203.26.11.154]. The response I received is: Hi. This is the qmail-send program at mailbox.muao-inc.net. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : 203.26.11.154 does not like recipient. Remote host said: 553 sorry, that domain isn't in my list of allowed rcpthosts ( Giving up on 203.26.11.154. hmmm did you just kill -HUP `pidof qmail-send` or did you shut down and restart qmail completely? If you didn't do the latter, try it. - Original Message - From: "Wilson Fletcher" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: 02 February 2000, Wednesday 00:42 Subject: RE: Sending to an IP address | | OK added [203.26.11.154] to both control/locals & control/rcpthosts still not luck (yes I restarted qmail)
RE: Sending to an IP address
I just tested this with my qmail config with my ip in rcpthosts and locals I received mail sent to my ip from an outside SMTP server [root@mail control]# cat rcpthosts mail.cimx.com cimx.com 206.112.223.188 [root@mail control]# cat locals mail.cimx.com cimx.com 206.112.223.188 [root@mail control]# Mail delivers like normal. here are my headers Return-Path: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] Received: (qmail 24970 invoked by uid 500); 2 Feb 2000 05:47:06 - Delivered-To: [EMAIL PROTECTED] Received: (qmail 24966 invoked from network); 2 Feb 2000 05:47:05 - Received: from fe2.rdc-kc.rr.com (HELO mail2.cinci.rr.com) (24.94.163.49) by mail.cimx.com with SMTP; 2 Feb 2000 05:47:05 - Received: from alcatraz ([24.29.20.43]) by mail2.cinci.rr.com with Microsoft SMTPSVC(5.5.1877.197.19); Tue, 1 Feb 2000 23:48:03 -0600 Message-Id: <[EMAIL PROTECTED]> X-Sender: [EMAIL PROTECTED] X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 02 Feb 2000 00:51:01 -0500 To: [EMAIL PROTECTED] From: Tim Hunter <[EMAIL PROTECTED]> Subject: test Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Return-Path: [EMAIL PROTECTED] X-UID: 113 I suggest you do a little more research before spitting off at the wrong people At 04:28 PM 2/2/00 +1100, you wrote: >hmmm. I don't think so. Here is my rcpthosts file: > > mclachlan.com.au > mclachlanlister.com.au > 203.26.11.154
RE: Sending to an IP address
OK added [203.26.11.154] to both control/locals & control/rcpthosts still not luck (yes I restarted qmail) -- From: Keith Warno[SMTP:[EMAIL PROTECTED]] Sent: Wednesday, 2 February 2000 16:47 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject:Re: Sending to an IP address To be a little more verbose: [www.xxx.yyy.zzz] (_with_ the brackets) must appear in control/rcpthosts and, if mail to said address is to be delivered locally, it must also appear (with the brackets) in control/locals. - Original Message - From: "Wilson Fletcher" <[EMAIL PROTECTED]> To: "'Tim Hunter'" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: 02 February 2000, Wednesday 00:28 Subject: RE: Sending to an IP address | hmmm. I don't think so. Here is my rcpthosts file: | | mclachlan.com.au | mclachlanlister.com.au | 203.26.11.154 | | As i said ... it works internally but not from my ISPs server. | | -- | From: Tim Hunter[SMTP:[EMAIL PROTECTED]] | Sent: Wednesday, 2 February 2000 15:59 | To: [EMAIL PROTECTED] | Subject: RE: Sending to an IP address | | your reply is your answer | Remote host said: 553 sorry, that domain isn't in my list of allowed | rcpthosts (#5.7.1) | | put 203.26.11.154 in rcpthosts if you want to receive mail for that host | read Life with qmail for more information | | | At 03:50 PM 2/2/00 +1100, you wrote: | >Well if you try mailing to it you will see. It is returned by the smtp | >server I use to send email which incidentally is also qmail. Here is the | >bounce message: | > | >Hi. This is the qmail-send program at gidora.zeta.org.au. | >I'm afraid I wasn't able to deliver your message to the following | >addresses. | >This is a permanent error; I've given up. Sorry it didn't work out. | > | >: | >203.26.11.154 does not like recipient. | >Remote host said: 553 sorry, that domain isn't in my list of allowed | >rcpthosts (#5.7.1) | >Giving up. | > | >--- Below this line is a copy of the message. | > | >Return-Path: <[EMAIL PROTECTED]> | >Received: (qmail 27215 invoked from network); 2 Feb 2000 04:36:16 - | >Received: from gw.mclachlan.com.au (HELO wraith.mclachlan.com.au) | >(203.26.11.145) | > by gidora.zeta.org.au with SMTP; 2 Feb 2000 04:36:16 - | >Received: by localhost with Microsoft MAPI; Wed, 2 Feb 2000 15:34:45 +1100 | >Message-ID: <[EMAIL PROTECTED]> | >From: Wilson Fletcher <[EMAIL PROTECTED]> | >Reply-To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> | >To: "'wilson@[203.26.11.154]'" | >Subject: Test | >Date: Wed, 2 Feb 2000 15:34:44 +1100 | >X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 | >MIME-Version: 1.0 | >Content-Type: text/plain; charset="us-ascii" | >Content-Transfer-Encoding: 7bit | > | >Test | > | > | > | >-- | >From: Chris Johnson[SMTP:[EMAIL PROTECTED]] | >Sent: Wednesday, 2 February 2000 15:32 | >To: [EMAIL PROTECTED] | >Cc: '[EMAIL PROTECTED]' | >Subject:Re: Sending to an IP address | > | >On Wed, Feb 02, 2000 at 03:25:58PM +1100, Wilson Fletcher wrote: | > > I tried to send to wilson@[203.26.11.154] but it failed. Can someone tell | >me | > > why ? | > | >I doubt it, unless you provide a detail or two. In what way did it fail? | > | >Chris | |
Re: Sending to an IP address
To be a little more verbose: [www.xxx.yyy.zzz] (_with_ the brackets) must appear in control/rcpthosts and, if mail to said address is to be delivered locally, it must also appear (with the brackets) in control/locals. - Original Message - From: "Wilson Fletcher" <[EMAIL PROTECTED]> To: "'Tim Hunter'" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: 02 February 2000, Wednesday 00:28 Subject: RE: Sending to an IP address | hmmm. I don't think so. Here is my rcpthosts file: | | mclachlan.com.au | mclachlanlister.com.au | 203.26.11.154 | | As i said ... it works internally but not from my ISPs server. | | -- | From: Tim Hunter[SMTP:[EMAIL PROTECTED]] | Sent: Wednesday, 2 February 2000 15:59 | To: [EMAIL PROTECTED] | Subject: RE: Sending to an IP address | | your reply is your answer | Remote host said: 553 sorry, that domain isn't in my list of allowed | rcpthosts (#5.7.1) | | put 203.26.11.154 in rcpthosts if you want to receive mail for that host | read Life with qmail for more information | | | At 03:50 PM 2/2/00 +1100, you wrote: | >Well if you try mailing to it you will see. It is returned by the smtp | >server I use to send email which incidentally is also qmail. Here is the | >bounce message: | > | >Hi. This is the qmail-send program at gidora.zeta.org.au. | >I'm afraid I wasn't able to deliver your message to the following | >addresses. | >This is a permanent error; I've given up. Sorry it didn't work out. | > | >: | >203.26.11.154 does not like recipient. | >Remote host said: 553 sorry, that domain isn't in my list of allowed | >rcpthosts (#5.7.1) | >Giving up. | > | >--- Below this line is a copy of the message. | > | >Return-Path: <[EMAIL PROTECTED]> | >Received: (qmail 27215 invoked from network); 2 Feb 2000 04:36:16 - | >Received: from gw.mclachlan.com.au (HELO wraith.mclachlan.com.au) | >(203.26.11.145) | > by gidora.zeta.org.au with SMTP; 2 Feb 2000 04:36:16 - | >Received: by localhost with Microsoft MAPI; Wed, 2 Feb 2000 15:34:45 +1100 | >Message-ID: <[EMAIL PROTECTED]> | >From: Wilson Fletcher <[EMAIL PROTECTED]> | >Reply-To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> | >To: "'wilson@[203.26.11.154]'" | >Subject: Test | >Date: Wed, 2 Feb 2000 15:34:44 +1100 | >X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 | >MIME-Version: 1.0 | >Content-Type: text/plain; charset="us-ascii" | >Content-Transfer-Encoding: 7bit | > | >Test | > | > | > | >-- | >From: Chris Johnson[SMTP:[EMAIL PROTECTED]] | >Sent: Wednesday, 2 February 2000 15:32 | >To: [EMAIL PROTECTED] | >Cc: '[EMAIL PROTECTED]' | >Subject:Re: Sending to an IP address | > | >On Wed, Feb 02, 2000 at 03:25:58PM +1100, Wilson Fletcher wrote: | > > I tried to send to wilson@[203.26.11.154] but it failed. Can someone tell | >me | > > why ? | > | >I doubt it, unless you provide a detail or two. In what way did it fail? | > | >Chris | |
RE: Sending to an IP address
hmmm. I don't think so. Here is my rcpthosts file: mclachlan.com.au mclachlanlister.com.au 203.26.11.154 As i said ... it works internally but not from my ISPs server. -- From: Tim Hunter[SMTP:[EMAIL PROTECTED]] Sent: Wednesday, 2 February 2000 15:59 To: [EMAIL PROTECTED] Subject:RE: Sending to an IP address your reply is your answer Remote host said: 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1) put 203.26.11.154 in rcpthosts if you want to receive mail for that host read Life with qmail for more information At 03:50 PM 2/2/00 +1100, you wrote: >Well if you try mailing to it you will see. It is returned by the smtp >server I use to send email which incidentally is also qmail. Here is the >bounce message: > >Hi. This is the qmail-send program at gidora.zeta.org.au. >I'm afraid I wasn't able to deliver your message to the following >addresses. >This is a permanent error; I've given up. Sorry it didn't work out. > >: >203.26.11.154 does not like recipient. >Remote host said: 553 sorry, that domain isn't in my list of allowed >rcpthosts (#5.7.1) >Giving up. > >--- Below this line is a copy of the message. > >Return-Path: <[EMAIL PROTECTED]> >Received: (qmail 27215 invoked from network); 2 Feb 2000 04:36:16 - >Received: from gw.mclachlan.com.au (HELO wraith.mclachlan.com.au) >(203.26.11.145) > by gidora.zeta.org.au with SMTP; 2 Feb 2000 04:36:16 - >Received: by localhost with Microsoft MAPI; Wed, 2 Feb 2000 15:34:45 +1100 >Message-ID: <[EMAIL PROTECTED]> >From: Wilson Fletcher <[EMAIL PROTECTED]> >Reply-To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> >To: "'wilson@[203.26.11.154]'" >Subject: Test >Date: Wed, 2 Feb 2000 15:34:44 +1100 >X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 >MIME-Version: 1.0 >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: 7bit > >Test > > > >-- >From: Chris Johnson[SMTP:[EMAIL PROTECTED]] >Sent: Wednesday, 2 February 2000 15:32 >To: [EMAIL PROTECTED] >Cc: '[EMAIL PROTECTED]' >Subject:Re: Sending to an IP address > >On Wed, Feb 02, 2000 at 03:25:58PM +1100, Wilson Fletcher wrote: > > I tried to send to wilson@[203.26.11.154] but it failed. Can someone tell >me > > why ? > >I doubt it, unless you provide a detail or two. In what way did it fail? > >Chris
Re: Sending to an IP address
The brackets are required. >From qmail-remote(8): The remote host is qmail-remote's first argument, host. qmail-remote sends the message to host, or to a mail exchanger for host listed in the Domain Name System, via the Simple Mail Transfer Protocol (SMTP). host can be either a fully-qualified domain name: silverton.berkeley.edu or an IP address enclosed in brackets: [128.32.183.163] If the mail is to be delivered locally to IP www.xxx.yyy.zzz, [www.xxx.yyy.zzz] must appear in control/locals and control/rcpthosts. - Original Message - From: "Roman Volf-RealShell Admin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: 01 February 2000, Tuesday 23:56 Subject: RE: Sending to an IP address | Get rid of the brackets. | | | | | Roman Volf | [EMAIL PROTECTED] | Realshell Internet Services | http://www.realshell.com | "We are all unique, just like everyone else" | | On Wed, 2 Feb 2000, Wilson Fletcher wrote: | | > Well if you try mailing to it you will see. It is returned by the smtp | > server I use to send email which incidentally is also qmail. Here is the | > bounce message: | > | > Hi. This is the qmail-send program at gidora.zeta.org.au. | > I'm afraid I wasn't able to deliver your message to the following | > addresses. | > This is a permanent error; I've given up. Sorry it didn't work out. | > | > : | > 203.26.11.154 does not like recipient. | > Remote host said: 553 sorry, that domain isn't in my list of allowed | > rcpthosts (#5.7.1) | > Giving up. | > | > --- Below this line is a copy of the message. | > | > Return-Path: <[EMAIL PROTECTED]> | > Received: (qmail 27215 invoked from network); 2 Feb 2000 04:36:16 - | > Received: from gw.mclachlan.com.au (HELO wraith.mclachlan.com.au) | > (203.26.11.145) | > by gidora.zeta.org.au with SMTP; 2 Feb 2000 04:36:16 - | > Received: by localhost with Microsoft MAPI; Wed, 2 Feb 2000 15:34:45 +1100 | > Message-ID: <[EMAIL PROTECTED]> | > From: Wilson Fletcher <[EMAIL PROTECTED]> | > Reply-To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> | > To: "'wilson@[203.26.11.154]'" | > Subject: Test | > Date: Wed, 2 Feb 2000 15:34:44 +1100 | > X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 | > MIME-Version: 1.0 | > Content-Type: text/plain; charset="us-ascii" | > Content-Transfer-Encoding: 7bit | > | > Test | > | > | > | > -- | > From: Chris Johnson[SMTP:[EMAIL PROTECTED]] | > Sent: Wednesday, 2 February 2000 15:32 | > To: [EMAIL PROTECTED] | > Cc: '[EMAIL PROTECTED]' | > Subject: Re: Sending to an IP address | > | > On Wed, Feb 02, 2000 at 03:25:58PM +1100, Wilson Fletcher wrote: | > > I tried to send to wilson@[203.26.11.154] but it failed. Can someone tell | > me | > > why ? | > | > I doubt it, unless you provide a detail or two. In what way did it fail? | > | > Chris | > | > | |
RE: Sending to an IP address
Get rid of the brackets. Roman Volf [EMAIL PROTECTED] Realshell Internet Services http://www.realshell.com "We are all unique, just like everyone else" On Wed, 2 Feb 2000, Wilson Fletcher wrote: > Well if you try mailing to it you will see. It is returned by the smtp > server I use to send email which incidentally is also qmail. Here is the > bounce message: > > Hi. This is the qmail-send program at gidora.zeta.org.au. > I'm afraid I wasn't able to deliver your message to the following > addresses. > This is a permanent error; I've given up. Sorry it didn't work out. > > : > 203.26.11.154 does not like recipient. > Remote host said: 553 sorry, that domain isn't in my list of allowed > rcpthosts (#5.7.1) > Giving up. > > --- Below this line is a copy of the message. > > Return-Path: <[EMAIL PROTECTED]> > Received: (qmail 27215 invoked from network); 2 Feb 2000 04:36:16 - > Received: from gw.mclachlan.com.au (HELO wraith.mclachlan.com.au) > (203.26.11.145) > by gidora.zeta.org.au with SMTP; 2 Feb 2000 04:36:16 - > Received: by localhost with Microsoft MAPI; Wed, 2 Feb 2000 15:34:45 +1100 > Message-ID: <[EMAIL PROTECTED]> > From: Wilson Fletcher <[EMAIL PROTECTED]> > Reply-To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > To: "'wilson@[203.26.11.154]'" > Subject: Test > Date: Wed, 2 Feb 2000 15:34:44 +1100 > X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 > MIME-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > > Test > > > > -- > From: Chris Johnson[SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, 2 February 2000 15:32 > To: [EMAIL PROTECTED] > Cc: '[EMAIL PROTECTED]' > Subject: Re: Sending to an IP address > > On Wed, Feb 02, 2000 at 03:25:58PM +1100, Wilson Fletcher wrote: > > I tried to send to wilson@[203.26.11.154] but it failed. Can someone tell > me > > why ? > > I doubt it, unless you provide a detail or two. In what way did it fail? > > Chris > >
