Re: [vchkpw] Multi domain bounce message handling
Le Samedi 18 Octobre 2003 02:50, Tom Collins a écrit : On Friday, October 17, 2003, at 05:27 PM, David Bristol wrote: This may not be the way to go about this, but have you verified that both domains are in the qmail/control/locals file? Don't put vpopmail domains in control/locals. You'll mess things up. There isn't a known solution to what was asked. Doublebounces go to the postmaster of the server. Bounce messages refer to the name of the physical server, and not the domain name. You might be able to modify qmail-send, but it would be very difficult to determine what hostname to use in the bounce message. What if there are multiple recipients that bounced? What if it's a message one of your user's is trying to send to a hotmail address? You don't want it to say that your server is hotmail.com. For debugging purposes, it's best to have the server use it's real name. You can adjust that by editing control/bouncehost and setting it to a single name. Yes, setting a bouncehost works. The snag is that the only sensible thing then must be to set bounchost to something neutral, like Mailserver. It cannot be set to domA or domB, as bounce messages from the other domain will then be utterly missleading. For the sake of argument, suppose that somebody wants to send mail to [EMAIL PROTECTED], but miss-spells the name and writes e.g. [EMAIL PROTECTED] He will receive a bounce message, but he will have no idea which message bounced, as there will no indication from where it come. So, his interlocateur Kvaksvik will be wondering why he hasn't received the message he is waiting for and thake his buisness elsewhere. Have I missunderstood something or is this really the state of affairs in 2003? Regards Sigmund.
Re: [vchkpw] Multi domain bounce message handling
Le Samedi 18 Octobre 2003 10:05, Sigmund Gudvangen a écrit : Le Samedi 18 Octobre 2003 02:50, Tom Collins a écrit : On Friday, October 17, 2003, at 05:27 PM, David Bristol wrote: For debugging purposes, it's best to have the server use it's real name. You can adjust that by editing control/bouncehost and setting it to a single name. Yes, setting a bouncehost works. The snag is that the only sensible thing then must be to set bounchost to something neutral, like Mailserver. It cannot be set to domA or domB, as bounce messages from the other domain will then be utterly missleading. For the sake of argument, suppose that somebody wants to send mail to [EMAIL PROTECTED], but miss-spells the name and writes e.g. [EMAIL PROTECTED] He will receive a bounce message, but he will have no idea which message bounced, as there will no indication from where it come. So, his interlocateur Kvaksvik will be wondering why he hasn't received the message he is waiting for and thake his buisness elsewhere. Have I missunderstood something or is this really the state of affairs in 2003? Yes, I think I did missunerstand it. The above scenario isn't true of cause, as the bounce message will say Hi. This is the qmail-send program at Mailserver. 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. [EMAIL PROTECTED] Sorry, no mailbox here by that name. vpopmail (#5.1.1) And then it isn't such a bad idea having the host name in the bounce message. Sorry, just a popmail newbie that hadn't had his coffe yet. Regards Sigmund.
[vchkpw] Multi domain bounce message handling
Hi, I am in the process of testing out a small qmail/vpopmail server, with two domains; domA.com and domB.com. I have set up one of the domains domA.com as the defult, i.e. /etc/qmail/defaultdomain contains domA.com. Booth domains work as intended for normal mail delivery, but if I send mail to e.g. a nonexisting user at either domain, the bounce message is always from domainA.com: Hi. This is the qmail-send program at domA.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. Moreover, the failure notices are allways sent to [EMAIL PROTECTED], never to [EMAIL PROTECTED] Is there a way to ensure that bounce messages arrive from the correct domain and that fairure messages reches the correct postmaster? Regards Sigmund.
Re: Re: [vchkpw] qmail/vpopmail: sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1.)
W.D. McKinney wrote: edit /etc/tcp.smtp and add 127.:allow,RELAYCLIENT= then issue 'qmailctl cdb' Then issue 'qmailctl stop' then '/home/vpopmail/bin/clearopensmtp' now issue 'qmailctl start' That got rid of the error message, but outgoing messages were still stuck in the qmail queue. After lots of searching it transpired that that eth0 was behaving unreliably, but only for outgoing trafic. My test-machine was an old 200 MHz Dell Optiplex. This is probably a Linus driver problem, as it ran Win 2000 without a hitch. Anyway, I installed everything on a new machine and now it worked stright away. By the way, I am still curious about the role of /home/vpopmail/etc/tcp.smtp. Try sending to remote users now and let us know. Im sending this message via the new qmail/vpopmail setup. Thanks for the help. Sigmund.
[vchkpw] qmail/vpopmail: sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1.)
Hi, I have just done a fresh install of qmail and vpopmail, on Mandrake 9.1, following Dave Sill, http://web.infoave.net/~dsill/lwq.html for the qmail installation. qmail is running fine; i.e. all four daemons are running and inst_check reports that all is well. I also managed to install vpopmail and add domains and users. Booth messages injected locally (using qmail-inject) and incomming messages via smtp (from KMail on another machine) duely arrive in the appropriate Maildir/new. However, when I attempt to send to an extern email-address (from KMail) qmail responds with the error message: sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1.). OK, the messaage is from qmail, but I think it is related to vpopmail, as I also have qmail (without vpopmail) running on another PC, and on with that machine I have no problems sending to external addresses. I installed vpopmail as follows: ./configure --enable-file-sync=y --enable-roaming-users=y make make install-strip and put 10.0.0.:allow,RELAYCLIENT 192.168.2.:allow,RELAYCLIENT into /etc/tcp.smtp and added 40 * * * * /home/vpopmail/bin/clearopensmtp 21 /dev/null to crontab. The last response to [vchkpw] smtp;553 sorry, sorry, that domain isn't allowed relay (#5.7.1) i.e http://www.mail-archive.com/[EMAIL PROTECTED]/msg14771.html suggest putting 127.:allow,RELAYCLIENT into /etc/tcp.smtp I have also tried that, but it didn't make any difference. Booth the above response and the vpopmail install instructions mention /etc/tcp.smtp, but I can find anything about /home/vpopmail/etc/tcp.smtp What's the latter for? Any ideas what's wrong? Regards Sigmund. In case it helps, here is the output from /var/qmail/bin/qmail-showctl: qmail home directory: /var/qmail. user-ext delimiter: -. paternalism (in decimal): 2. silent concurrency limit: 120. subdirectory split: 23. user ids: 502, 504, 505, 0, 506, 507, 508, 509. group ids: 502, 503. badmailfrom: (Default.) Any MAIL FROM is allowed. bouncefrom: (Default.) Bounce user name is MAILER-DAEMON. bouncehost: (Default.) Bounce host name is mydomain.net. concurrencylocal: (Default.) Local concurrency is 10. concurrencyremote: Remote concurrency is 20. databytes: (Default.) SMTP DATA limit is 0 bytes. defaultdomain: Default domain name is mydomain.net. defaulthost: (Default.) Default host name is mydomain.net. doublebouncehost: (Default.) 2B recipient host: mydomain.net. doublebounceto: (Default.) 2B recipient user: postmaster. envnoathost: (Default.) Presumed domain name is mydomain.net. helohost: (Default.) SMTP client HELO host name is mydomain.net. idhost: (Default.) Message-ID host name is mydomain.net. localiphost: (Default.) Local IP address becomes mydomain.net. locals: me: My name is mydomain.net. percenthack: (Default.) The percent hack is not allowed. plusdomain: Plus domain name is mydomain.net. qmqpservers: (Default.) No QMQP servers. queuelifetime: (Default.) Message lifetime in the queue is 604800 seconds. rcpthosts: SMTP clients may send messages to recipients at mydomain.net. SMTP clients may send messages to recipients at amotherdomain.net. morercpthosts: (Default.) No effect. morercpthosts.cdb: (Default.) No effect. smtpgreeting: (Default.) SMTP greeting: 220 mydomain.net. smtproutes: (Default.) No artificial SMTP routes. timeoutconnect: (Default.) SMTP client connection timeout is 60 seconds. timeoutremote: (Default.) SMTP client data timeout is 1200 seconds. timeoutsmtpd: (Default.) SMTP server data timeout is 1200 seconds. virtualdomains: Virtual domain: mydomain.net:mydomain.net Virtual domain: anotherdomain.net:anotherdomain.net concurrencyincoming: I have no idea what this file does. rcpthosts.lock: I have no idea what this file does. defaultdelivery: I have no idea what this file does. virtualdomains.lock: I have no idea what this file does.
