Re: qmail and Lotus Notes
On Tue, 7 Aug 2001 [EMAIL PROTECTED] wrote: > The qmail server is sending and receiving emails from Internet, and is also > able to send emails to the Notes MTA server. The problem is that the Notes > MTA couldn't send emails to the qmail server, although I can logon the > Notes MTA and open port 25 to the qmail server. What does the log on the Notes server say? What does the log on your qmail host say, are any connections from the Notes server logged (not counting your telnet sessions)? Could the Notes server be sending bare linefeeds? Try recordio to find out what's happening. Mads
Re: SV: relay problem
On Fri, 25 May 2001, Pål Fr. Johansen wrote: > Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm ^^ ^^ ^^ ^^ > SoHOW THE F.. DO I UNSUBSCRIBE, from this...amazing mail-list ? By using the info the list gave you when you subscribed. If you've for some reason has thrown it away away you might get it once more. The contact address is written in every message on this list, see above. Doesn't your MUA show you this info? By the way, RFC 2822 section 3.6.5 says that you may put "Re: " in front of the Subject when you're answering. Why do you put "SV: " there? "SV" is an abbreviation of a Norwegian word, most subscribers of this list are not familiar with the Norwegian language. Ask your MUA vendor to fix this. Mads
Re: delivering problem
On Tue, 15 May 2001, Oscar Rodriguez Rodriguez wrote: > delivery 1: deferral: Uh-oh:_home_directory_is_writeble._(#4.7.0) ... Then check who has permission to write to that directory. Too many? Mads
Re: Virus found in message "Re: Qmail and Procmail"
> From: System Anti-Virus Administrator <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > A virus was discovered in an e-mail addressed to you. We have > rejected the infected mail so your computer will not be infected. Thank you. However, - a message from the list to me doesn't go through your computers. - you have now revealed that andreas2 is subscribed to the list. What about sending such warning messages to the envelope sender address? Or what about just dropping the infected messages silently? A simple 'grep ... exit 99' quietly stopped it for me. Sitting here with no virus but lots of warning messages it occurs to me that the latter is at least as disturbing as the first. Please consider doing something with your AV-software. Mads
Re: why didn't it send my msg?
> 2. How can I enable qmail-smtpd? What is the best way to do it? There are several ways to start qmail-smtpd. One is to use inetd. The other way, which is recommended by the author, is to use tcpserver. See http://cr.yp.to/qmail/faq/servers.html#tcpserver-smtpd Mads
Re: Compiling problems?
On Thu, 9 Nov 2000, Stian Brekmo wrote: > maildirwatch.c:62: warning: return type of `main' is not `int' These messages seems to be normal when compiling on RHL. > I 'm having big troubles getting qmail to work Could you be more specific? At what point in the INSTALL instructions does things stop working? Mads
Re: relaying
On Thu, 28 Sep 2000, Petr Novotny wrote: > On 28 Sep 2000, at 19:20, Alan Chung wrote: > > > I am trying to setup some relaying for tcp.smtp server. > > > > Can I put domain name instead of IP address in /etc/tcp.smtp-rules? > > No, unless you do some serious patching. mee@host:/local/src/ucspi-tcp-0.88> grep hostname CHANGES ui: tcpserver supports hostname rules. Am I missing something? Mads
Re: qmail on Digital UNIX 4.0D -- syslog problems
On 5 Jul 2000, Bjørn Nordbø wrote: > According to TEST.delivery qmail should syslog a line whenever > it starts. [...] Note that qmail logs to STDOUT. If you followed step 8 of INSTALL, you'll realize that it is splogger who feeds syslog. Since you apparently have daemontools installed I suggest you forget about syslog, and use multilog to do the logging. On our 4.0D boxes /service/qmail/run contains #!/bin/sh exec env - PATH="/var/qmail/bin:$PATH" qmail-start ./Mailbox and /service/qmail/log/run contains #!/bin/sh exec setuidgid qmaill multilog t s50 n20 /var/log/qmail which means that log entries end up in /var/log/qmail/current. We have a similar approach for the SMTP service using tcpserver, and it's all working very well. Mads
Re: Could my problems be Mandrake 7 security settings?
On Tue, 23 May 2000, James wrote: > So I manually make the directory accessible, then try to run ./rc again > (from /var/qmail) and get this error: > > "alert: cannot start: unable to open mutex" To fix the permissions, cd to your qmail source directory and type make setup check Mads
Re: Qmail installation on FreeBSD 4 following LWQ didn't work out
On Wed, 26 Apr 2000, Gabriel Ambuehl wrote: [...] svscan: No such file or directory If you install daemontools according to the instructions, svscan will be in /usr/local/bin, or where you specified it to be (conf-home). > [...] ignoring all advice > that FreeBSD people are giving)? If you installed it as a package svscan might be somewhere else, or, as in you case, not there at all due to an old version. DJB has made it easy to grab the latest version and follow some very simple installation instructions. I've installed daemontools a couple of times now, on FreeBSD and other platforms, and never felt any need for a package. What are the specific arguments against doing this on FreeBSD? Mads
Re: setuidgid fatal unknown account qmail
On Thu, 16 Mar 2000, PM Martin wrote: > Subject: setuidgid fatal unknown account qmail [...] though qmail is running > okay. If you followed the installation instructions you should have a user account named qmaill. Thats qmaill, not qmail. Mads
Re: qmail and uscpi-tcp
On Wed, 15 Mar 2000, Pierre-Yves DESLANDES wrote: > Hi everybody, i'm using Qmail with tcpserver.And i can't manage to use my mail >server to forward outgoing messages. What happens when you try to send a message? What does the log say? Mads
Re: change mailer-daemon address
On Fri, 11 Feb 2000, Magnus Østergaard wrote: > How can I change the mailer-daemon address to [EMAIL PROTECTED] > instead of [EMAIL PROTECTED] ? echo domain.foo > /var/qmail/control/bouncehost Then restart qmail. Read the qmail-send(8) man page. Look for bouncehost and bouncefrom. Mads
Re: Retry Schedule and bounce time?
On Wed, 2 Feb 2000 [EMAIL PROTECTED] wrote: > [...] the retry schedule... See http://Web.InfoAve.Net/~dsill/lwq.html#retry-schedule > But I can't seem to find how qmail decides to give up on delivering a msg. > My experience is that it's around 3 days, but I'd like to know exactly. Try /var/qmail/bin/qmail-showctl | grep queuelifetime If you want to change this to 3 days ( 3 x 86400 secs), try echo 259200 > /var/qmail/control/queuelifetime kill -HUP Mads
Re: multilog datestamping
On Wed, 2 Feb 2000, A Hoffman wrote: [...] For some reason tai64nlocal > does not appear to be kicking in. > # more /var/qmail/supervise/qmail-send/log/run > #!/bin/sh > exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t > /var/log/qmail > > # more /var/qmail/supervise/qmail-smtpd/log/run > #!/bin/sh > exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t > /var/log/qmail/smtpd These scripts don't call tai64nlocal anywhere, that's why. :-) Mads
Re: remote root qmail-pop with vpopmail advisory and exploit with patch (fwd)
On Wed, 26 Jan 2000, Petr Novotny wrote: [...] Everyone will suggest you to ditch splogger > and use cyclog instead. Well, cyclog is already history for some of us. :-) History: BigBang -> syslog -> splogger -> cyclog -> multilog Mads
Re: Unable to deliver to all but one
On Sun, 23 Jan 2000, Jacob Joseph wrote: > What does this mean? > deferral: /bin/sh:_dot-forward:_command_not_found/ The message says that qmail can't find dot-forward. Take a look at this user's .qmail and/or .forward file. Have you installed dot-forward? Mads
Re: Timezone
On Thu, 20 Jan 2000, Walt Mankowski wrote: > But there's a patch available that will use your local timezone > instead. [...] Sure, but why tamper with qmail's approach? When tracking down delivery problems it's easier for humans and programs to read the Received:-lines when all time stamps are in the same timezone rather than 10 different ones. To make it even harder some systems add strange symbolic names like EST, which don't tell me much. E might indicate east, and T probably means Time. East of me is Sweden, so EST must be Eastern Swedish Time. Dan made life easier. IMHO applying such patches makes it harder again. If you like to display the time stamps in a local timezone, ask your MUA author to make the MUA do so. Or take a look at http://cr.yp.to/mess822.html Mads
Re: Timezone
On Thu, 20 Jan 2000, Martin Renner wrote: [...] qmail is setting the time > to "11:55:06 -". Yes, qmail always uses UTC. Mads
Re: problem with users that has a "-" in their username
On Tue, 4 Jan 2000, Geir Høgberg wrote: [...] john also recieves [EMAIL PROTECTED]'s mail. Thats normal. john will receive john-anything. Se the dot-qmail(5) man page, "EXTENSION ADDRESSES". Mads
Re: tcpserver log failed connections?
On Thu, 14 Oct 1999, Fred Backman wrote: > I couldn't find it in the man pages, so is there a way to log failed > connections with tcpserver? (ie. connections which are defined as > illegal in the tcprules data file) tcpserver logs 'ok' if it accepts a connection, and 'deny' if it rejects it. Just try it and watch the log. Mads E. Eilertsen
Re: qmLogsort
On 27 May 1999, Monte Mitzelfelt wrote: > I think this one is ready for primetime. It groups mail log records by > message and delivery. It eliminates all of that scrolling up and down in > the log file looking for outcomes. Hmm, doesn't qmailanalog do the same thing for you? Mads
Re: MRTG && qmail
On 12 Feb 1999, Russell Nelson wrote:
> And qmail-mrtg follows:
Thanks for sharing it.
However, at least on my host, it always produces two lines of '0'.
A proper close of the matchup process makes zoverall happy! :-)
Mads
*** qmail-mrtg.orig Mon Mar 1 22:30:04 1999
--- qmail-mrtg Mon Mar 1 22:30:10 1999
***
*** 33,48
--- 33,49
open(QA, "|$qa/matchup >/tmp/out.$$ 5>$holdingfile") or die;
while() { print QA; }
close(P);
while(<>) {
split;
next if ($_[0] < $start || $_[0] >= $stop);
print QA;
}
+ close(QA);
# analyze the last five minutes.
open(REP, "$qa/zoverall ) {
if (/^Completed messages: (\d+)/) {
print "$1\n";
if (!$1) {
print "0\n";
Next MX never used when best MX says 520
I can't get mail delivered to a specific domain. The messages just stay in the queue. DNS says domainMX 0 host1 domainMX 10 host2 host1 says 520 Connection not authorised from this address. qmail connects to host1 and says deferral: Connected_to_N.N.N.N_but_greeting_failed./... qmail seemingly never tries host2. The administrators of domain says - this setup is intentional (sort of firewall/spam control) - why isn't your mailer using the second-best MX? - others have reported this too. They use qmail too. What's wrong here? The error code? qmail? Mads
