Help decoding a bounce msg
hi, I would like to ask more experienced mail admins around here to help me check this bounce msg. My main concern is that I am not sure whether it is my customer (signoplast.com.ar) who's infected. It's not clear to me if (66.60.1.118) is the originator of the msg or the originator of the bounce. Could anyone be so kind as to give me some hints on how should I read this? Thanks! Martin Original Message Subject: failure notice Date: 12 Jan 2001 07:35:19 - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Hi. This is the qmail-send program at scim.com.ar. I tried to deliver a bounce message to this address, but the bounce bounced! [EMAIL PROTECTED]: vdeliver: Invalid or unknown virtual user '3Dsp' --- Below this line is the original bounce. Return-Path: Received: (qmail 15136 invoked from network); 12 Jan 2001 07:35:09 - Received: from h066060001118.isol.net.ar (HELO recepci-n) (66.60.1.118) by scim.com.ar with SMTP; 12 Jan 2001 07:35:09 - From: Hahaha [EMAIL PROTECTED] Subject: Enanito si, pero con que pedazo! MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="--VE2R8D6NKTI7GH67WDMJ89U3WT"
Re: svscan
Thomas, I'm finding theexact same problem here. I guess you are installing from Bruce's RPM packages ... well it seems that there is some kind of version mismatch between the packages. I couldn't solve it yet. I'd say you should check which are the recommended verisons of the daemontools package and the supervise-scripts package... that's the path I'm following. martin Thomas Holton wrote: Dec 2 .. init: Id "SV" respawning too fast: disabled for 5 minutes
Re: svscan
Thomas, I am guessing it's an issue with supervise scripts. Thy've gone from 2.x to 3.x and there things stopped working for me. The problem is that I haven't been able to replace 3.1 with 2.4 in a clean way. martin Thomas Holton wrote: still no clue here so i suppose i should go back and try installing again. -tom
[OT] do you know this MTA(not qmail) error msg?
hi, sorry for being OT. I need help to diagnose an errormsg I'm receiving from a remote MTA -- mainly to show it's the other admin who's in fault. Or else repair my error and be humble about it :). To make matters worse, the errormsg is unknown to me: seems to be coming from a box I think is running WinNT. The full msg is at the end of this email. The relevant lines seem to be: - - Transcript of session follows - 451 [EMAIL PROTECTED]... reply: read error from mail1.dacas.com.ar. 553 mail2.dacas.com.ar. config error: mail loops back to me (MX problem?) 554 [EMAIL PROTECTED]... Local configuration error --AAA30448.976851513/ns2.dacas.com.ar Content-Type: message/delivery-status Reporting-MTA: dns; ns2.dacas.com.ar Received-From-MTA: DNS; mail.netizen.com.ar Arrival-Date: Fri, 15 Dec 2000 00:38:30 -0300 Final-Recipient: RFC822; [EMAIL PROTECTED] Action: failed Status: 5.5.0 Remote-MTA: DNS; mail2.dacas.com.ar Last-Attempt-Date: Fri, 15 Dec 2000 00:38:33 -0300 - now I did an nslookup and got: reino.com.arpreference = 5, mail exchanger = mail1.dacas.com.ar reino.com.arpreference = 10, mail exchanger = mail2.dacas.com.ar It certainly seems I'm on the safe side. But I wanted to check with more experienced admins, specially because I've never seen such msg. The bounced msg looks like: Return-Path: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: (qmail 21300 invoked from network); 15 Dec 2000 11:39:31 - Received: from unknown (HELO localhost) ([EMAIL PROTECTED]) by 10.10.10.10 with SMTP; 15 Dec 2000 11:39:31 - Delivered-To: [EMAIL PROTECTED] Received: from ns.scim.net by localhost with POP3 (fetchmail-5.5.1) for [EMAIL PROTECTED] (single-drop); Fri, 15 Dec 2000 08:39:31 -0300 (ART) Received: (qmail 5343 invoked from network); 15 Dec 2000 03:28:46 - Received: from mail.dacas.com.ar (HELO bbs.dacas.com.ar) (200.43.156.10) by scim.com.ar with SMTP; 15 Dec 2000 03:28:46 - X-ROUTED: Fri, 15 Dec 2000 00:28:14 -0300 Received: from [200.43.156.7] by bbs.dacas.com.ar with smtp id 004527d8 ; Fri, 15 Dec 2000 00:27:38 -0300 Received: from localhost (localhost) by ns2.dacas.com.ar (8.9.3/8.8.7) with internal id AAA30448; Fri, 15 Dec 2000 00:38:33 -0300 Date: Fri, 15 Dec 2000 00:38:33 -0300 From: Mail Delivery Subsystem [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="AAA30448.976851513/ns2.dacas.com.ar" Subject: Returned mail: Local configuration error Auto-Submitted: auto-generated (failure) This is a MIME-encapsulated message --AAA30448.976851513/ns2.dacas.com.ar The original message was received at Fri, 15 Dec 2000 00:38:30 -0300 from [EMAIL PROTECTED] [200.16.153.4] - The following addresses had permanent fatal errors - [EMAIL PROTECTED] - Transcript of session follows - 451 [EMAIL PROTECTED]... reply: read error from mail1.dacas.com.ar. 553 mail2.dacas.com.ar. config error: mail loops back to me (MX problem?) 554 [EMAIL PROTECTED]... Local configuration error --AAA30448.976851513/ns2.dacas.com.ar Content-Type: message/delivery-status Reporting-MTA: dns; ns2.dacas.com.ar Received-From-MTA: DNS; mail.netizen.com.ar Arrival-Date: Fri, 15 Dec 2000 00:38:30 -0300 Final-Recipient: RFC822; [EMAIL PROTECTED] Action: failed Status: 5.5.0 Remote-MTA: DNS; mail2.dacas.com.ar Last-Attempt-Date: Fri, 15 Dec 2000 00:38:33 -0300 --AAA30448.976851513/ns2.dacas.com.ar Content-Type: message/rfc822 Return-Path: [EMAIL PROTECTED] Received: from mail.netizen.com.ar ([EMAIL PROTECTED] [200.16.153.4]) by ns2.dacas.com.ar (8.9.3/8.8.7) with ESMTP id AAA30446 for [EMAIL PROTECTED]; Fri, 15 Dec 2000 00:38:30 -0300 From: [EMAIL PROTECTED] Received: from www (scim.com.ar [200.16.153.141]) by mail.netizen.com.ar (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id AAA32103; Fri, 15 Dec 2000 00:17:32 -0300 Date: Fri, 15 Dec 2000 00:17:32 -0300 Message-Id: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Consulta empresarial explicacion: Esta es una consulta de una empresa al sitio web de Reino S.A. nombre y apellido: KRONUS PRODUCCIONES direccion: PRODUCCION TELEVISIVA Y PUBLICITARIA localidad: Capital Federal cp: 1045 ciudad: BS. AS. provincia: BS. AS. pais: Argentina telefono particular: 4953-3692 e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] consultas: DESEARIAMOS PONERNOS EN CONTACTO CON LA EMPRESA PARA OFRECERLES UNA PROPUESTA PUBLICITARIA EN UN PROGRAMA DE TV DE YOGA Y SALUD. SALUDOS CORDIALES Submit: Enviar --AAA30448.976851513/ns2.dacas.com.ar--
Outlook Express Prank
boys and girls, this is not reasonable. Please do be kind with your fellow admins even if they do things you wouldn't do. Dropping a bomb such as that, *knowingly* is very unfriendly. No one deserves being crashed by a prankster, and nobody is expecting such uncivil behaviour in a technical list. Please do you some responsibility towards this tiny community. Thanks. martin
Re: Outlook Express Prank
Alex, this is not a call for censorchip, please! We are on a public list! I'm asking for a bit of professionalism. Whoever posted that practical joke was doing it on purpose -- and that's not professional at all. Professionals know that it takes a lot of work to build, and very little to destroy. Pranksters usually enjoy the power of destruction they gain with a little knowledge. Of course you can be a prankster. Just not here, please. There are people working, who that rely on this list for discussion and for help when their mail servers act up. They don't enjoy being the victims of a prank, whoever clever it might be. I'm asking people not to attack other people's programs just because we know how to. We should not be script kiddies, y'know. martin Alex Pennace wrote: No one deserves to be censored because some people made a poor choice for their MUA.
Re: Outlook Express Prank
Felix von Leitner wrote: Doesn't it seem a little idiotic to use Outlook on a mailing list about an Unix MTA? We are on the *internet*. Welcome. Many people, many machines, lots of strange company policies, personal choices and other constraints. Please refrain from making assumptions on how somebody else's machine/software should be run, because we are not here to judge. We're here to share. And, of course, you can criticize my MTA and its setup. And even my MUA. But please, people, it's not funny to kill it! The way *anyone* runs his/her boxes is not the *right* way. Is just his/her way. We're discussing qmail, and I'm asking people not to post things that will make some software blow up. I don't know who's to blame, but please, lets be good netizens. martin
Re: Outlook Express Prank
Felix von Leitner wrote: What in the seven hells are you talking about? Who did what prank that caused Outlook to barf and die? And if that happened as you insinuate above, why would you blame him and not Outlook? Felix, please, inform yourself and you'll save time. A few hours ago some jokester ( Chris Johnson [EMAIL PROTECTED] ) sent a msg that read If you want to have fun with Outlook Express users, put this in your signature: [EMAIL PROTECTED] [EMAIL PROTECTED] [replace QUOTE with " ... I didn't know if were using a susceptible MUA] which is a valid address as per RFC822 -- and a recipe for OE lockup. A few OE users on this list were hit. Chis knew what he was doing, and I'd bet he did it for fun. Now, however crappy OE may be, locking people's machines for fun is not a behaviour to be encouraged. martin
Re: how to set the rights for maildir to be secure
Dave, this thread got me wondering, and, as I suspected, my machines are usually configured with home at 0755 (world can read/execute, only owner -root- can write), so only root can add/delete users. [these machines are RH Linux + Bastille, mostly] On the other hand, I wouldn't trust a system (much less a distro) that sets the users directories (/home/user) to world readable ... my machines have something like 0700 (owner can do whatever, the rest of the world cant even peek inside). Looking around, I've found that vmailmgr does indeed set the "users" directory to 0755 ... I guess it's doing it for a reason, but inner directories (/home/domain/users/myvirtualuser/) are secured tightly (0700), so I don't really know. Anyway, it does makes a point come through: a machine set up as a mail host with virtualdomains is probably 'hackable' with a local account -- specially regarding the privacy of emails sitting in the users maibox. It shouldn't be, of course, but I won't be betting my head on that one... martin pd: what distro are you using that sets users directories to 755? Dave Sill wrote: I'm not sure you're aware of how systems are actually configured. All the user directories on my systems are world readable/executable, and they're that way by default, not because I did something to make it that way.
[OT]Help trying to understand rfc822!
hi, I know it's a bit OT here, but given the collective knowledge on RFC822 that gathers here, I hope someone can help me a bit. Besides, its MTA related after all ;) I'm sending mail from a perl script and I have one var (or config setting) for the 'To:' field. This script uses Net::SMTP to deliver its load directly into a sendmail box. Now if I insert 2 addresses, like '[EMAIL PROTECTED], [EMAIL PROTECTED]', and there's a qmail at scim.net everything's allright. Now some hosts don't like this: I'm having problems because relay.sion.com rejects my 'To: [EMAIL PROTECTED] [EMAIL PROTECTED]'. I've tried it with qmail-inject, manually feeding it with a 'To: [EMAIL PROTECTED] [EMAIL PROTECTED]' and it doesn't bounce! Reading RFC822 (at http://www.cis.ohio-state.edu/htbin/rfc/rfc822.html) I can see the appendix A, in the item A.1.5., it looks like it should be valid. In fact at A.3.3. there's an example that looks very much like mine... I'll find a workaround in the meantime, but, am I wrong to think its allright to have a comma-delimited To: field? martin
command confirmation interface [à la ezmlml]
hi, I'm starting to be fond of the easy path qmail gives me to turn email addresses into commands. Now, besides my nicey development box, some of these commands could be useful for my users, but I'd like to implement a 'confim source of command' feature like ezmlm has. Just before commmiting myself to writing such a mechanism, I'd like to know if someone's already has written one. The commands I'm thinking about are not sensitive (it wouldn't be *that* bad if someone fools the mechanism). I understand that the security this mechanism provides is feeble against a knowledgeable and determined hacker. Most users, though, will be deterred. That's my aim. I'm developing with Perl mostly, so if it's done in Perl, the better. Well, if I knew something of C, I'd rip it off EZMLM -- mmhh. Could I do that? Should read the licence ... [EMAIL PROTECTED]
does qmail support dots in user names?
hi, if I have a user called "user.com", can I tell qmail to use it as a recipient for a virtualdomain? Like in virtualdomains: --- user.com:user.com --- I have tried doing this and qmail cannot find the user at all. Mails to [EMAIL PROTECTED] got bounced with a "Sorry, no mailbox here by that name. (#5.1.1)". Checking the maillog, I can see that qmail-send does translate [EMAIL PROTECTED] into [EMAIL PROTECTED], so the virtdomain rules are being applied ok. Now when it comes the time to actually find the domain.com user, it fails. I've also tested sending mails to domain.com@localhost and they failed with a (#5.1.1) error. So my conclusion is that qmail does not behave properly with dotted user names. Is this documented somewhere? Or am I doing something wrong? martin
mail to virtuser@virtdomain.com : Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
hi, I've just set up a vdomain (using qmail + vmailmgr) and certainly I've forgotten something. Can you check my checklist (!) and tell me what am I missing? [warning: I did edit the logs/control files I'm reporting to avoid unneeded clutter, if you think there might be a mistake in any relevant file, tell me and I'll promptly post it] - The MX is properly setup on the machine's BIND (you won't be able to test it though). - The user is "signoplastcomar". I ran vsetup at is home, and indeed it contains .qmail-default (with a pipe to vdeliver) and users.cdb and users directory. Running listvdomain there shows the configured v-users. Additionally, all the files seem to be properly owned and secured. - rcpthosts contains 'signoplast.com.ar' and virtualdomains contains 'signoplast.com.ar:signoplastcomar' - qmail-send was sent a HUP signal. As things werent working, all of qmail and related daemons were restarted. Now, when at the command line I test with `mail [EMAIL PROTECTED]`, the logs say: (...) Oct 11 09:03:45 www qmail: 971265825.432508 starting delivery 361: msg 103476 to local [EMAIL PROTECTED] (...) Oct 11 09:03:45 www qmail: 971265825.470246 delivery 361: failure: Sorry,_no_mai lbox_here_by_that_name._(#5.1.1)/ (...) See? it *is* considering rcpthosts and virtualdomains allright, but can't find a user that is right there, and I'm not sure of where to look now ... lastly, qmail-showctl says: qmail home directory: /var/qmail. user-ext delimiter: -. paternalism (in decimal): 2. silent concurrency limit: 509. subdirectory split: 23. user ids: 102, 103, 104, 0, 105, 106, 107, 108. group ids: 16, 11. aliasempty: Default delivery target contains: |preline procmail Default delivery target contains: /Maildir/ badmailfrom: (Default.) Any MAIL FROM is allowed. bindroutes: (Default.) No binding routes. bouncefrom: (Default.) Bounce user name is MAILER-DAEMON. bouncehost: (Default.) Bounce host name is www.scim.net. checkpassword: Password checking program is checkvpw. concurrencylocal: (Default.) Local concurrency is 10. concurrencypop3d: (Default.) POP-3 daemon concurrency is 20. concurrencyqmqpd: (Default.) QMQP daemon concurrency is 20. concurrencyqmtpd: (Default.) QMTP daemon concurrency is 20. concurrencyremote: (Default.) Remote concurrency is 20. concurrencysmtpd: (Default.) SMTP daemon concurrency is 20. concurrencyspop3d: (Default.) SSL POP-3 daemon concurrency is 20. databytes: (Default.) SMTP DATA limit is 0 bytes. defaultdomain: Default domain name is scim.net. defaulthost: Default host name is scim.net. doublebouncehost: (Default.) 2B recipient host: www.scim.net. doublebounceto: (Default.) 2B recipient user: postmaster. envnoathost: (Default.) Presumed domain name is www.scim.net. helohost: (Default.) SMTP client HELO host name is www.scim.net. idhost: (Default.) Message-ID host name is www.scim.net. localiphost: (Default.) Local IP address becomes www.scim.net. locals: Messages for localhost are delivered locally. Messages for localhost.localdomain are delivered locally. Messages for www.scim.net are delivered locally. logger: (Default.) Logging is done via: splogger. me: My name is www.scim.net. percenthack: (Default.) The percent hack is not allowed. plusdomain: (Default.) Plus domain name is www.scim.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 localhost. SMTP clients may send messages to recipients at localhost.localdomain. SMTP clients may send messages to recipients at www.scim.net. SMTP clients may send messages to recipients at scim.net. SMTP clients may send messages to recipients at scim.com.ar. SMTP clients may send messages to recipients at langhoff.com.ar. SMTP clients may send messages to recipients at boherdi.com.ar. SMTP clients may send messages to recipients at posadapajaros-spa.com. SMTP clients may send messages to recipients at posadaspa.com. SMTP clients may send messages to recipients at posadaspahotel.com. SMTP clients may send messages to recipients at spahotel.net. SMTP clients may send messages to recipients at posadaspahotel.com.ar. SMTP clients may send messages to recipients at posadaspa.com.ar. SMTP clients may send messages to recipients at spahotel.com.ar. SMTP clients may send messages to recipients at posadapajaros.com.ar. SMTP clients may send messages to recipients at banys.com.ar. SMTP clients may send messages to recipients at banis.com.ar. SMTP clients may send messages to recipients at voluntariosenlared.com. SMTP clients may send messages to recipients at voluntariosenred.com. SMTP clients may send messages to recipients at intermujer.com. SMTP clients may send messages to recipients at intermujer.net. SMTP clients may send messages to recipients at rmb.com.ar. SMTP clients may send messages to recipients at e-transurban.com. SMTP clients may send
Re: mail to virtuser@virtdomain.com : Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
on to part II: I though there was something fishy with the user, so - removed the user I was using (signoplastcomar) - # /usr/sbin/useradd signo - # su signo - $ cd - $ vsetup - $ vadduser test - $ exit - # vi /var/qmail/control/virtualdomains changed the line related to signoplast to read ... signoplast.com.ar:signo ... "/etc/qmail/control/virtualdomains" 26L, 608C written - # ps ax | grep send 18465 ?S 0:03 qmail-send 19882 pts/1R 0:00 grep send - # kill -HUP 18465 - # mail [EMAIL PROTECTED] Subject: test 01 dd Cc: - # grep 'test@signoplast' /var/log/maillog Oct 11 10:19:37 www qmail: 971270377.250487 starting delivery 467: msg 103457 to local [EMAIL PROTECTED] - # grep 'delivery 467' /var/log/maillog Oct 11 10:19:37 www qmail: 971270377.250487 starting delivery 467: msg 103457 to local [EMAIL PROTECTED] Oct 11 10:19:37 www qmail: 971270377.288180 delivery 467: failure: Sorry,_no_mai lbox_here_by_that_name._(#5.1.1)/ h!? What am I missing??? can *anyone* tell anything? martin
*very* strange problems with virtualdomains
hi, this is a repost of a previos problem, which you can find under the subject "mail to [EMAIL PROTECTED] : Sorry,_no_mailbox_here_by_that_name._(#5.1.1)". Basically, sending mail to users in a new virtual domain returned error #5.1.1. Directory permissions are set just fine, and the new user/vdomain has no differencies with other users/domains I have set up. Guided by Petr Novotny [EMAIL PROTECTED] I've included the like `| set environment` as the first line of the .qmail-default file, and found qmail never gets there. The 5.1.1 error gets triggered earlier... a brief rehash of my setup: - [warning: I did edit the logs/control files I'm reporting to avoid unneeded clutter, if you think there might be a mistake in any relevant file, tell me and I'll promptly post it] - The MX is properly setup on the machine's BIND (you won't be able to test it though -- its an internal machine now). - The user is "signoplastcomar". I ran vsetup at is home, and indeed it contains .qmail-default (with a pipe to vdeliver) and users.cdb and users directory. Running listvdomain there shows the configured v-users. Additionally, all the files seem to be properly owned and secured. - rcpthosts contains 'signoplast.com.ar' and virtualdomains contains 'signoplast.com.ar:signoplastcomar' - qmail-send was sent a HUP signal. As things weren't working, all of qmail and related daemons were restarted. Now, when at the command line I test with `mail [EMAIL PROTECTED]`, the logs say: (...) Oct 11 09:03:45 www qmail: 971265825.432508 starting delivery 361: msg 103476 to local [EMAIL PROTECTED] (...) Oct 11 09:03:45 www qmail: 971265825.470246 delivery 361: failure: Sorry,_no_mai lbox_here_by_that_name._(#5.1.1)/ (...) See? it *is* considering rcpthosts and virtualdomains allright, but can't find a user that is right there, and I'm not sure of where to look now ... lastly, qmail-showctl says: qmail home directory: /var/qmail. user-ext delimiter: -. paternalism (in decimal): 2. silent concurrency limit: 509. subdirectory split: 23. user ids: 102, 103, 104, 0, 105, 106, 107, 108. group ids: 16, 11. aliasempty: Default delivery target contains: |preline procmail Default delivery target contains: /Maildir/ badmailfrom: (Default.) Any MAIL FROM is allowed. bindroutes: (Default.) No binding routes. bouncefrom: (Default.) Bounce user name is MAILER-DAEMON. bouncehost: (Default.) Bounce host name is www.scim.net. checkpassword: Password checking program is checkvpw. concurrencylocal: (Default.) Local concurrency is 10. concurrencypop3d: (Default.) POP-3 daemon concurrency is 20. concurrencyqmqpd: (Default.) QMQP daemon concurrency is 20. concurrencyqmtpd: (Default.) QMTP daemon concurrency is 20. concurrencyremote: (Default.) Remote concurrency is 20. concurrencysmtpd: (Default.) SMTP daemon concurrency is 20. concurrencyspop3d: (Default.) SSL POP-3 daemon concurrency is 20. databytes: (Default.) SMTP DATA limit is 0 bytes. defaultdomain: Default domain name is scim.net. defaulthost: Default host name is scim.net. doublebouncehost: (Default.) 2B recipient host: www.scim.net. doublebounceto: (Default.) 2B recipient user: postmaster. envnoathost: (Default.) Presumed domain name is www.scim.net. helohost: (Default.) SMTP client HELO host name is www.scim.net. idhost: (Default.) Message-ID host name is www.scim.net. localiphost: (Default.) Local IP address becomes www.scim.net. locals: Messages for localhost are delivered locally. Messages for localhost.localdomain are delivered locally. Messages for www.scim.net are delivered locally. logger: (Default.) Logging is done via: splogger. me: My name is www.scim.net. percenthack: (Default.) The percent hack is not allowed. plusdomain: (Default.) Plus domain name is www.scim.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 localhost. SMTP clients may send messages to recipients at localhost.localdomain. SMTP clients may send messages to recipients at www.scim.net. SMTP clients may send messages to recipients at scim.net. SMTP clients may send messages to recipients at scim.com.ar. SMTP clients may send messages to recipients at langhoff.com.ar. SMTP clients may send messages to recipients at boherdi.com.ar. SMTP clients may send messages to recipients at posadapajaros-spa.com. SMTP clients may send messages to recipients at posadaspa.com. SMTP clients may send messages to recipients at posadaspahotel.com. SMTP clients may send messages to recipients at spahotel.net. SMTP clients may send messages to recipients at posadaspahotel.com.ar. SMTP clients may send messages to recipients at posadaspa.com.ar. SMTP clients may send messages to recipients at spahotel.com.ar. SMTP clients may send messages to recipients at posadapajaros.com.ar. SMTP clients may send messages to recipients at
replacing a working qmail box
hi, I'm about to replace a qmail box. I'm trying to plan a suitable strategy to replace the box in the least time, with the least hassles. A new box is ready, with the same software installed, except for sone security critical patches. A good deal of qmail related things are running there. See: Software: - qmail (as per qmail+patches v14 by Bruce Guenter) - svscan, supervise and friends of daemontools in general - vmailmgr - pop3d - ezmlm with idx - Courier-IMAP daemon Config/Data: - a few dozens of VDomains - 4 mailing lists managed by ezmlm - no users are (yet) using the IMAP services - The box doesn't relay for anyone, (except for mailing lists, and these are announce lists that can afford to loose their queue) so I don't think I'll have problems waiting for the queue to empty. It's usually empty. Now, the strategy: a - Get the queue to empty (how do I keep qmtpd from being called from supervise) b - Check the old box UIDs for the users attached to each vdomain, and create users on the new box with the same login/UID. c - tar and copy the homedir of these users to the new box d - untar keeping ownerships and permissions e - will this transfer my ezmlm-idz mailing lists safely? I hope so! f - copy /var/qmail/control and /var/qmail/alias to the new box g - copy the dns setttings to the new box h - disconnect the old box, give the new box the old IP, `shutdown -r ` to see that it all comes up nicely. i - go home early for once in my debugging life! Besides i, do you find anything wrong/misplaced with this scenario? If it works, we could actually build an appendix to LWQ! martin
Re: html forms within messages
eric, greetings from BA! What you could do is trigger a *new* message. I don't think you can actually change the html msg that is already in the users INBOX. Anyway, as this certainly needs a connection and an HTML-aware mailer, why don't you put a link and open a new browser window? It'll be much more standard that counting on the MUA handling forms and redirects. martin Eric Dahnke wrote: we can send html formatted messages. can we send an html email which includes a form or link that when submitted would contact a web server and refresh the original html message with new cgi generated content? thx - eric
550 error with one particular v-domain using vmailmgr
hi, I have a *very* weird problem with only one of the many virtualdomains I am hosting with qmail+vmailmgr. The machine doesn't accept SMTP connections deliveries for v-users of e-transurban.com. The error qmail reports when rejecting *remote* messages is [from the bounced message] [EMAIL PROTECTED]: 200.16.153.4 does not like recipient. Remote host said: 550 [EMAIL PROTECTED]... User unknown Giving up on 200.16.153.4. I can read exactly the same in the maillogs on the server from which I'm testing. It seems that the receiving qmail smtp daemon doesn't log the failed connection attempt, nor its reason for rejecting the connection. Sending a mail locally to the very same virtual accounts, using `mail [EMAIL PROTECTED]` does work though. I have a .qmail-default for the v-domain looking like: --- [EMAIL PROTECTED] |/usr/local/bin/vdeliver --- and e-transurban.com is in both rcpthosts and virtualdomains. The DNS settings seem to be allright, and I can confirm I'm connecting to the right server (the IPs match). Other virtualdomains are working allright and the very same domain works fine locally. I've checked and re-checked the DNS, and doesn't seem to be there. The only suspect I still have is checkvpw ... may be it doesn't like dashes? Do you have a clue? ... i don't :[ martin
virtualdomains syntax [was Re: 550 error with one particular v-domain using vmailmgr]
hi, I am still in a knot with this issue, but I'm starting to think that for the 'e-transurban.com' domain I should have something different than: e-transurban.com:transurban to map to the 'transurban' user. Should the dash be encoded somehow? martin
[OT] Achieving Time-Synch at mailserver
hi, sorry for the OT-ness. I just hope other mail-admins in here may have had the same problem, and may be willing to share some hints with me. I have 2 mails servers that I want to synch (and keep with the world's clock). As one is in co-location, there's no problem at all: I'm installing NTPd (although I have some security concerns). The other machine has a intermittent connection, so I'm looking for a way to synchronize on a command (instead of a daemon). I checked CPAN for NTP and found nothing. The Net::Time module doesn't seem to help as it's looking for a time server, and not a NTP server. Am I too misguided? How are you guys keeping machines in synch? martin
Re: Semi-OT: Allowing only specific email clients.
If everything else fails, you can still get job at Microsoft! Kris Kelley wrote: I'm currently brainstorming ways that a mail server can be modified to work only with specific email clients.
Re: Web Interface for QMail [WING/acmemail]
hi I'm looking also for a web interface for qmail, and I'd like it to be programmed in perl for mod_perl. I'm now looking into WING, wondering if anyone has tried it with qmails virtual domains ? martin
[OT]Mail::* Perl modules to validate email address (RFC822)
hello, sorry for the OT, but I guess/hope the knowledge I'm looking for is not completely unrelated to this particular list, and I'm not aware of any Perl-email related mailing list. I'm trying to validate an email address as per RFC822, and, even though I've seen a lot of quick'n'dirty regexps to do so, I'd like to use actually RFC compliant code, known to work. Right now I'm perusing the Mail::* modules (docs and code), just grabbed from CPAN, looking for validating code, and finding none whatsoever. Has anyone experience with this modules? As far as I can see, they are too high-level for what I'm looking for. Or maybe I'm wrong? martin
Re: [OT]Mail::* Perl modules to validate email address (RFC822)
list, silly me. read the faqs first! perlfaq9 tells me I cannot validate emails in such a way, and points to a possible (but imperfect) approach by t.christiansen. off I go, to see if that's useable. sorry for everybody's time and bandwidth. martin pd: I did reply to myself so the (partial) answer gets to the archives and we all let this thread die.
Re: [OT]Mail::* Perl modules to validate email address (RFC822)
Magnus Bodin wrote: Doesn't Mail::RFC822 have validation code? I thought it did. No, but Mail::Address [1] or RFC::RFC822::Address [2] are you sure? I've been looking at Mail::Address and found nothing in its code that hinted of ay validation. It looked like an 'address book' mechanism, that built objects with a human-readable name and an address, and provided a few functions on that. Not much more, and certainly not any validation I could see. as per `perldoc perlfaq9` there's no realiable way to tell a functioning email address from a functioning diesel engine until you actually send it. martin
removimg a msg from the queue
hi list, a girl from accounting came crying she needed a particular email stopped from being delivered. as we don't have a permanent connection, I told her she was lucky and I did the following - skimmed the qmail-send, qmail-queue and qmail-remote manpages and found nothing - searched /var/qmail/queue and removed info/10/227894 mess/10/227894 remote/10/227894 and now I stand here and ask myself: did I do something terribly wrong? qmail-qread and qmail-qstat don't see the message, and apparently it hasn't been submitted. but maybe I did break something ... and, for the next time, is there a 'proper way' of performing the above mentioned deed cleanly? martin
qmail bouncing messages
hi list, it seems that my qmail setup is bouncing messages every once in a while. lists managed by ezmlm send me warnings such as : Messages to you from the vmailmgr mailing list seem to have been bouncing. I've attached a copy of the first bounce message I received. and the bounce looks like : Return-Path: Received: (qmail 432 invoked from network); 11 Jul 2000 15:18:53 - Received: from m36-ras4.netizen.com.ar (HELO localhost.localdomain) ([EMAIL PROTECTED]) by lists.em.ca with SMTP; 11 Jul 2000 15:18:53 - Received: (qmail 7888 invoked for bounce); 11 Jul 2000 15:13:33 - Date: 11 Jul 2000 15:13:33 - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: failure notice Hi. This is the qmail-send program at localhost.localdomain. 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, I couldn't find any host named localhost.localdomain. (#5.1.2) --- Below this line is a copy of the message. now i don't have the experience to know why once in a while doesn't recognize the virtual user [EMAIL PROTECTED] and wants to resolve localhost.locadomain. has anyone seen this? [hope the answers don't bounce too ;)] martin
routing a qmail setup
hello, first of all, sorry for the subject, I didn't know who to clearly explain what I'm trying to do in a line. My setup is simple: - I've got 2 qmail servers, one co-located and one internal to my company, with dial-up connection. - Both think they are *.scim.net MX - Upon dial-up connection, the internal server uses fetchmail to download mail for local users and I send an ALRM signal to qmail-send. the problem is here: qmail-send sends the remote mail directly to the recipients MX, and those are somethimes flaky (hotmail accounts, specially), so it keeps trying for a long time until the mail is sent or the delay is so long the the connection times out and disconnects. [ important point here, the dial-up connection (through pppd) is set to hangup when it reached a certain time of inactivity ] what I want it to do is: - route all the 'remote' mail to the online server. - the remote server should RELAY those mail, but ... only from me (don't really want to be an open relay). But hey! I'm on a dial-up acc - dynamic ip ... I really think it *should* be possible to 'route' all my traffic through the co-located server, but can I keep it from being an open relay? thanks in advance, specially if you read this long, long posting! martin [just getting in terms with qmail]
Re: routing a qmail setup
greg, the 'internal' part of the solution works great, thanks! Regarding the 'external' part of the solution ... you wrote external.scim.net must allow selective relaying; if you're using tcpserver, then add the IP address of internal.scim.net followed by ':allow,RELAYCLIENT=""' into /etc/tcp.smtp and type 'tcprules /etc/tcp.smtp.cdb /tmp/tcp.tmp /etc/tcp.smtp' but I have a dynamic IP address! [because of the dial-up connection]. is there a reasonable way to authenticate my server with tcpserver? is there a suitable mailing list to ask about tcpserver? martin
Re: routing a qmail setup
Petr. true! of course they do know their own IPs! I had been thinking how could I seduce one of their sysadmins to hand their dial-up IPs, and how could I keep it sync'ed (they are growing fast). The answer was right there... Thanks!!! martin Petr Novotny wrote: (The proper way, usually, is to relay through your ISP's server; they know their dialup netblock IP.)
msglog@localhost ?
hi list, I've had to quickly recover from a full server crash, and, together with many things, I've had to re-contrsuct my qmail control files from scratch. I forgot to change 'me' and had many bounces from [EMAIL PROTECTED] and that prompted a question ... does qmail keep all sent msgs there? what is exaclty the purpouse of this msglog@x? martin
help with fetchmail/qmail interaction
hi, i've got server A online, running qmail with vmailmgr and user SCIMNET handling all the virtualdomain SCIM.NET I've got my intranet server, which runs in a similar fashion, and connects to the internet regularly and runs fetchmail. It has the same v-users configured under the SCIMNET user. I've been reading the docs on fetchmail (specially the man pages and the FAQ) and can't get the sample settings for qmail to work. Under my scimnet user in my intranet server I've got a .fetchmail file that says (mostly) this: - defaults qvirtual "scimnet-" smtpaddress "scim.net" forcecr fetchtall keep # at least until it works! # and this one for a test-user poll mail.scim.net with protocol pop3 no dns envelope "Delivered To: user scimnet-test # for [EMAIL PROTECTED] password xx - I've read in the docs that its feasible to setup a .fetchmail file that will get the emails for all the possible v-users, but I can't really get not even 1 user to work! I really though that the qvirtual setting plus the smtpaddress setting would strip the scimnet- part from the username and append the resulting user to the server's address. Right now I'm lost, dazed and confused. Is there anyone that's got it working? Fetchmail is 5.4.0 by the way... martin
vmailmgr - listing users/aliases per domain,...
hi, i'm just starting to use qmail + vmailmgr to handle our customers mailboxen, and I'd like to know if there's a way to list the users/aliases in a given virtualdomain. surely must be there, but couldn't find it. martin
secure strategy to add v-users from cgi
hi list, I'm looking for a safe way to add users to a webmail service set up on qmail + vmailmgr + courier-imap + twig (a php mailclient). The part missing is, you guessed, adding new users automagically. Now I'm straining my head to think of the safest solution to give inmmediate registration to new users. All of the webmail users are running on the same UID the best path I could think of is writing a cgi that takes the info, validates the username and pw to make sure no escaping/shell invocation gets through and then pass them as parameters to a suid perl script that changes to the proper user, goes to its ~ and invokes vadduser. do you see any trouble with this approach, besides the care I must take to take the results (success/failure) all the way back to the cgi? or maybe there is a well know and understood sanctioned way to do it? martin
Re: No logs / supervise/ok doesn't exist...
given to me by [EMAIL PROTECTED] : This appears to be a problem with the older versions of the qmail+patches RPM. To fix it, you need to stop and start svscan. -- Bruce Guenterhttp://em.ca/~bruceg/
Running Courier-IMAP 0.33
hi list, I'm trying to get courier-imap to run on 2 different servers to no avail. Whenever I try to run ` imapd.rc start ` I get a "bind: adress already in use" error ... I've been readin the man pages and found nothing, and I've also been looking at the /etc/services file, hoping I had something wrong there, but doesn't look broken. does anyone have courier-imap running allright with qmail/vmailmgr? can you tell me what could I be missing? thanks martin
No logs / supervise/ok doesn't exist...
It seems I'm havimg mostly the same problem that Goran Blazic described a few months ago in a thread called " No log?". In a nutshell, after installing qmail i've got no logging activity from anything Mail-related. But the thread died without a solution. I guess/hope that Goran was able to get his logging to work ... but he forgot to post how he did it, and the archives thoughtfully strip all emails in fear of spam :( is anyone out there with a solution? I guess it's related to supervise, as you may see: # /etc/rc.d/init.d/qmail restart Stopping qmail: qmail qmail/log (already down) done. Starting qmail: qmail/log (will be started later) qmail done. and then # /etc/rc.d/init.d/qmail status qmail: qmail: up (pid 5527) 37912 seconds qmail/log: unable to open supervise/ok: file does not exist thanks! martin
qmail/log (will be started later) qmail done
hi, I've just installed qmail in a new box and everytime qmail starts, it greets me with the following msg: # /etc/rc.d/init.d/qmail restart Stopping qmail: qmail qmail/log (already down) done. Starting qmail: qmail/log (will be started later) qmail done. and the same seems to happen with the other qmail modules: noone is logging. My current log-handler is Syslog (just because I didn't touch a thing from the standard qmail install), and Syslog seems to be running fine (other services log just fine). now I've spent 2 hours of my sunday trying to find how to get logging to run, even under Syslog, and I just couldn't find the way. Can anybody point me to any obvious mistake I may be making? martin
IMAP / POP conflicts
hi, i'm quite a newcomer to email administration, and I'm attempting to set up qmail to server both IMAP and POP clients. For POP i'm using the qmail's pop3d (ruinning just fine) , and I'm installing Courier to handle IMAP clients. Are there any problems in : a - having one vdomain handled with imap and other with pop [vdomain granularity] (I'm using one UID per vdomain). b - having one user with IMAP and another with POP, despite of the vdomain it belongs to. c - having users that sometimes connect with POP and sometimes with IMAP. My question is regarding to whether it'll mess up the users' mailboxes (and/or my server) or not. I'm not interested in setting up a POP-allowed-users list and IMAP-allowed-users list and bounce the users that tries the wrong protocol. Mainly my goal is to (a) continue serving my POP/dial-up customers and set up a Webmail front end that speaks IMAP. But I don't want to have a separate mailserver for IMAP. And if using both IMAP and POP on the same mailbox doesn't mess things up,. I'd like to allow my POP customers to be able to use the webmail interfase to read their mail (as long as they didn't download it!). hope at least one of my options is trouble free :) thanks in advance martin
