qmail Digest 25 Mar 2001 11:00:00 -0000 Issue 1314
Topics (messages 59645 through 59657):
omail-admin doesn't work with vmailmgr
59645 by: Mark Lo
Re: What is the default value of these control files
59646 by: Alexander Jernejcic
what rpm of vmailmgr do i need
59647 by: Mark Lo
Re: no mailbox here(#5.1.1) - don't works!
59648 by: Tetsu Ushijima
Re: bounce mail
59649 by: Tetsu Ushijima
Re: [vmailmgr] what rpm of vmailmgr do i need
59650 by: Olivier M.
Re: local vs remote delivery
59651 by: Tom Beer
Personal mail server
59652 by: Sridhar
Forwarding to another system.
59653 by: Roger Walker
Fatal qq error
59654 by: Tyrone Mills
[announce] oSpam version 0.01 - new project started
59655 by: Olivier M.
Re: redundant mail servers
59656 by: Russell Nelson
Log entry: success: did_0+0+0???
59657 by: Sam Laffere
Administrivia:
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
Hi,
I am trying to use omail-admin with vmailmgr, I can adduser or deluser
or add virtualdomains under the console windows. But, When I run it under
the web using omail-admin, An error messages stating that "Failed to open
socket file, is daemon running ?". I have installed vmailmgr-0.96.9-1 ,
vmailmgr-php-0.96.9-1, and vmailmgr-daemon-0.96.9-1 from rpm.
Please help me out
Thank you
hi,
[mailto:[EMAIL PROTECTED]] had many questions ...
have a look at http://www.lifewithqmail.org/
there you will find the answers and some really usefull background
information
:) alexander
Hi,
I would like to know what vmailmgr rpm do I need to run vmailmgr under
omail-admin.
Re: where can I get the rpm version of ucspi-tcp. I need this rpm to work
with vmailmgr-daemon-tcp-0.96.9-2.i386.rpm.
Thank you
Mark
Kep Brown writes:
> One hack is to write a simple shell script, mine is called qmail-aliasemail,
> that calls fastforward then runs another process if the user is still not
> found.
No need to write a script; just use the pass-through option
of fastforward:
-p Pass through. If fastforward does not find the
recipient in cdb, it exits 0, giving the message to
further commands in .qmail-default. If fastforward
finds the recipient, it forwards the message and
exits 99, so that further commands are skipped.
The .qmail-default file would look like:
|fastforward -d -p /etc/aliases.cdb
&postmaster
--
Tetsu Ushijima
Charles Cazabon writes:
> > Connected_to_203.184.222.2_but_sender_was_rejected./Remote_host_said:_553_Re
> > quested_action_not_taken:_mailbox_name_not_allowed/
>
> You sent mail to an address which doesn't exist. The remote server bounced
> it. End of story.
No. It's the _sender_ address that was rejected. A similar
problem was reported on this list several months ago. See:
http://www.ornl.gov/its/archives/mailing-lists/qmail/2000/11/msg00482.html
--
Tetsu Ushijima
On Sat, Mar 24, 2001 at 08:48:15PM +0800, Mark Lo wrote:
> I would like to know what vmailmgr rpm do I need to run vmailmgr under
> omail-admin.
The best way (which allways worked for me) is to take the .tar.gz
files, and to compile and install the stuff yourself.
Regards,
Olivier
--
_________________________________________________________________
Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
qmail projects: http://omail.omnis.ch - http://webmail.omnis.ch
Hi,
> > I'll try to set up my local delivery in qmail and been stuck in the
moment
> > and can't get out of it. I can use qmail for remote delivery. But if I
try to
> > make a local delivery it connects to teh net and delivers the message
via the
> > net to my pop box. Can anyone give me the path where to start from for
> > troubleshooting?
>
> Your logs make it look like the local delivery instruction contained a
> forwarding address which was remote.
>
> Post the results of `qmail-showctl`
user-ext delimiter: -.
paternalism (in decimal): 2.
silent concurrency limit: 120.
subdirectory split: 23.
user ids: 1004, 1005, 1006, 0, 1007, 1008, 1009, 1010.
group ids: 101, 102.
badmailfrom: (Default.) Any MAIL FROM is allowed.
bouncefrom: (Default.) Bounce user name is MAILER-DAEMON.
bouncehost: (Default.) Bounce host name is daemon.system.
concurrencylocal: (Default.) Local concurrency is 10.
concurrencyremote: (Default.) Remote concurrency is 20.
databytes: (Default.) SMTP DATA limit is 0 bytes.
defaultdomain: Default domain name is system.
defaulthost: (Default.) Default host name is daemon.system.
doublebouncehost: (Default.) 2B recipient host: daemon.system.
doublebounceto: (Default.) 2B recipient user: postmaster.
envnoathost: (Default.) Presumed domain name is daemon.system.
helohost: (Default.) SMTP client HELO host name is daemon.system.
idhost: (Default.) Message-ID host name is daemon.system.
localiphost: (Default.) Local IP address becomes daemon.system.
locals:
Messages for daemon.system are delivered locally.
me: My name is daemon.system.
percenthack: (Default.) The percent hack is not allowed.
plusdomain: Plus domain name is daemon.system.
qmqpservers: (Default.) No QMQP servers.
queuelifetime: (Default.) Message lifetime in the queue is 604800 seconds.
rcpthosts:
SMTP clients may send messages to recipients at daemon.system.
morercpthosts: (Default.) No effect.
morercpthosts.cdb: (Default.) No effect.
smtpgreeting: (Default.) SMTP greeting: 220 daemon.system.
smtproutes: (Default.) No artificial SMTP routes.
timeoutconnect: (Default.) SMTP client connection timeout is 60 seconds.
timeoutremote: (Default.) SMTP client data timeout is 1200 seconds.
timeoutsmtpd: (Default.) SMTP server data timeout is 1200 seconds.
virtualdomains: (Default.) No virtual domains.
defaultdelivery: I have no idea what this file does.
concurrencyincoming: I have no idea what this file does.
and `ls -l ~tom/.qmail*`
-rw-r--r-- 1 root root 18 Mar 23 15:40 /home/tom/.qmail
-rw-r--r-- 1 root root 9 Mar 11 16:58 /home/tom/.qmail.tmp
-rw-r--r-- 1 root root 11 Mar 13 03:08 /home/tom/.qmail~
, and
the contents of every file named .qmail* in tom's home directory.
/home/tom/Mailbox .qmail
/.Mailbox .qmail.tmp
Tom
hi
my first mail here. i've a shell a/c in my college and can i
install qmail ( for myself ) without being root or without the root being
disturbed ? i mean it is only for sending mails. i've thought abt several
issues here...
* where do i install it ? can it be done in /home/omicron/qmail ?
* how do i prevent qmail from running as qmail* and use omicron for
everything.
* can it be used for receiving mails... i mean the MX record does not
specify the port. so #25 is used. but if i make my qmail to bind to say
1025, then how do i receive the mails , if it is possible ?
Thanks in advance...
regards
omicron
--
Outside of a dog, a book is man's best friend. Inside of a dog, it is too
dark to read.
I need to forward all mail from the mailhost (2 domains) which is
on the public LAN through a VPN to an Exchange box for actual distribution
(The latter part is not my choice or decision.).
The FAQ 7.4 describes using .qmail files to forward everything to
the explicit host.
The qmail-remote(8) man page describes using the smtproutes file,
which may also work in this case.
What would be the most effective way to do so? The QMAIL box is
only there to receive everything from the Internet and send it to the
Exchange box.
Thanks.
--
Roger Walker <http://www.rat-hole.com>
Voice/Fax 1-780-440-2685 <http://www.man-from-linux.com>
"HIS Pain; YOUR Gain" <http://www.rope.net>
<http://www.rope.net/signature.html>
Hello again,
I've setup a web server as a null client. When I try to test QMail on that
machine I get the following error:
qmail-inject: fatal: qq unable to read configuration (#4.3.0)
Where should I be looking?
Thanks,
Tyrone
____________________________________________________
UNIX is user-friendly, it's just picky about who its friends are...
winmail.dat
Hello,
Just spent a few hours on a new little but maybe interesting project,
which should make all the spams comming to your mailbox disapear :)
Project homepage: http://omail.omnis.ch/ospam/
Description:
oSpam - An ultimative Perl & qmail based anti-Spam System
=====
Purpose of oSpam:
-----------------
It's a package inspired from the mapSoN tool, and other
tools used for example by the php-project mail server.
2 main features:
1) use it for your usenet postings: as From: address, you get
an "[EMAIL PROTECTED]" address, which will be
valid one week. After this delay, the mails sent to this
address will be put in "quarantaine", waiting for a confirmation
from the author, which will never happen if it is a spam.
2) use it as your main email address: put all your friends
addresses in your accepted.txt file. If somebody which isn't
in the list send you a mail, he will get a small and unique
confirmation request, and then the mail(s) will be delivered
transparentely.
Every operation is logged: look at the ~/maildir/ospam/ospam.log file
and at the source code to understand how the whole is working.
I hope you will find this tool usefull!
Beware: the whole is currently working, but it's not yet really
to use IRL : just posting this as a Request for Comments :)
--Olivier
--
_________________________________________________________________
Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
qmail projects: http://omail.omnis.ch - http://webmail.omnis.ch
PGP signature
Vincent Schonau writes:
> On Fri, Mar 23, 2001 at 11:01:51AM -0500, Russell Nelson wrote:
> > Gopi Sundaram writes:
>
> >> I'm reluctant to move to Maildir until we can get more MUAs to support
> >> them (specifically Pine and Netscape).
>
> > Wrong idea. Never expose your mailboxes to your users. Always use a
> > virtual mailbox system -- either pop3 or imap.
>
> Why?
Because if your application programs can see your mailboxes, then
you're stuck supporting those mailboxes. As a general rule, you
*always* want to hide objects behind an API. Whether those objects
are hardware Ethernet controllers hidden behind a packet driver, or a
mailbox hidden behind POP3, or a network connection hidden behind
tcpserver, you never want to expose any more details about anything
than you have to.
--
-russ nelson will be speaking at http://www.osdn.com/conferences/brie/
Crynwr sells support for free software | PGPok | Watch out! He's got an
521 Pleasant Valley Rd. | +1 315 268 1925 voice | opinion, and he's not
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | afraid to share it!
Good Morning to all, especially those burning the midnite oil!
This evening I caught my qmail/vpopmail server not doing it's job. I would
like to keep it from happening in the future, and to help fill in some blank
spots as to what really makes this thing work.
This server runs about 10 virtual domains, but only handles maybe 20 - 100
messages per hour. Light usage, I would guess.
For about the last 30 hours or so, it appears that all incoming mail has
been accepted for my domain 'sasnak.net', and then vaporized. All other
domains mail has been delivered successfully.
All log entries show this for 'sasnak.net'
delivery 28: success: did_0+0+0/
and the messages are nowhere to be found. A search of the mailing list
caused me to look at permissions/ownerships, so I created a new domain
(test.com) and compared these things. Nothing turned up.
Out of desperation, I tried
echo to: [EMAIL PROTECTED] | /var/qmail/bin/qmail-inject
and the messages was delivered properly. I thought maybe tcpserver
qmail-smtp might have been causing it, but before going any further, I tried
sending myself a message via sqwebmail, and it worked. It previously had
not been working. All the incoming mail has been delivered correctly since
then.
My specific questions are these.
Where did the mail go during this time?
What caused it to start working? Not my qmail-inject, I'm sure.
How do I keep it from happening again?
Where is there more info on the "success: did_0+0+0" and "success:
did_0+0+1" log messages? I have seen a few other numbers or combinations in
here and would like to know what they mean.
As a "probably not important" footnote, I had installed BigBrother on this
server in the last two weeks, but had made no changes recently. As part of
my troubleshooting, I had rebooted the machine and had not restarted
BigBrother about one hour before this started working again.
Thank You,
Sam Laffere
Just a clip of the logs:
Mar 24 23:10:30 moe qmail: 985497030.206191 info msg 112050: bytes 289 from
<[EMAIL PROTECTED]> qp 980 uid 1008
Mar 24 23:10:30 moe qmail: 985497030.214839 starting delivery 28: msg 112050
to local [EMAIL PROTECTED]
Mar 24 23:10:30 moe qmail: 985497030.215062 status: local 1/10 remote 0/20
Mar 24 23:10:30 moe qmail: 985497030.226354 delivery 28: success: did_0+0+0/
Mar 24 23:10:30 moe qmail: 985497030.226584 status: local 0/10 remote 0/20
Mar 24 23:10:30 moe qmail: 985497030.226741 end msg 112050
Mar 24 23:13:19 moe qmail: 985497199.789656 new msg 112050
Mar 24 23:13:19 moe qmail: 985497199.790402 info msg 112050: bytes 291 from
<[EMAIL PROTECTED]> qp 1021 uid 1008
Mar 24 23:13:19 moe qmail: 985497199.798631 starting delivery 29: msg 112050
to local [EMAIL PROTECTED]
Mar 24 23:13:19 moe qmail: 985497199.799290 status: local 1/10 remote 0/20
Mar 24 23:13:19 moe qmail: 985497199.888826 delivery 29: success: did_0+0+1/
Mar 24 23:13:19 moe qmail: 985497199.889097 status: local 0/10 remote 0/20
Mar 24 23:13:19 moe qmail: 985497199.889254 end msg 112050
Mar 24 23:14:16 moe qmail: 985497256.084798 new msg 112050
Mar 24 23:14:16 moe qmail: 985497256.085545 info msg 112050: bytes 293 from
<[EMAIL PROTECTED]> qp 1041 uid 1008
Mar 24 23:14:16 moe qmail: 985497256.092490 starting delivery 30: msg 112050
to local [EMAIL PROTECTED]
Mar 24 23:14:16 moe qmail: 985497256.092706 status: local 1/10 remote 0/20
Mar 24 23:14:16 moe qmail: 985497256.126467 delivery 30: success: did_0+0+0/
Mar 24 23:14:16 moe qmail: 985497256.126758 status: local 0/10 remote 0/20
Mar 24 23:14:16 moe qmail: 985497256.126914 end msg 112050
