Re: dns for qmail only??

2001-07-27 Thread Jeff_D_Sweeten

You avoid a second machine for internal/external DNS bu using BIND 9.1.x which
supports multiply view.

Jeff Sweeten
Sr. Internet Engineer
Aon
200 E Randolph
Chicago, Il 60601





Kourosh Ghassemieh [EMAIL PROTECTED] on 07/26/2001 02:21:43 PM

To:   Gary MacKay [EMAIL PROTECTED], [EMAIL PROTECTED]
cc:(bcc: Jeff D Sweeten/ASC/US/AON)

Subject:  Re: dns for qmail only??




You need to run a separate DNS server for internal queries, that's how I
have my DNS set up.  We use a separate DNS server for the internal
addresses and we don't have any problems.  qmail ignores /etc/hosts,
it needs a DNS server.

At 12:22 PM 7/26/2001 -0400, you wrote:
bind-9.1.0-10

Ricardo SIGNES wrote:
 
  In a message dated Thu, Jul 26, 2001 at 08:53:57AM -0400, Gary MacKay
 wrote:
   I moved qmail off of a 'do it all' box to it's own box. It's running
   great. My problem is that the old machine is still the DNS for my
   domain. When it sends status messages to me, it, I'm guessing, checks
   DNS and gets the public IP of the new box, can't connect to it from
   behind the firewall (both boxes are 192. ), so it sends it to the
   secondary MX record, which is my old ISP. I then get it via getmail cron
   job, but I'd like for it to deliver internally. I've changed the
   /etc/hosts to point to the 192. address, but qmail must not look at
   that. How can I have DNS giving out the public IP for the world, yet
   tell qmail the 192. addr??
 
  What DNS server are you running?
 
  --
  rjbs
 

 Part 1.2Type: application/pgp-signature

-

Kourosh Ghassemieh
MindWare Information Systems  Technologies
9255 Sunset Blvd, Penthouse
West Hollywood CA 90069
(310) 729-1784
[EMAIL PROTECTED]

Networking Solutions for Your Business









Re: Qmail resending multiple times...

2001-07-24 Thread Jeff_D_Sweeten

This is indicative of the Mimesweeper machine not being able to handle the
volume being passed it from the qmail machine.  We've had the same issues and
the group responsible for Mimesweeper (and in our case Mailsweeper) had to add
additional load balanced machines to keep up with qmail.

I reject their suggestion of reducing my concurrency since that only pushes the
problem back to sender.

Jeff Sweeten
Sr. Internet Engineer
Aon
200 E Randolph
Chicago, Il 60601






Darren Kukulka [EMAIL PROTECTED] on 07/24/2001 02:33:49 AM

To:   '[EMAIL PROTECTED]' [EMAIL PROTECTED]
cc:(bcc: Jeff D Sweeten/ASC/US/AON)

Subject:  Qmail resending multiple times...



Hi,

Just wanting to know if anyone has solved this behaviour...

We are running SMTP redirects via Qmail 1.03 through to a Mimesweeper mail
host.

Most messages make it through quite happily but every now and then we get
ones that hang around and get retransmitted, usually with the following
appearing in the log ;

delivery x: deferral:
Connected_to_xx.xx.xx.xx_but_connection_died._Possible_duplicate!_(#4.4.2)

Have been around the web to find someone else with a solution but to no
avail - closest I came to was some guy suggesting to check if the source
mail contained Bare CR's (think he was referring to bare carriage returns
but not sure).

Any ideas ?

Cheers,
Darren Kukulka
[EMAIL PROTECTED]







Re: Qmailanalog matchup error [Virus Checked]

2001-05-29 Thread Jeff_D_Sweeten

Sounds like a path PATH issue

You have have  ...\qmailanalog\bin in your path





John Scarborough [EMAIL PROTECTED] on 05/29/2001 02:23:15 PM

To:   [EMAIL PROTECTED]
cc:(bcc: Jeff D Sweeten/ASC/US/AON)
Subject:  Qmailanalog matchup error [Virus Checked]



I am trying to run matchup.  I have cleaned the maillog as
documented and generated a file to parse through matchup.
Running matchup results in output like below .

Any help you  TIA!

 /usr/local/qmailanalog/bin/matchup:
 [EMAIL PROTECTED]: No such file or directory
 /usr/local/qmailanalog/bin/matchup: 990959401.508748: command
 not found
 /usr/local/qmailanalog/bin/matchup: 990959401.510608: command
 not found
 /usr/local/qmailanalog/bin/matchup: 990959401.555309: command
 not found
 /usr/local/qmailanalog/bin/matchup: 990959401.558207: command
 not found
 /usr/local/qmailanalog/bin/matchup: 990959401.559713: command
 not found
 /usr/local/qmailanalog/bin/matchup: 990959420.577015: command
 not found
 /usr/local/qmailanalog/bin/matchup: 990959420.578531: command
 not found
 /usr/local/qmailanalog/bin/matchup: syntax error near
 unexpected token `Sorry,_I_couldn't_find_any_host_by_that_name._(#'
 /usr/local/qmailanalog/bin/matchup:
 /usr/local/qmailanalog/bin/matchup: line 735: `
 990967436.502499 delivery 1604: deferral:
 Sorry,_I_couldn't_find_any_host_by_that_name._(#4.1.2)/'
 Broken pipe


 John Scarborough
 TwinEngines Inc.
 404.522.4262
 http://www.twinengines.com
 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]




Title: Qmailanalog matchup error





I am trying to run matchup. I have cleaned the maillog as 
documented and generated a file to parse through matchup. 
Running matchup results in output like below .

Any help you  TIA!

/usr/local/qmailanalog/bin/matchup: 
[EMAIL PROTECTED]: No such file or directory
/usr/local/qmailanalog/bin/matchup: 990959401.508748: command 
not found
/usr/local/qmailanalog/bin/matchup: 990959401.510608: command 
not found
/usr/local/qmailanalog/bin/matchup: 990959401.555309: command 
not found
/usr/local/qmailanalog/bin/matchup: 990959401.558207: command 
not found
/usr/local/qmailanalog/bin/matchup: 990959401.559713: command 
not found
/usr/local/qmailanalog/bin/matchup: 990959420.577015: command 
not found
/usr/local/qmailanalog/bin/matchup: 990959420.578531: command 
not found
/usr/local/qmailanalog/bin/matchup: syntax error near 
unexpected token `Sorry,_I_couldn't_find_any_host_by_that_name._(#'
/usr/local/qmailanalog/bin/matchup: 
/usr/local/qmailanalog/bin/matchup: line 735: ` 
990967436.502499 delivery 1604: deferral: 
Sorry,_I_couldn't_find_any_host_by_that_name._(#4.1.2)/'
Broken pipe


John Scarborough
TwinEngines Inc.
404.522.4262
http://www.twinengines.com
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 
 







Re: Cann't get qmail to start properly

2001-04-04 Thread Jeff_D_Sweeten

I'm positive this has to be something simple, I just cann't see it.  I've
researched the archives and documentation to no avail.

tcpserver accepts the connection and qmail places the mail in
/opt/qmail/queue/todo (yes I compiled qmail to use opt in place of var) and then
it just sits there.   Fot the life of me I can't figure out why qmail-smtpd
dosen't spawn the next process.

Everthing worked fine back when I used inetd.conf, but I now want to add ORBS
blcking and have to switch to tcpserver.

Running Solaris 2.6

Starup is /etc/rc2.d/S88qmail;
# cat /etc/rc2.d/S88qmail
#!/bin/sh
#

#
# Startup for Qmail
#
# /usr/local/bin/rblsmtpd -rrbl.maps.vix.com \
# /usr/local/bin/rblsmtpd -rdul.maps.vix.com \

case "$1" in
'start')
#/usr/local/bin/supervise /opt/qmail/supervise/tcpserver-qmail-smtpd
  /usr/local/bin/tcpserver -c 10 -u 103 -g 101 \
  -x /etc/tcprules.d/qmail-smtpd.cdb \
  0 smtp \
  /opt/qmail/bin/qmail-smtpd 21 | \
  /opt/qmail/bin/splogger qmail 

ps -ef provides the following;
# ps -ef
 UID   PID  PPID  CSTIME TTY  TIME CMD
root 0 0  0 14:59:59 ?0:01 sched
root 1 0  0 14:59:59 ?0:00 /etc/init -
root 2 0  0 14:59:59 ?0:00 pageout
root 3 0  0 14:59:59 ?0:02 fsflush
root   141   138  0 15:00:33 ?0:00 /usr/lib/saf/ttymon
root   132 1  0 15:00:31 ?0:00 /usr/lib/utmpd
root   138 1  0 15:00:33 ?0:00 /usr/lib/saf/sac -t 300
root   213 1  0 15:27:02 console  0:00 /usr/lib/saf/ttymon -g -h -p
qmail-test console login:  -T sun -d /dev/console
root   217   215  0 15:32:58 pts/00:00 -sh
root   124 1  0 15:00:31 ?0:00 /opt/qmail/bin/splogger qmail
root   105 1  0 15:00:29 ?0:00 /usr/sbin/inetd -s
  qmaild   125   124  0 15:00:31 ?0:00 /usr/local/bin/tcpserver -c 10 -u
 103 -g 101 -x /etc/tcprules.d/qmail-smtpd.cdb
root   122 1  0 15:00:31 ?0:00 /usr/sbin/cron
root   215   105  0 15:32:58 ?0:00 in.telnetd
root   282   217  0 16:15:44 pts/00:00 ps -ef

qmail-showctl;
# qmail-showctl
qmail home directory: /opt/qmail.
user-ext delimiter: -.
paternalism (in decimal): 2.
silent concurrency limit: 255.
subdirectory split: 63.
user ids: 102, 103, 104, 0, 105, 106, 107, 108.
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 qmail-test.aon.com.

concurrencylocal: (Default.) Local concurrency is 10.

concurrencyremote: (Default.) Remote concurrency is 20.

databytes: SMTP DATA limit is 1024 bytes.

defaultdomain: Default domain name is aon.com.

defaulthost: Default host name is qmail-test.aon.com.

doublebouncehost: (Default.) 2B recipient host: qmail-test.aon.com.

doublebounceto: (Default.) 2B recipient user: postmaster.

envnoathost: (Default.) Presumed domain name is qmail-test.aon.com.

helohost: (Default.) SMTP client HELO host name is qmail-test.aon.com.

idhost: (Default.) Message-ID host name is qmail-test.aon.com.

localiphost: (Default.) Local IP address becomes qmail-test.aon.com.

locals:
Messages for localhost are delivered locally.
Messages for smtp.aon.com are delivered locally.
Messages for smtp02.aon.com are delivered locally.
Messages for amtp01.aon.com are delivered locally.

me: My name is qmail-test.aon.com.

percenthack: (Default.) The percent hack is not allowed.

plusdomain: (Default.) Plus domain name is qmail-test.aon.com.

qmqpservers: (Default.) No QMQP servers.
queuelifetime: (Default.) Message lifetime in the queue is 604800 seconds.

rcpthosts:
SMTP clients may send messages to recipients at aon.com.

morercpthosts: (Default.) No effect.

morercpthosts.cdb: (Default.) No effect.

smtpgreeting: (Default.) SMTP greeting: 220 qmail-test.aon.com.

smtproutes:
SMTP route: aon.com:smtp02.aon.com

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.





Modified 5.3.4 error

2001-03-29 Thread Jeff_D_Sweeten

Does anyone out there have a patch for inserting the databytes control field in
the #5.3.4 error.  Management doesn't wnat to block huge mails unless we tell
the sender what our max is.

Jeff Sweeten
Aon Corp.