Re: Serialmail send problem
On Mon, Aug 06, 2001 at 02:09:33PM -0400, Dave Sill wrote: Hi Dave, I have followed your LWQ and my setup should be straight out of that on both boxes. Thanks for that and the several other times you have helped me over the past years. I have run qmail for the past 2 years using serial mail to get mail to my subdomain. When col7.metta.lk dial into metta.lk and send the mail it is going OK, but when the connection from metta.lk to the Internet is down then the mail is not going out of col7.metta.lk Oops, so you have a problem, after all. So why doesn't the mail leave col7? I STATED: When the metta.lk world network is down, then the problem is there. At other times there is not any problem. I will have to withdraw that statement: I manually shutdown eth0 on metta.lk and sent mail to the Internet from col7.metta.lk The result was what you said: metta.lk took the mail and queued it for later delivery. I would like metta.lk to first of all accept mail from col7.metta.lk and then for metta.lk to send the mail out to the Internet whenever possible. That's how things are designed to work. For now I cannot come up with any error and I shall have to dig a bit more and will try to come back later with some more details. For now, Thanks for your reply Mettavihari A saying of the Buddha from http://metta.lk/ Realizing this fact, let the virtuous and wise person swiftly clear the way that leads to Nibbana. Random Dhammapada Verse 289
Re: Serialmail send problem
[EMAIL PROTECTED] wrote: I have installed qmail and serialmail and everything is working. Cool. Thanks for letting us know. My setup is as follows metta.lk __ | | -to the InterNet. |__| | modem dial-up to my Internet box | | __ | | _ local LAN col7.metta.lk |__| | several modems for user dial in When col7.metta.lk dial into metta.lk and send the mail it is going OK, but when the connection from metta.lk to the Internet is down then the mail is not going out of col7.metta.lk Oops, so you have a problem, after all. So why doesn't the mail leave col7? I would like metta.lk to first of all accept mail from col7.metta.lk and then for metta.lk to send the mail out to the Internet whenever possible. That's how things are designed to work. -Dave
Serialmail send problem
Hi all, I have installed qmail and serialmail and everything is working. My setup is as follows metta.lk __ | | -to the InterNet. |__| | modem dial-up to my Internet box | | __ | | _ local LAN col7.metta.lk |__| | several modems for user dial in When col7.metta.lk dial into metta.lk and send the mail it is going OK, but when the connection from metta.lk to the Internet is down then the mail is not going out of col7.metta.lk I would like metta.lk to first of all accept mail from col7.metta.lk and then for metta.lk to send the mail out to the Internet whenever possible. This is a recurrent problem as the Internet connection often is down on Sat and then only come up again on Mon morning due to many reasons beyond my control Thanks in advance. Mettavihari A saying of the Buddha from http://metta.lk/ He, who speaks much is not the one well versed in the Law. He, who hears the Law and practices what he has learnt is the one who knows the Law. Random Dhammapada Verse 259
Re: Manually manipulating serialmail queues
There is a perfectly good list for serialmail. Subscribe by sending a mail to [EMAIL PROTECTED]. I did just a few hours ago. I received my confirmation request, replied to it... and I'm still waiting. I'll give it a few more hours. BTW, is there any place where the serialmail list is archived? Just so that I can, uh, search it looking for my question before posting... Serialmail isn't a daemon, something else starts it -- usually a script that pppd activates. You can solve those problems by adding some features to whatever starts serialmail. I know it isn't a daemon. In my customer's case, it's started by a cron job that calls it every 30 minutes using setlock. The complete line is something like: /usr/local/bin/setlock -nx ~alias/outmail/seriallock /usr/local/bin/maildirsmtp ~alias/outmail alias-outmail- [UPSTREAM MAIL SERVER'S IP] `hostname` So, with that in mind, what are the features that you mention above? :-) (I'm afraid that they will turn out to be write a shell script to grep the mails in the queue and touch those who come from $BIG_BOSS, but oh well...) Paulo Jan. DDnet.
Re: Manually manipulating serialmail queues
On Thu, Jul 19, 2001 at 05:22:17PM +0200, Paulo Jan wrote: [snip] So, with that in mind, what are the features that you mention above? :-) (I'm afraid that they will turn out to be write a shell script to grep the mails in the queue and touch those who come from $BIG_BOSS, but oh well...) That's the way to go! /bin/sh is your friend :) Jörgen
Manually manipulating serialmail queues
Hi all: I have a customer who is using serialmail to upload their mail through their dial-up connection to our mail server. They have two problems: 1) Sometimes the dialup line isn't fast enough, and mail piles up. They would like to manually move some messages so that serialmail sends them before others. How could I do this? I guess that touch-ing the files so that they have an earlier date would work, but it would be better if it was automated (messages from this and that user always get more priority). Also, there's the problem of what happens if serialmail is already running while they are doing this; would serialmail catch that change right away? (That is, after sending the current message, it would scan again the queue, find the message that has been touch-ed, and start with it inmediately). Would it do that, or does serialmail scan the queue only once (when it starts)? 2) Related to the above: sometimes there are messages that don't get sent; instead, they just sit in the queue while serialmail is happily processing other mails that arrived after them. I suppose that the cause might be that serialmail timed out while trying to send them and just skipped them... but those mails aren't usually *that* big, just regular 3K, 10K, etc., messages. Is there any other cause for this? How could I force serialmail to send them? Paulo Jan. DDnet.
Serialmail algorithm? (leftover mails)
Hi all: I have a customer with a Linux server that connects to us through a dialup account, and sends us their queued mail using serialmail. The problem they are having is that, from time to time, they have some leftover mails that don't get sent, even if I kill all the running instances of serialmail and start it up by hand. The situation goes more or less like: 1) serialmail is started by a cron job, creates a lock on the outgoing mail directory using seriallock and starts sending the messages in the queue. 2) Before it has finished (the queue has several megabytes of messages), the cron job gets called again, but since the lockfile is... erm, locked, it doesn't do anything (or at least that's how I think it works...). 3) After several hours like this, you can see in the outgoing queue several old messages that, according to their timestamp, should have been sent by the first serialmail invocation, but haven't. You kill all the running instances of serialmail, start it by hand and... it starts sending mail NOT from the very beginning of the queue (i.e. those leftover messages), but from somewhere in the middle. My question is: what's going on? Or, to be more precise: -Does serialmail create a lock in the messages in the outgoing queue too, instead of just in the lock file? Does that (hypothetical) lock remain if I kill serialmail by hand? -Is my assumption in 2) correct? (That is, that the second invocation of serialmail doesn't do anything). The line I use in my crontab file is: /usr/local/bin/setlock -nx ~alias/outmail/seriallock /usr/local/bin/maildirsmtp ~alias/outmail alias-outmail- [IP of the upstream mail server] `hostname` Where ~alias/outmail is the Maildir where the outgoing messages get sent. -How does serialmail "choose" which mails in the Maildir to sent first? By filename? By timestamp? How? In case you are wondering, yes, the leftover mails do have envelope senders in the right format, that is, "Delivered-To: alias-outmail-user@domain". Anyone can help? Paulo Jan. DDnet.
serialmail Autoturn and qmail problem
hello friends i have installed serialmail package and trying to use it , but its not working i have followd all the steps specified in AUTOTURN file which comes with source code of serialmail i am running qmail with ldap, these are my configuration Details step by step 1) created a directory "autoturn' in /var/qmail/ then maildirmake 1.2.3.4 chown -R qmaild 1.2.3.4 echo ./1.2.3.4/ .qmail-1.2.3.4-default chmod 644 .qmail-1.2.3.4-default ( 1.2.3.4 = static ip address of my my client for whom i am trying to use this AUTOTURN) 2) changed the group of this newly created/var/qmail/autoturn directory to group "qmail" 3) chmod 2755 /var/qmail/autoturn 4) i have put the line "+autoturn-:qmaild:503:502:/var/qmail/autoturn:-:: where 503 is uid of qmaild 502 is uid of nofiles in /var/qmail/users/assign 5) the i have also run /var/qmail/bin/qmail-newu command sucessfully and it is creating the "cdb" file. 6) and replaced "qmail-smtpd" with following sh -c ' /var/qmail/bin/qmail-smtpd cd /var/qmail/autoturn exec setlock -nx $TCPREMPTEIP/seriallock \ /usr/local/bin/maildirsmtp $TCPREMOTEIP /var/qmail/autoturn/ -$TCPREMOTEIP -$TC PREMOTEIP AutoTURN ( Is this the correct script ,because i dont know much about this) 7) i have also defined specified this same qmail node in MX for that perticular domain for which i wants to use "AUTOTURN" featur 8)i have specified the same domain name in "rcpthosts" and "virtualdomains", control files. content of rcpthosts file diskonnet.com bogus.com content of virtualdomains bogus.com:autoturn-1.2.3.4 where 1.2.3.4 is the static ip which our customer is using my problem is , when i am trying to telnet on port 25 on the mechine running qmail with above config, it gives cant connect to service not available , now as soon as i have replaced "qmail-smtpd" in tcpserver call with the script which is given in the document for your reference i am again specifying the script sh -c ' /var/qmail/bin/qmail-smtpd cd /var/qmail/autoturn exec setlock -nx $TCPREMPTEIP/seriallock \ /usr/local/bin/maildirsmtp $TCPREMOTEIP /var/qmail/autoturn/ -$TCPREMOTEIP -$TC PREMOTEIP AutoTURN now if i just run this script then its giving me a smtp prompt which we usually get if we telnet to port "25". now when i will give "mail from: [EMAIL PROTECTED]" O.k. "rcpt to: [EMAIL PROTECTED]" o.k data go ahead now when i will type somedata and press return key its giving 451 See http://pobox.com/~djb/docs/smtplf.html. maildirserial: fatal: unable to scan $MAILDIR/new: file does not exist now please point me what i am doing something wrong , i dont know why , its giving me this error , bcoz i have created Maildir in /var/qmail/autoturn/1.2.3.4/Maildir i have also tried creating " Maildir" in /var/qmail/autoturn/Maildir i have tried it for 4-5 days, but unfortunately i am not able to solve it , thanks Regards Prashant Desai
Re: The problem with serialmail/qmail and dialup lines
Paulo Jan [EMAIL PROTECTED] wrote: I've been in this list, on and off, for about two years, and I have seen the issue discussed several times, but have never seen a solution for this particular case (customer on a dialup line, sending large mails to several people). Has anyone come up with a way to deal with this situation? The best workaround I'm aware of is to set up a list containing the recipients on the server. That won't help much if the list is dynamic. Or is this one of the cases where other MTAs could actually have done a better job? Yes, other MTA's could handle this more efficiently. -Dave
The problem with serialmail/qmail and dialup lines
Hi all: First of all, thanks to all those who responded to my question regarding "System crash". Time to upgrade the Linux kernel, I guess... I have now another problem, related this time with serialmail and the old topic of messages-addressed-to-several-users-sent-separately. I have recently installed AutoTURN for a customer that was using sendmail in their local Linux proxy/mail server until now, and whose connection to us is an ISDN dial-up line. Things are working OK so far... except that these customer's users need to send often large attachments (1-5 Mb.), each of them to several people. Given qmail's way of dealing with multi-recipient mails, this means that my customer's messages are taking longer to reach me. I am aware of the causes behind this design decision taken in qmail, and I know that this subject has been beaten to death in this list; what I haven't seen yet, though, is a solution to this particular case I'm talking about. I've been in this list, on and off, for about two years, and I have seen the issue discussed several times, but have never seen a solution for this particular case (customer on a dialup line, sending large mails to several people). Has anyone come up with a way to deal with this situation? Or is this one of the cases where other MTAs could actually have done a better job? Paulo Jan. DDnet.
serialmail
Since the serialmail list doesn't appear to have a lot of traffic, I wonder if anyone can point me in the direction of an archive. -- I'm Keyser Soze...No, I'm Keyser Soze. I'm Keyser Soze and so's my wife! (Monty Python play The Usual Suspects.)
Serialmail bounce messages
I am currently setting up a store and forward service on our existing Exim platform. A maildir and serialmail implementation seems to be the best solution and is working very well on our test platform. However, as I am constrained by an existing Exim platform I would like to send bounce messages from serialmail through Exim rather than qmail. Serialmail appears to inject bounce messages directly into the qmail queue in a rather complex manner. Can anyone explain to me the reasons for this complexity and why it shouldn't use a simple "public" MTA interface, ie simply call for example /usr/bin/sendmail? Has anyone written a patch for serialmail to allow it to use other MTAs? Also, is there any documentation other than the man pages for serialmail and qmail-queue as the code itself is not rich in comments? Thanks in advance Brian
serialmail
Hi, I'm using the serialmail package to let some people initiate an smtp connection to their server whenever they make a pop connection, so all mail gets delivered. Now I don't use an alias for this user, so I have to rewrite the headers all the time for this user so that the prefix "alias-" is put in fron of the first "Delivered-to" line. Now I want to know if anybody can make this serialmail package work without having to use the prefix option, or how I can rewrite a header in a .qmail file? With friendly regards, Franky
ETRN (not serialmail + pullmail)
Does anyone know ETRN+qmail ?
setlock-ing serialmail?
Hi all: Leaving aside Taylor UUCP and aliases for the moment... I have a customer with a dialup connection that has a Linux server with qmail/serialmail, and sends us their outgoing mail following the recipe in the TOISP file of the serialmail distribution. They have a cron job that executes maildirsmtp every 30 minutes to send the mail queue, etc., etc. The problem is that they often send very big files through mail (I know, I know...), so the queue gets very big and the following situation often arises: 1) maildirsmtp gets executed. The server starts sending out the 30 Mb. or so of messages. 2) After 30 minutes, the queue hasn't been sent completely yet, but another instance of maildirsmtp is started, and begins sending messages from the queue again. 3) After a few hours, one can find 10 or 11 instances of maildirsmtp running at the same time on the dialup line. My questions are: 1) Could I run setlock with maildirsmtp to prevent this situation? Say: /usr/local/bin/setlock -nx ~alias/pppdir/seriallock /usr/local/bin/maildirsmtp ~alias/outmail alias-outmail- (MY_MAIL_SERVER_IP) `hostname` I think there's nothing wrong with the above line, but I'd like to check with somebody else. 2) How does maildirsmtp "decide" which messages of the queue to send? If I understand serialmail's mechanism correctly, in the situation above described the second instance of maildirsmtp should start sending again the same messages than the first one, but from what I've seen it doesn't do so. Can maildirsmtp "know" which messages of the queue are "locked" by another instance of the program? The man pages don't say anything about this. 3) If there are new messages arriving to the queue while maildirsmtp is working, does it send them in the current batch, or they have to wait for the next time maildirsmtp is executed? Paulo Jan. DDnet.
Re: setlock-ing serialmail?
Paulo Jan [EMAIL PROTECTED] wrote on Thu, 18 May 2000: 1) maildirsmtp gets executed. The server starts sending out the 30 Mb. or so of messages. 2) After 30 minutes, the queue hasn't been sent completely yet, but another instance of maildirsmtp is started, and begins sending messages from the queue again. When I was using a similar setup, I had this code snippet as part of my "pppdeliver" script that invoked maildirsmtp: # Sanity check to avoid two copies running simultaneously if [ -e $PIDFILE ]; then # pppdeliver is already running OTHERPID=`cat $PIDFILE` logger -t pppdeliver -p mail.notice [$$] Already running at PID $OTHERPID exit 1 else echo $$ $PIDFILE fi It's not secure etc. etc. but it worked. :-) Also the script would of course rm $PIDFILE before exiting. Anyway, any other sort of locking mechanism should work just as well I imagine. Sorry, I don't know enough about maildirsmtp to answer your other questions. Regards, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / Change is inevitable, except from a vending machine.
Re: Working with SerialMail and Queue
Carlo Manuali [EMAIL PROTECTED] wrote: My problem was to manage the queue manually, to send E-Mail only at some hours (ex. 8 am and 5pm). Can someone help me to explain how can i have to use serialmail (or other way) to do this with the products that i have already installed? Install serialmail. In particular, you need maildirsmtp, which takes a mailbox in maildir format and sends the contents via smtp. Configure qmail to deliver all outgoing mail to a maildir mailbox by adding the following entry to control/virtualdomains: :alias-catchall and creating the associated .qmail file: echo ./outgoing/ ~alias/.qmail-catchall In whatever script you use to bring up your network connection, add a maildirsmtp invocation to send the mail queued in ~alias/outgoing. Or set up cron jobs at 8 AM and 5 PM to run maildirsmtp, if you know the connection will be up at those times. See the maildirsmtp man page for details on running it. -Dave
Working with SerialMail and Queue
Hi to all. Sorry if I already post a similar question, but i don't understand the best way that should I follow. I've installed qmail with vpopmail, qmailadmin and sqwebmail and I manage many domains and users very efficently via web. My problem was to manage the queue manually, to send E-Mail only at some hours (ex. 8 am and 5pm). You and others told me to try serialmail or work with switch, but unlikely i'm not very well (i'm newbies about administration...) and my ideas are very confused. Can someone help me to explain how can i have to use serialmail (or other way) to do this with the products that i have already installed? Whatever help is appreciated. Thanks for your patience, --Carlo Carlo Manuali Centro d'Ateneo per i Servizi Informatici (CASI) University of Perugia ITALY
Serialmail/Turnmail
Hi, I've just come across the turnmail on the qmail web site - it looks like exactly like what I need. I've compiled serialmail and installed it properly. I've tried quite a few things to get the script working but none of them seem to work. I'm starting pop3d at the moment with: /usr/bin/tcpserver 0 110 /usr/sbin/qmail-popup chef.praceng.co.uk /usr/bin/checkpassword /usr/sbin/qmail-pop3d Maildir I've copied the contents to /usr/sbin/turnmail and tried the following line but no luck: /usr/bin/tcpserver 0 110 /usr/sbin/qmail-popup chef.praceng.co.uk /usr/bin/checkpassword /usr/sbin/autoturn Any ideas or tips how to get this working as its really bugging me! I've copied the contents of the autoturn and pasted them below as I had to remove one ; for the script to work. #!/bin/sh if [ -d Maildirdummy ]; then /usr/bin/maildirsmtp $1 $USER- $TCPREMOTEIP `hostname` 21 | logger -p daemon.notice /usr/sbin/qmail-pop3d Maildirdummy fi exec /usr/sbin/qmail-pop3d $1 Can anyone help me or gives me some tips to getting it too work? Thanks, Chris
How to kick serialmail
Hi, I have qmail 1.03 installed and am using serialmail to provide ETRN like functionality. The problem is that I don't know what to send to the server to 'kick' it into sending all mail for the domain assiciated with the IP address I am SMTP'ing from. Can anyone tell me what is meant to be sent to the server. Cheers, Del.
Re: How to kick serialmail
Derek Smith [EMAIL PROTECTED] wrote: I have qmail 1.03 installed and am using serialmail to provide ETRN like functionality. What Dan calls AutoTURN? The problem is that I don't know what to send to the server to 'kick' it into sending all mail for the domain assiciated with the IP address I am SMTP'ing from. Can anyone tell me what is meant to be sent to the server. If you're doing AutoTURN, all you need to do is connect to port 25 on the server. -Dave
serialmail
Does serialmail require the dialup host to have a static IP? Thanks, Jose
Serialmail not removing lock files...
Hi all: Well, I've got at last serialmail and AutoTURN installed and working, following the instruciones in the serialmail package. The only problem that I have now is that, after triggering an AutoTURN delivery, maildirsmtp locks the proper directory, sends the messages in it correctly... but never unlocks the directory (that is, it doesn't delete the "seriallock" file that it creates). The line that I use to start serialmail in my startup scripts is: /usr/local/bin/tcpserver -c55 -v -x/etc/tcp.smtp.cdb -u 7791 -g 2108 0 smtp /etc/rc.d/rc.qmail-smtpd 21 |/usr/local/bin/accustamp | /usr/local/bin/setuser root /usr/local/bin/cyclog -n12 /var/log/qmail-receive And "rc.qmail-smtpd", in turn, has: /usr/local/qmail/bin/qmail-smtpd cd /usr/local/qmail/autoturn exec setlock -nx $TCPREMOTEIP/seriallock \ maildirsmtp $TCPREMOTEIP autoturn-$TCPREMOTEIP- $TCPREMOTEIP AutoTURN The AutoTURN instructions said to include this in the main qmail startup script with "sh -c '(script here)'", but I couldn't get it to work properly in any way (specially the part about redirecting errors to cyclog), so I'm putting them in a separate file. Looking at the setlock man pages, I see this: Normally the lock disappears when program exits. (Here's the complete story: program is given a descriptor for a locked ofile pointing to file. The lock disappears when this ofile is (1) closed by all the processes that have descriptors for it or (2) explicitly unlocked.) Which makes me think that maildirsmtp doesn't exit cleanly, but I can't find it with ps -auxw anywhere in my list of processes. Also, I don't know what an "ofile" is; I even asked our local Unix guru, who claims that he has never heard that word before (feel free to tell me if we need to depose him of his guru status). Any ideas? I'm using Slackware 3.2 (with a Linux 2.0.34 kernel) if that helps. If you need more information, just ask... Paulo Jan. DDnet.
Re: Serialmail not removing lock files...
On Fri, Nov 26, 1999 at 04:20:37PM +0100, Paulo Jan wrote: You've misunderstood the setlock manpage. After setlock's child exits, the lock on the seriallock file does indeed disappear, but the file is not removed. This makes sense, because it will have to be created again soon, so why waste resources removing it? If you want to test this, find a seriallock file for which the maildirserial process has completed, then try to lock it yourself: setlock -n /var/qmail/autoturn/1.2.3.4/seriallock echo ok If you get back an "ok", it means the file was not locked, implying that no maildirserial was running at that time. Otherwise, you'll get an error message from setlock saying it was unable to lock the file. Hi all: Well, I've got at last serialmail and AutoTURN installed and working, following the instruciones in the serialmail package. The only problem that I have now is that, after triggering an AutoTURN delivery, maildirsmtp locks the proper directory, sends the messages in it correctly... but never unlocks the directory (that is, it doesn't delete the "seriallock" file that it creates). The line that I use to start serialmail in my startup scripts is: [snip] -- Anand
Serialmail
Would somebody kindly point me to a one page set of instructions on how to use SerialMail? The INSTALL that comes with serialmail simply says: 1. make 2. make setup check Now what am I supposed to do with the 2 files it apparrently creates, ./install and ./instcheck? I can pretty much guess what they do, but I don't want to make any assumptions. The man pages are nice, but there is no 'guide', nothing that gives a general overview on what needs to be done to get a simple serialmail session going. Much appreciated, Jose
Re: Serialmail
Read the TOISP file. - Eric Jose de Leon escribió: Would somebody kindly point me to a one page set of instructions on how to use SerialMail? The INSTALL that comes with serialmail simply says: 1. make 2. make setup check Now what am I supposed to do with the 2 files it apparrently creates, ./install and ./instcheck? I can pretty much guess what they do, but I don't want to make any assumptions. The man pages are nice, but there is no 'guide', nothing that gives a general overview on what needs to be done to get a simple serialmail session going. Much appreciated, Jose
Serialmail and ETRN
I'm needing some ETRN capabilities and reading the archives hints that serialmail provides this functionality. Can someone confirm, deny or provide some details? Thanks. andy -- --- Andy WaldenWork Email: [EMAIL PROTECTED] Network Administrator, Pers Email: [EMAIL PROTECTED] MTCO CommunicationsPhone: (800) 859-6826 "A little nonsense now and then, is relished by the wisest men." -Willi Wonka
Re: Serialmail and ETRN
At 09:46 31/08/99 -0500, you wrote: I'm needing some ETRN capabilities and reading the archives hints that serialmail provides this functionality. Can someone confirm, deny or provide some details? Thanks. Serialmail allows your qmail smtp to connect to another SMTP and to give it all messages for a domain. With a script, even on a dialup connexion with dynamic IP. That's not really ETRN but's that's like it. The remote SMTP must be configured to receive messages that he is sent.
Re: Serialmail and ETRN
On Tue, 31 Aug 1999, Dimitri SZAJMAN wrote: At 09:46 31/08/99 -0500, you wrote: I'm needing some ETRN capabilities and reading the archives hints that serialmail provides this functionality. Can someone confirm, deny or provide some details? Thanks. Serialmail allows your qmail smtp to connect to another SMTP and to give it all messages for a domain. With a script, even on a dialup connexion with dynamic IP. That's not really ETRN but's that's like it. The remote SMTP must be configured to receive messages that he is sent. So would the remote system also need to use qmail/serialmail? Thanks, andy
Re: Serialmail and ETRN
At 09:55 31/08/99 -0500, Andy Walden wrote: Serialmail allows your qmail smtp to connect to another SMTP and to give it all messages for a domain. With a script, even on a dialup connexion with dynamic IP. That's not really ETRN but's that's like it. The remote SMTP must be configured to receive messages that he is sent. So would the remote system also need to use qmail/serialmail? The remote system can be any SMTP, under any OS, but must be configured to accept receiving mail for the domain you want ETRN-like.
Re: serialmail/autoTURN not working
Hi everyone, Can I take it that the lack of response to my strace output means that either nobody knows the answer or that anyone who does know the answer thinks I'm being stupid for not seeing it and not worth replying to? If the former then thanks anyway for trying to help, but I guess I'll have to go with another MTA. If the latter then thanks for nothing and I guess I'll be going with another MTA. Tom.
Re: serialmail/autoTURN not working
"Tom Furie" [EMAIL PROTECTED] wrote:
open("/dev/tty", O_RDWR|O_NONBLOCK) = -1 EACCES (Permission denied)
ioctl(0, TCGETS, 0xbaac)= -1 EINVAL (Invalid argument)
I must admit, I have no idea how to read this output. Why is it trying to
open /dev/tty?
Good question. Try adding a "/dev/null" to the maildirsmtp
invocation.
-Dave
Re: serialmail/autoTURN not working
Good question. Try adding a "/dev/null" to the maildirsmtp invocation. That would appear to have fixed the problem, but why should I have to feed something else to maildirsmtp before it does its job? Cheers, Tom
Re: serialmail/autoTURN not working
"Tom Furie" [EMAIL PROTECTED] wrote: Good question. Try adding a "/dev/null" to the maildirsmtp invocation. That would appear to have fixed the problem, but why should I have to feed something else to maildirsmtp before it does its job? You're not feeding it something else, you're telling it not to try to read from the tty. The question is: why does it think it's got access to a tty? I can't answer that. -Dave
serialmail
Hi all, I have installed AutoTURN and serial mail I have not quite understood the instructions in serial mail and I see different usages on this list mentioned by Dave and others Could you kindly indicate where I can get a lwq or HOWTO on serial mail. Thanks Jacob
Re: question on Serialmail and ETRN (fwd)
Hi! Anand Buddhdev has provided me very good answers on Serialmail and ETRN and I thought I should share it with others and also let the answers be archived by the mailing list. Thank you very much Anand Buddhdev! -- Forwarded message -- Date: Sat, 24 Jul 1999 11:02:18 +0300 From: Anand Buddhdev [EMAIL PROTECTED] To: Goh Sek Chye [EMAIL PROTECTED] Subject: Re: question on Serialmail and ETRN On Sat, Jul 24, 1999 at 12:01:29PM +0800, Goh Sek Chye wrote: Hi! Sorry to trouble you here. Hello Goh. No trouble at all. I read your posting below from the mailing list archive for qmail. I am getting very confused here and I need some enlightenment about qmail/serailmail. 1. qmail alone cannot support ETRN command. You must install serialmail to enable qmail to support ETRN command (True/False)? Sort of true and false. qmail on its own does not support ETRN, and probably never will. This is because qmail's author likes writing modular software, where each little program does one thing, and does it well. So to get funtionality similar to ETRN, you install serialmail, which can also help in other instances. For example, if you look on the qmail homepage, and look for "turnmail", you will see it is a use of serialmail without ETRN, but with POP instead. 2. I have a server (running sendmail) acting as a secondary mail server for all my ISDN customer with different domain. Currently, they are using ETRN to nudge sendmail to push any new mails for their doamin to their mail server (the MX record with higher priority for their domain) That's usually the standard way of doing it with sendmail. I want to use qmail/serialmail instead of sendmail. From your answer to the posting below, can I say that my customer do not need to change any thing (continue to use ETRN) if I migrate from sendmail to qmail/serialmail? Correct. As I have quite a number of my customer using Microsoft Exchange Server, can I also say that I should patch qmail as described in your posting below? qmail will work fine with MS Exchange. We have anumber of such customers here. However, I heard somebody had trouble with MS Exchange because it was looking for the 250-ETRN response to the EHLO command. Since qmail itself doesn't support ETRN, it doesn't advertise it in its response. I see no harm it patching qmail-smtpd with a few lines of code to advertise ETRN and return a "250 Ok" to an ETRN. Try using the system without patching first. If you have problems, then patch it as I described. 3. After reading through serialmail docs, am I right to say that serialmail will store mails for each different domain in their respective directories? Correct. The directory name will be the IP address of the customer. Does this mean that once my customer makes a smtp connection and issue ETRN, qmail will know exactly which directory the mails for the domain are stored and deliver it from there to the customer mail server(MX record with higher preference) ? Small correction here. With the qmail model, the issue of lower/higher MX records becomes irrelevant. With sendmail, you had: MX 10 customer MX 20 isp.mail.server This is because sendmail, when kicked with an ETRN, will still do MX processing as usual. With qmail, the serialmail package doesn't use MX records (since it's designed for serial links, not routed links). Therefore, your customer's domain will only have one MX record, like this: 10 MX isp.mail.server. All their mail will be stored in the maildir. When they connect, and either send an ETRN, *or* even just send email, serialmail will be triggered, and it will deliver the mail out of the customer's directory to their IP address. If this is true, I am really impressed. This is a very well designed piece of software (in contrast with sendmail which will have to go through all its queue to single out if there are any new mails for the domain in response to ETRN ) Very true. qmail and it's auxilliary packages, like serialmail, are impressive pieces of software. They're small, fast, modular, easy to use and understand, and best of all, free! -- See complete headers for more info
Re: serialmail/autoTURN not working
"Tom Furie" [EMAIL PROTECTED] wrote: qmail alone - passes deliver and receive tests fine. Add ucspi-tcp, run qmail-smtpd through tcpserver - still passes deliver and receive tests. Add serialmail, follow the instructions in AUTOTURN. Section 3 - if I use sh -c..., I cannot connect to port 25 on the mail server. Using csh -c, I can connect to port 25. Send mail to [EMAIL PROTECTED], message goes into /var/qmail/autoturn/customers.ip/new Run maildirsmtp command to process test.domain queue e.g. maildirsmtp 1.2.3.4 autoturn-1.2.3.4- 1.2.3.4 AutoTURN, mail is processed and arrives at ms.test.domain Send mail from test.domain using qmail.server as relay, mail arrives at destination, but delivery from qmail.server to ms.test.domain is not triggered. rc.local looks like - /usr/local/bin/tcpserver -v -u 503 -g 502 0 smtp csh -c ' /var/qmail/bin/qmail-smtpd cd /var/qmail/autoturn exec /usr/local/bin/setlock -nx $TCPREMOTEIP/seriallock \ /usr/local/bin/maildirsmtp $TCPREMOTEIP autoturn-$TCPREMOTEIP- $TCPREMOTEIP AutoTURN ' 21 | /var/qmail/bin/splogger smtpd 3 csh -cf '/var/qmail/rc ' I have tried /var/qmail/rc both before and after the tcpserver command with no apparent difference. Yeah, it doesn't matter. OK, so basically smtpd works when you connect to port 25, are queueing up in the maildir, the maildirsmtp command works when you run it manually, but it doesn't work automatically? Change your smtpd startup command to something like: /usr/local/bin/tcpserver -v -u 503 -g 502 0 smtp csh -c ' /var/qmail/bin/qmail-smtpd cd /var/qmail/autoturn echo = /tmp/autoturnlog date /tmp/autoturnlog env /tmp/autoturnlog echo "exec /usr/local/bin/setlock -nx $TCPREMOTEIP/seriallock \ /usr/local/bin/maildirsmtp $TCPREMOTEIP autoturn-$TCPREMOTEIP-$TCPREMOTEIP AutoTURN" /tmp/autoturnlog exec /usr/local/bin/setlock -nx $TCPREMOTEIP/seriallock \ /usr/local/bin/maildirsmtp $TCPREMOTEIP autoturn-$TCPREMOTEIP-$TCPREMOTEIP AutoTURN ' 21 | /var/qmail/bin/splogger smtpd 3 Then connect to port 25 from your client and look at /tmp/autoturnlog. Make sure the maildirsmtp command is exactly right. -Dave
Re: serialmail/autoTURN not working
no apparent difference. Yeah, it doesn't matter. Didn't think so. OK, so basically smtpd works when you connect to port 25, are queueing up in the maildir, the maildirsmtp command works when you run it manually, but it doesn't work automatically? Sounds about right. Change your smtpd startup command to something like: Then connect to port 25 from your client and look at /tmp/autoturnlog. Make sure the maildirsmtp command is exactly right. contents of autoturnlog entry - Thu Jul 22 16:55:52 GMT 1999 PWD=/var/qmail/autoturn HOSTNAME=post CONSOLE=/dev/console PREVLEVEL=N AUTOBOOT=YES runlevel=3 MACHTYPE=i386 SHLVL=3 previous=N BOOT_IMAGE=linux SHELL=/bin/bash HOSTTYPE=i386-linux OSTYPE=linux HOME=/ TERM=linux PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin RUNLEVEL=3 INIT_VERSION=sysvinit-2.74 _=/usr/local/bin/tcpserver PROTO=TCP TCPLOCALPORT=25 TCPREMOTEIP=192.153.153.123 TCPLOCALIP=192.153.153.208 TCPREMOTEPORT=2363 TCPLOCALHOST=qmail.colloquium.co.uk TCPREMOTEHOST=ms.vti.co.uk VENDOR=intel LOGNAME=qmaild USER=qmaild GROUP=nofiles HOST=post REMOTEHOST=ms.vti.co.uk exec /usr/local/bin/setlock -nx 192.153.153.123/seriallock /usr/local/bin/maildirsmtp 192.153.153.123 autoturn-192.153.153.123- 192.153.153.123 AutoTURN The maildirsmtp command here is the same as used manually Cheers, Tom
Re: serialmail/autoTURN not working
"Tom Furie" [EMAIL PROTECTED] wrote: Change your smtpd startup command to something like: Then connect to port 25 from your client and look at /tmp/autoturnlog. Make sure the maildirsmtp command is exactly right. contents of autoturnlog entry - Thu Jul 22 16:55:52 GMT 1999 PWD=/var/qmail/autoturn HOSTNAME=post CONSOLE=/dev/console PREVLEVEL=N AUTOBOOT=YES runlevel=3 MACHTYPE=i386 SHLVL=3 previous=N BOOT_IMAGE=linux SHELL=/bin/bash HOSTTYPE=i386-linux OSTYPE=linux HOME=/ TERM=linux PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin RUNLEVEL=3 INIT_VERSION=sysvinit-2.74 _=/usr/local/bin/tcpserver PROTO=TCP TCPLOCALPORT=25 TCPREMOTEIP=192.153.153.123 TCPLOCALIP=192.153.153.208 TCPREMOTEPORT=2363 TCPLOCALHOST=qmail.colloquium.co.uk TCPREMOTEHOST=ms.vti.co.uk VENDOR=intel LOGNAME=qmaild USER=qmaild GROUP=nofiles HOST=post REMOTEHOST=ms.vti.co.uk exec /usr/local/bin/setlock -nx 192.153.153.123/seriallock /usr/local/bin/maildirsmtp 192.153.153.123 autoturn-192.153.153.123- 192.153.153.123 AutoTURN The maildirsmtp command here is the same as used manually Hm, OK, are setlock and maildirsmtp executable by qmaild? Are /, /usr, /usr/local, and /usr/local/bin world executable? I'm running out of ideas. Perhaps replace: exec /usr/local/bin/setlock -nx $TCPREMOTEIP/seriallock \ /usr/local/bin/maildirsmtp $TCPREMOTEIP autoturn-$TCPREMOTEIP-$TCPREMOTEIP AutoTURN ' 21 | /var/qmail/bin/splogger smtpd 3 with: exec /usr/local/bin/setlock -nx $TCPREMOTEIP/seriallock \ /usr/bin/strace /usr/local/bin/maildirsmtp $TCPREMOTEIP autoturn-$TCPREMOTEIP-$TCPREMOTEIP AutoTURN ' 21 /tmp/autoturn.strace and examine /tmp/autoturn.strace to see what maildirsmtp is doing. -Dave
Re: serialmail/autoTURN not working
Hi Dave, Hm, OK, are setlock and maildirsmtp executable by qmaild? Are /, /usr, /usr/local, and /usr/local/bin world executable? I'm running out of ideas. They are, [root@post bin]# ls -l maildirsmtp setlock -rwxr-xr-x 1 qmaild root 195 Jul 21 14:51 maildirsmtp -rwxr-xr-x 1 root root 8572 Jul 21 14:51 setlock [root@post bin]# ls -ld / /usr /usr/local /usr/local/bin drwxr-xr-x 17 root root 1024 Jun 25 15:41 / drwxr-xr-x 19 root root 1024 Jul 9 16:17 /usr drwxr-sr-x 13 root root 1024 Jul 20 12:58 /usr/local drwxr-sr-x 2 root root 1024 Apr 28 09:02 /usr/local/bin and examine /tmp/autoturn.strace to see what maildirsmtp is doing. Hmm, absolutely nothing in the output? Definitely seems something is wrong there. Cheers, Tom
serialmail/autoTURN not working
Hello, I initially posted this to the serialmail mailing list, but since it doesn't look as though I'm getting any response there I thought I'd try here. - I have qmail 1.03, ucspi-tcp 0.84 and serialmail 0.75 installed on Redhat Linux 5.2 kernel 2.2.9. The system essentially works, i.e. incoming mail goes into the correct queue directory and I can use maildirsmtp to push queued mail to the target when the link is up. The problem is that when the client machine sends mail out, it doesn't trigger the server to send mail to the client. The logs don't show anything to help me shed any light on the problem. As far as I know I followed the instructions correctly, but nothing I do seems to fix this problem. Thanks for any help you can offer, Tom.
Serialmail won't run from cron
Hello, I'm using serialmail-70 over a ppp link for outgoing mail on a linux box. From the ip-up scripts it runs perfectly. However, if the conection stays up, I call serialmail from a crontab on the hour. I have the path to tcpclient set as a system wide path, and call serialmail from the crontab as root. Neither serialmail nor fetchmail run when called from the crontab if they are currently running. When called from the crontab, syslog always spits one (or both) of the 2 following errors: Jul 2 10:00:02 gateway serialmail: 930920402.294743 maildirserial: fatal: unabl e to get scanner status: no child processes Jul 2 11:00:01 gateway serialmail: 930924001.911220 maildirserial: fatal: unabl e to run tcpclient: file does not exist Anyone? Cheers - eric + + + + + + + + + + + + + + + + + + + + Spark Sistemas E-mail - presentado por IWCC Argentina S.A. Tel: 4702-1958 e-mail: [EMAIL PROTECTED] + + + + + + + + + + + + + + + + + + + +
Re: Serialmail won't run from cron
Eric Dahnke [EMAIL PROTECTED] wrote: I'm using serialmail-70 over a ppp link for outgoing mail on a linux box. From the ip-up scripts it runs perfectly. However, if the conection stays up, I call serialmail from a crontab on the hour. Smells like an environment difference. I have the path to tcpclient set as a system wide path, What's that? and call serialmail from the crontab as root. Neither serialmail nor fetchmail run when called from the crontab if they are currently running. What do you mean? You have some kind of locking mechanism? When called from the crontab, syslog always spits one (or both) of the 2 following errors: Jul 2 10:00:02 gateway serialmail: 930920402.294743 maildirserial: fatal: unable to get scanner status: no child processes Jul 2 11:00:01 gateway serialmail: 930924001.911220 maildirserial: fatal: unable to run tcpclient: file does not exist Don't know about the first one, but the second clearly says that tcpclient wasn't in the PATH. I would create a script called run_serialmail that does nothing but: #!/bin/sh PATH=$PATH:/var/qmail/bin:/path/to/tcpclient:/path/to/anything/else export PATH (serialmail command from your current crontab) then tell cron to run run_serialmail. -Dave
Serialmail
I have been trying to automate the uploading of messages from a Maildir to a remote SMTP server (my isp's). Using serialmail on RedHat 6 If I execute /usr/local/bin/maildirsmtp ~alias/pppqueue alias-ppp- smtpmail.globalnet.co.uk jeacocke at the command prompt all works fine However when I put it in a /etc/ppp/ip-up.local script it doesn't work Any Ideas Stewart
Re: Serialmail
On Mon 1999-06-21 (14:32), Stewart Jeacocke wrote: I have been trying to automate the uploading of messages from a Maildir to a remote SMTP server (my isp's). Using serialmail on RedHat 6 If I execute /usr/local/bin/maildirsmtp ~alias/pppqueue alias-ppp- smtpmail.globalnet.co.uk jeacocke at the command prompt all works fine However when I put it in a /etc/ppp/ip-up.local script it doesn't work Any Ideas From the maildirsmtp man page: maildirsmtp needs tcpclient in $PATH Perhaps when /etc/ppp/ip-up.local executes /usr/local/bin or wherever tcpclient is, is not in the PATH. Try something like: PATH=$PATH:/usr/local/bin maildirsmtp ~alias/pppqueue ... HTH Stewart - Keith -- Keith Burdis - MSc (Com Sci) - Rhodes University, South Africa Email : [EMAIL PROTECTED] WWW : http://www.rucus.ru.ac.za/~keith/ IRC : Panthras JAPH "Any technology sufficiently advanced is indistinguishable from a perl script" Standard disclaimer. ---
Re: qmail/serialmail queue names
Note that there's a separate serialmail mailing list. Tom Furie writes: For readability and manageability I would prefer to create the queues by hostname, You can give the maildir whatever name you want, as long as you set up an appropriate symbolic link from the IP address. ---Dan
qmail/serialmail queue names
Hello, I am using qmail with serialmail for smtp queues. When I create a queue using the targets IP address everything works fine, I can push the mail out and the target can initiate the transfer by connecting to the SMTP port on my server. For readability and manageability I would prefer to create the queues by hostname, however when I do this the target can no longer initiate the transfer, although I can still push mail to them when they are up. I realise this is more a serialmail question than qmail, but can anyone advise me how to get round this? Cheers, Tom
serialmail over ssh
Hi. Here's a small utility I wanted to share
(and get some peer review on;)
Serialmail seemed to me almost ideal for dialup
links. I never liked fetchmail.. But then again,
fetchmail could easily operate under ssh.
qmtpoverssh is a simple wrapper for serialqmtp
and qmail-qmtpd that runs under maildirserial.
It runs serialqmtp on one end but tunnels the
connection through ssh and runs qmail-qmtpd on
the other end (note qmail-qmtpd does not have to
be listening on a port - it will used directly).
Usage is like this:
maildirserial dir prefix qmtpoverssh prefix2 hostname user
prefix and prefix2 will usually be the same;
look at the documentation of maildirserial and
serialqmtp. hostname and user specify where the
ssh connection will be made.
You have to have RSA authentication or something
similar for this to work. I suggest making a new
key with an empty password and limited access.
TODO:
give qmail-qmtpd some environment variables to
make it log information more nicely.
--
Havoc Consulting | unix, linux, perl, mail, www, internet, security consulting
+358 50 5486010 | software development, unix administration, training
#include unistd.h
#include stdio.h
/* maildirserial [-b] [-tlifetime] dir prefix
qmtpssh prefix2 host login */
#define PROGNAME "qmtpoverssh"
#define READ 0
#define WRITE 1
void fail(char *s) {
fprintf(stderr,"%s: failure: %s\n",PROGNAME,s);
exit(100);
}
void defer(char *s) {
fprintf(stderr,"%s: deferral: %s\n",PROGNAME,s);
exit(111);
}
int main (int argc, char **argv) {
int pid;
int toserial[2];
int fromserial[2];
if (argc4) { fail("usage: qmtpoverssh prefix host login."); }
if (pipe(toserial)==-1) { defer("pipe to serialqmtp failed."); }
if (pipe(fromserial)==-1) { defer("pipe from serialqmtp failed."); }
pid=fork();
if (pid==-1) { defer("fork failed."); }
if (pid==0) { /* child */
if (dup2(toserial[READ],6)==-1) { defer("dup2 failed on stdin."); }
if (dup2(fromserial[WRITE],7)==-1) { defer("dup2 failed on stdout."); }
argv[0] = "serialqmtp";
argv[2] = NULL;
execvp("serialqmtp", argv);
defer("exec serialqmtp failed");
}
else { /* parent */
if (dup2(toserial[WRITE],1)==-1) { defer("dup2 failed on stdin."); }
if (dup2(fromserial[READ],0)==-1) { defer("dup2 failed on stdout."); }
execlp("ssh", "ssh","-q",argv[2],"-l",argv[3],"/usr/sbin/qmail-qmtpd");
defer("exec ssh failed");
}
}
Re: serialmail net
Ralf Nagel wrote: Hi, I am running a small "masqueraded" network (4 linux-machines, 1 NT). The mail (qmail of course) setup seems to be okay - everything works fine as far as local and intranet traffic (linux - linux) is concerned. But how can I collect all outgoing mail on a central "mail server" waiting for the next dial up connection for sending out? AND How can I incorporate the NT-machine (intranet and outgoing)? Thanks...Ralf using Fetchmail (for example), and launching it with your /etc/ppp/ip-up.local (or whatever you call it).
Re: serialmail net
Fabrice Scemama wrote: Ralf Nagel wrote: Hi, I am running a small "masqueraded" network (4 linux-machines, 1 NT). The mail (qmail of course) setup seems to be okay - everything works fine as far as local and intranet traffic (linux - linux) is concerned. But how can I collect all outgoing mail on a central "mail server" waiting for the next dial up connection for sending out? AND How can I incorporate the NT-machine (intranet and outgoing)? Thanks...Ralf using Fetchmail (for example), and launching it with your /etc/ppp/ip-up.local (or whatever you call it Oh, my bad English, I suppose... Fabrice, I am using fetchmail for my INCOMING mail! I would like to put all my OUTGOING mail on a central server (one of my own linux-machines) using the serialmail package for dial up outbound. But thanks for your quick response Ralf
Re: serialmail net
Ralf Nagel wrote: Fabrice Scemama wrote: Ralf Nagel wrote: Hi, I am running a small "masqueraded" network (4 linux-machines, 1 NT). The mail (qmail of course) setup seems to be okay - everything works fine as far as local and intranet traffic (linux - linux) is concerned. But how can I collect all outgoing mail on a central "mail server" waiting for the next dial up connection for sending out? AND How can I incorporate the NT-machine (intranet and outgoing)? Thanks...Ralf using Fetchmail (for example), and launching it with your /etc/ppp/ip-up.local (or whatever you call it Oh, my bad English, I suppose... Fabrice, I am using fetchmail for my INCOMING mail! I would like to put all my OUTGOING mail on a central server (one of my own linux-machines) using the serialmail package for dial up outbound. But thanks for your quick response Ralf This seems to be working like that by default. But you need a working DNS on your local SMTP.
serialmail/qmail workaround needed
Hello List, I've got a dialup client with a qmail/fetchmail/serialmail instalation acting as their mailgateway. The client wants to restrict some of the accounts to internal mail use only. Question is, how can I keep such restricted users' messages from ending up in serialmail's outgoing pppdir? (obviously, the restricted user would never receive any external messages, but he or she would be able to send to any external address they like, no?) - cheers eric
Re: Serialmail fd 7 error!
On Thu, Nov 18, 1999 at 10:14:09AM +0100, Rok Papez wrote: Hi Roger, qmail and serialmail m.l. On Thu, 18 Nov 1999, Roger Wrethman wrote: Go and have a look at http://www.e-smith.net They have this all down to a tee. I was expecting help It seems I've got a commercial :-(. I guess Qmail/serialmail just isn't up to the job. Everybody can smart-ass around about Linux support how great the mailing list/newsgroup support is and that it's better than commercial. My experiance (specialy with qmail/serialmail) shows that this is not the case. The people who know don't bother to answer, the people who don't know smart-ass around :-. I'm sorry but this is very dissapointing that no-one on qmail nor serialmail mailing list is able to just give me a hint (RTFM would do, if I accidently missed the docs - I do a lot of RTFM on our local user group m.l.). But it is not like I'm the power user who can go in and use the RTSL (Read The Source, Luke). Obviously a step in the right direction would be to dump Qmail/Serialmail altogether. Local user group people know only about sendmail and qmail users are obviously unwilling to help out. I'll mail djb personaly.. maybe he will answer altough I doubt it... I'll probably get ditched together with SPAM into /dev/null. Hi Well.. if you think there is not enough support for linux/free software, go on, and install exchange server (running nt-microsoft-commercial-help) I guess if what you need is an easy job, installation will be faster. It will run slower, be a bit mysterious (like all those windows things) - and of course M$ will respond to mails you send to them asking for help. I am quite sure, just will just have to call the hotline, and those nice competent guys there will call you back, telling you how to use RBL/IMAP/filter mails/chack for viruses/tune your mailserver. If exchange server can´t do what you need, they will incorporate the changes you need in the next release, if you ask really nice, they will give you there software for 1/2 the price. greetings, Florian Pflug
RE: Serialmail fd 7 error!
Hi Roger, qmail and serialmail m.l. On Thu, 18 Nov 1999, Roger Wrethman wrote: Go and have a look at http://www.e-smith.net They have this all down to a tee. I was expecting help It seems I've got a commercial :-(. I guess Qmail/serialmail just isn't up to the job. Everybody can smart-ass around about Linux support how great the mailing list/newsgroup support is and that it's better than commercial. My experiance (specialy with qmail/serialmail) shows that this is not the case. The people who know don't bother to answer, the people who don't know smart-ass around :-. I'm sorry but this is very dissapointing that no-one on qmail nor serialmail mailing list is able to just give me a hint (RTFM would do, if I accidently missed the docs - I do a lot of RTFM on our local user group m.l.). But it is not like I'm the power user who can go in and use the RTSL (Read The Source, Luke). Obviously a step in the right direction would be to dump Qmail/Serialmail altogether. Local user group people know only about sendmail and qmail users are obviously unwilling to help out. I'll mail djb personaly.. maybe he will answer altough I doubt it... I'll probably get ditched together with SPAM into /dev/null. -- best regards, Rok Papez.
RE: Serialmail fd 7 error!
Hey Rok, how's the trolling today? You checked TFM 'man tcpclient', right? Perhaps you could describe the efforts you've made to resolve your trouble. We already know about the throwing about of insults, but that's not generally a success strategy. What else have you done? -- Jeff Hayward On Thu, 18 Nov 1999, Rok Papez wrote: Hi Roger, qmail and serialmail m.l. On Thu, 18 Nov 1999, Roger Wrethman wrote: Go and have a look at http://www.e-smith.net They have this all down to a tee. I was expecting help It seems I've got a commercial :-(. I guess Qmail/serialmail just isn't up to the job. Everybody can smart-ass around about Linux support how great the mailing list/newsgroup support is and that it's better than commercial. My experiance (specialy with qmail/serialmail) shows that this is not the case. The people who know don't bother to answer, the people who don't know smart-ass around :-. I'm sorry but this is very dissapointing that no-one on qmail nor serialmail mailing list is able to just give me a hint (RTFM would do, if I accidently missed the docs - I do a lot of RTFM on our local user group m.l.). But it is not like I'm the power user who can go in and use the RTSL (Read The Source, Luke). Obviously a step in the right direction would be to dump Qmail/Serialmail altogether. Local user group people know only about sendmail and qmail users are obviously unwilling to help out. I'll mail djb personaly.. maybe he will answer altough I doubt it... I'll probably get ditched together with SPAM into /dev/null. -- best regards, Rok Papez.
RE: Serialmail fd 7 error! Qmail support
Hello Jeff. On Thu, 18 Nov 1999, Jeff Hayward wrote: - Hey Rok, how's the trolling today? Great!!! :)). No, realy. I actualy got a *response* (yours). It is not a polite one (I didn't expect it to be), but at least it *is* there... it is even suggesting something. Was that "RTFM" so hard to say the first time I asked for help ?? :-). It didn't help much.. but it was a gesture. You actualy proved that when politeness doesn't get you anywhere trolling might :). - You checked TFM 'man tcpclient', right? Perhaps you could describe Actualy I just did (man 1 tcpclient)... I still don't have a clue why it works when I telnet and why it doesn't when I fork() and exec() from daemon. Since daemon environment is a bit different I realy hopped for someone more experianced to help me out And btw.: I didn't check tcpclient *before* becouse I didn't notice maildirsmtp is a script. I apologize for not knowing everything :-(. I also alopologize for not checking every executable on my sistem if is is a script or a binary image - but what can you expect from a simple user. And about the tcpclient errors... When run from telnet maildirsmtp worked and when run from a daemon, errors got lost to /dev/null becouse I didn't redirect error logging correctly (I did "21 " instead of " 21" ). - the efforts you've made to resolve your trouble. We already know about the throwing about of insults, but that's not generally a Throwing insults? Let me check: Ok one might be here: - Everybody can smart-ass around about Linux support how great the mailinglist/newsgroup support is and that it's better than commercial. - This one applies only if you claim that linux support is great. And the other one can apply only if you "don't know": - The people who know don't bother to answer, the people who don't know smart-ass around :-. - I was a bit upset I apologize for the later one.. but the smart-assing about *great* Linux support stays!!! Linux support isn't great and the docs aren't great (except for some *realy* great HOWTOs in /usr/doc/HOWTO). And guess what.. the first time someone actualy had to tell me where to look for them :). A "RTFM /usr/doc/HOWTO/*" got me "on the track". Can you please do the same for qmail+serialmail ? about the throwing about of insults, but that's not generally a success strategy. What else have you done? Since you obviously know more about success strategies then me, please do help me and show me how to get help. - success strategy. What else have you done? I've searched the Qmail and Serialmail mailing list archives for similar problems. I've serached the www.qmail.org site for "serialmail" and "maildirsmtp". I did "man maildirsmtp". I did "cat /opt/qmail/doc/* | grep serialmail". I've read "/opt/serialmail/doc/serialmail/*" files. And *then* I asked on the Qmail mailing list. -- best regards, Rok Papez.
RE: Serialmail fd 7 error!
The guy who sent you to www.e-smith.net was trying to help you. You can download their package for free, burn it to a CD, and then install it on one of your systems. You could opt to pay for a CD and they also offer full support, but this isn't a requirement. I wouldn't be so quick to think people on these mailing lists are trying to be snide in their remarks. -Original Message- From: Rok Papez [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 18, 1999 4:14 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Serialmail fd 7 error! Hi Roger, qmail and serialmail m.l. On Thu, 18 Nov 1999, Roger Wrethman wrote: Go and have a look at http://www.e-smith.net They have this all down to a tee. I was expecting help It seems I've got a commercial :-(. I guess Qmail/serialmail just isn't up to the job. Everybody can smart-ass around about Linux support how great the mailing list/newsgroup support is and that it's better than commercial. My experiance (specialy with qmail/serialmail) shows that this is not the case. The people who know don't bother to answer, the people who don't know smart-ass around :-. I'm sorry but this is very dissapointing that no-one on qmail nor serialmail mailing list is able to just give me a hint (RTFM would do, if I accidently missed the docs - I do a lot of RTFM on our local user group m.l.). But it is not like I'm the power user who can go in and use the RTSL (Read The Source, Luke). Obviously a step in the right direction would be to dump Qmail/Serialmail altogether. Local user group people know only about sendmail and qmail users are obviously unwilling to help out. I'll mail djb personaly.. maybe he will answer altough I doubt it... I'll probably get ditched together with SPAM into /dev/null. -- best regards, Rok Papez.
Splogger w/ serialmail. More logging info?
Hello List, Splogger logs my outgoing serialmail connections as such. Jan 13 19:26:03 gateway splogger: 916266363.922180 maildirserial: info: new/916257200.459.gateway.godel.com.ar succeeded: 199.227.85.32 said: 250 ok 916269611 qp 4983 Is there anyway to get more information than this? I'd like to get the sender's address if possible. Sender and recipient even better. Many thx - eric __ Get Your Private, Free Email at http://www.hotmail.com
Re: qmail, fetchmail, serialmail et al
-BEGIN PGP SIGNED MESSAGE- But now what? How do I get serialmail --- if that is what I should be using --- to send email out to my ISP? Or have I wandered down the wrong path? If you followed the advice in the FAQ (created an ~alias/pppdir maildir and put the line ":alias-ppp" in your /var/qmail/control/virtualdomains) all your outgoing mail should be in the ~alias/pppdir directories. Just arrange for serialmail to run whenever your link comes up (e.g.: run it in your ip-up script) /var/qmail/bin/maildir2smtp ~alias/pppdir alias-ppp- ip.address.of.your.smtp.relay your-helo-name A better option (IMHO) is to apply the patch and foolow the directions at http://www.warren.demon.co.uk/qmail.html If you don't want to deliver mail yourself (you're on a slow, intermittent link *and* trust the smtp server of you ISP) you can use it to deliver mail by putting a line in /var/qmail/control/smtproutes :name.of.your.smtp.relay Bye - -- Luca Olivetti | Tarifa Plana ya! http://tarifaplana.home.ml.org/ http://www.luca.ddns.org/ | FAQhttp://www.luca.ddns.org/ptp-faq.html - UNETE A LA ASOCIACION DE INTERNAUTAS: HTTP://WWW.INTERNAUTAS.ORG -BEGIN PGP SIGNATURE- Version: 2.6.3i Charset: latin1 iQEVAwUBNo9dEC+cN8LMozC5AQGiNgf6As+SDR6Zn8NRTwDA/cXwjreHYWT5EldH ZpPjL7oKaayKEqy9P8hwft4gbM2sj5hq7MkKZpnDM4UpB2X+IHMTxpFY+Foq07kg EE4z2q0CRbj17cSpN7WBcgGC114YMy9GGs4khz+hZ+lkXdx2O9ATDkf+n5Yv/5CC mtqw/5daATv1e+fabBABTJVU0Pa71wDdL7OCM8T+fUG5n6KtKfS1vKu0k7ERYxF5 lfWFL0fNCQ83d0kC7bpvVgBanPZXZfAm+YznMkHn5teRQu+8pm4Zp2hHr2QtdZ9t NJxEiwOWE7gyUeokwAn4b7lx+piGGaAuvQYO9boKMwcISIY66prZJg== =9its -END PGP SIGNATURE-
qmail, fetchmail, serialmail et al
I am sorely puzzled. I have installed qmail, fetchmail, serialmail and several other odds and ends on a separate server/firewall machine to handle email for a small office. I have fetchmail set up to download incoming email from our ISP and feed it to qmail which distributes it. This seems to be working correctly, though I have only run small test cases so far. My problem is how to get outgoing mail to work. I now have qmail set up to allow RELAYCLIENT for the local machines and it will now accept outgoing email from those machines and queue it in the remote queue. But how do I get it to go out to my ISP when ppp is up? The only clue I found was in the qmail FAQ which said "How do I set up a separate queue for a SLIP/PPP link?" The answer was use serialmail, which I have downlaoded and installed along with tcpserver and tcpclient. But now what? How do I get serialmail --- if that is what I should be using --- to send email out to my ISP? Or have I wandered down the wrong path? Help! andy p.s. I am not a Unix newbie, though I am several years out of date, but I am a Linux and qmail newbie Andy Davidson --- Pheon Research --- 503-537-0985 If you know what you're doing, you're not learning anything.
problem with serialmail
i have installed serialmail on various machines without any problem,
but now i have a problem, it won't deliver any mail, and without
warnings or any error messages...
here is last few lines of strace:
[priyadi@priyadi priyadi]$ strace /usr/local/bin/maildirsmtp ~/pppdir
priyadi-ppp- bdg.centrin.net.id priyadi.ml.org 21 | tail -20
sigaction(SIGPIPE, {SIG_IGN}, NULL) = 0
chdir("/home/priyadi/pppdir") = 0
open(".", O_RDONLY|O_NONBLOCK) = 3
chdir("/var/qmail") = 0
open("control/me", O_RDONLY|O_NONBLOCK) = 4
read(4, "priyadi.ml.org\n", 128)= 15
close(4)= 0
open("control/bouncefrom", O_RDONLY|O_NONBLOCK) = -1 ENOENT (No such file
or directory)
open("control/bouncehost", O_RDONLY|O_NONBLOCK) = -1 ENOENT (No such file
or directory)
open("control/doublebouncehost", O_RDONLY|O_NONBLOCK) = -1 ENOENT (No such
file or directory)
open("control/doublebounceto", O_RDONLY|O_NONBLOCK) = -1 ENOENT (No such
file or directory)
fchdir(3) = 0
pipe([4, 5])= 0
fork() = 6877
close(5)= 0
read(4, "", 1024) = 0
--- SIGCHLD (Child exited) ---
close(4)= 0
wait4(6877, [WIFEXITED(s) WEXITSTATUS(s) == 0], 0, NULL) = 6877
_exit(0)
the system is linux 2.1.131 (it doesn't work in 2.0.36 either BTW),
someone please help me, i really have no idea here...
Re: problem with serialmail
On Sat, Jan 02, 1999 at 05:17:49AM +0700, Priyadi Iman Nurcahyo wrote:
i have installed serialmail on various machines without any problem,
but now i have a problem, it won't deliver any mail, and without
warnings or any error messages...
here is last few lines of strace:
[priyadi@priyadi priyadi]$ strace /usr/local/bin/maildirsmtp ~/pppdir
priyadi-ppp- bdg.centrin.net.id priyadi.ml.org 21 | tail -20
sigaction(SIGPIPE, {SIG_IGN}, NULL) = 0
chdir("/home/priyadi/pppdir") = 0
open(".", O_RDONLY|O_NONBLOCK) = 3
chdir("/var/qmail") = 0
open("control/me", O_RDONLY|O_NONBLOCK) = 4
read(4, "priyadi.ml.org\n", 128)= 15
close(4)= 0
open("control/bouncefrom", O_RDONLY|O_NONBLOCK) = -1 ENOENT (No such file
or directory)
open("control/bouncehost", O_RDONLY|O_NONBLOCK) = -1 ENOENT (No such file
or directory)
open("control/doublebouncehost", O_RDONLY|O_NONBLOCK) = -1 ENOENT (No such
file or directory)
open("control/doublebounceto", O_RDONLY|O_NONBLOCK) = -1 ENOENT (No such
file or directory)
fchdir(3) = 0
pipe([4, 5])= 0
fork() = 6877
close(5)= 0
read(4, "", 1024) = 0
--- SIGCHLD (Child exited) ---
close(4)= 0
wait4(6877, [WIFEXITED(s) WEXITSTATUS(s) == 0], 0, NULL) = 6877
_exit(0)
This is what an strace of serialsmtp normally looks like when the maildir
is empty. See the fork()? That is where the process splits in two. The _other_
half (which you are not tracing while you should) checks the maildir. If you're
sure something _is_ wrong, add -f to strace and tell us what happens.
Greetz, Peter.
--
squeezer AND I AM GONNA KILL MIKE| Peter van Dijk
squeezer hardbeat, als je nog nuchter bent: | [EMAIL PROTECTED]
squeezer @date = localtime(time); | realtime security d00d
squeezer $date[5] += 2000 if ($date[5] 37); |
squeezer $date[5] += 1900 if ($date[5] 99); |-x- I love Rhona -x-
