qmail Digest 1 Nov 2000 11:00:00 -0000 Issue 1171
Topics (messages 51391 through 51434):
Re: Blocked pipe to qmail-queue
51391 by: Greg Cope
Return receipt
51392 by: Enrique
51393 by: OK 2 NET - Andr� Paulsberg
51394 by: Enrique
51410 by: Andy Bradford
51415 by: Brett Randall
51416 by: Enrique
51417 by: Jason Haar
51419 by: Daniel Augusto Fernandes
X-EnvelopeTo and forwarding
51395 by: Tristan Graham
51397 by: Magnus Bodin
51400 by: Tristan Graham
Delivery report...
51396 by: Daniel POGAC
51398 by: Frank Tegtmeyer
Re: Can't get POP3 Authorisation to work
51399 by: Howard Miller
51403 by: Howard Miller
51404 by: Howard Miller
51405 by: Howard Miller
51409 by: Tim Hunter
Problems to get messages in Maildir
51401 by: Schwarz Hans-Juergen
QRECEIPT
51402 by: Daniel POGAC
Re: smtp auth
51406 by: Chris Garrigues
51420 by: Chris Garrigues
Wildcard MX Obsolescence
51407 by: best.atoka-software.com
51412 by: Aaron L. Meehan
51421 by: best.atoka-software.com
51423 by: Peter Green
51429 by: Allen Wayne Best
Please help! I just can't figure it out.
51408 by: Mike Jackson
qmail + mysql
51411 by: Sebastian Wolfgarten
Re: Forward and Reply-To field
51413 by: Kai MacTane
Logging Message-ID:s in conjuction with delivery log lines?
51414 by: Magnus Bodin
51428 by: Markus Stumpf
qmail+mysql problem
51418 by: Sebastian Wolfgarten
alias
51422 by: Tomy
51431 by: David Dyer-Bennet
Re: high performance configs [was: Blocked pipe to qmail-queue]
51424 by: Jeff Mayzurk
.forward VS .qmail ?
51425 by: Mr.F
Behind firewall?
51426 by: Boyd Kelly
51427 by: Anthony Abby
unable to append to bounce messsage; HELP!(#2 settings)
51430 by: srl.metronet.com
Serialmail bounce messages
51432 by: brian.wilkinson.bt.com
dot-qmail
51433 by: Alan Chung
how do I install the qmail-virusscanner
51434 by: Ruprecht Helms
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]
----------------------------------------------------------------------
Jeff Mayzurk wrote:
>
> >On Tue, Oct 31, 2000 at 12:02:55AM +0100, Peter van Dijk wrote:
> >>DESCRIPTION
> >> qmail-queue reads a mail message from descriptor 0. It
> >> then reads envelope information from descriptor 1. It
> >> places the message into the outgoing queue for future
> >> delivery by qmail-send.
> >
> >Yeah, I read through that and while it implies that you terminate the
> >session by doing a close, it doesn't say that. It could, for example,
> >terminate it by a line consisting only of '.'...
> >
> >I'd change it to read:
> >
> >qmail-queue reads a message from descriptor 0, terminated by a close().
> >[...]
> >
>
> It also doesn't state the requirement that these operations must be
> serialized. Yes, the implication is there, but it's hardly what I'd call
> clear.
>
> Beter yet:
>
> "qmail-queue reads a message from descriptor 0. After EOF is received
> on descriptor 0, it reads envelope information from descriptor 1."
>
> By the way, does anyone have any interest in comparing notes on really high
> volume qmail configs? I'm looking for performance in the range of 200-250k
> remote deliveries per hour. We're halfway there with relatively few
> modifications on a modest dual-processor Sun. Before we really start digging
> into the code (or throwing more hardware at it), I'd like to hear from others
> who are dealing with similar volumes.
I've a similar issue (high performance required).
We deceided to go for multiple smallish intel boxes due to cost for
emails per hour ratios work in favour of intel on Linux (or FreeBSD but
thats a different flame ;-).
Lirking on this list I've seen people achieve between 30k to 150k and
hour. The average appears to be 50k an hour.
If bandwidth is not an issue then next bottle neck is the queue and disk
speed. As far as a I can see once you've moved from a simple DISK, you
can either:
a) Avoide the queue and talk direct to qmail-remote (and take care of
bounces / process mgt yourself).
This appears to be where people are getting above 100k and hour.
b) Buy lots of fast disks - RAID 0+1 (due to write performance RAID 5
appears a bad idea).
On SUN this gets expensive !
c) Some suggest RAM disks / Flash DISKS.
Is it Russ or Ken Jones has used Flash disks for this ?!? can't
rememeber.
If anyone has any hard info / experience here. I would be interested.
If you've any nice patches I would be very interested - but my spin on
the issue is KISS - i.e we will scale by adding small nodes - not
expensive boxen, and also going with simple set-ups for the sanity of
the people whom will run this.
I would be very instered in anyone thoughts on theses issues.
Regards
Greg Cope
>
> Thanks,
>
> -Jeff
Hi.
Qmail doesn't support "return receipt". Any solution for this?.
Thank's.
--
Enrique Rodr�guez
> Qmail doesn't support "return receipt". Any solution for this?.
I'm pretty sure you are confusing "Reply-To:" with "Return-Path:",
"Return-Path:" also known as envelope sender is used as the
return address/receipt on "all" mailservers including QMAIL.
"Reply-To:" is used by E-Mail clients when the user presses his REPLY button,
and should under NO circumstances be supported by the mailserver.
MVH Andr� Paulsberg
"OK 2 NET - Andr� Paulsberg" wrote:
>
> > Qmail doesn't support "return receipt". Any solution for this?.
>
> I'm pretty sure you are confusing "Reply-To:" with "Return-Path:",
> "Return-Path:" also known as envelope sender is used as the
> return address/receipt on "all" mailservers including QMAIL.
>
> "Reply-To:" is used by E-Mail clients when the user presses his REPLY button,
> and should under NO circumstances be supported by the mailserver.
>
> MVH Andr� Paulsberg
Thanks for you answer, maybe i have expresed bad.
I want use the features on my mail client (Netscape Communicator 4.61)
"Request return receipt" when i send a email, on my mail server (QMAIL).
But when i send a email whith these features to on, i don't receive
confirmation after i read these email.
QMAIL dosen't support send's confirmation, how can resolve these?. Exist
any patch?
Thanks again.
--
Enrique Rodr�guez
On Tue, 31 Oct 2000 12:28:09 +0100, Enrique wrote:
> Qmail doesn't support "return receipt". Any solution for this?.
Return receipt is not at all a function of the underlying MTA. All you
really need is to include a Disposition-Notification-To header in every
outgoing mail with the address that you want it to go to. This has
nothing to do with qmail, but it has everything to do with the client
you are using.
Andy
>>>>> "Andy" == Andy Bradford <[EMAIL PROTECTED]> writes:
> On Tue, 31 Oct 2000 12:28:09 +0100, Enrique wrote:
> Return receipt is not at all a function of the underlying MTA. All
> you really need is to include a Disposition-Notification-To header
> in every outgoing mail with the address that you want it to go to.
> This has nothing to do with qmail, but it has everything to do with
> the client you are using.
You may be interested to know (but not really care) that MS Exchange
and Lotus Notes are two MTAs I have had to work with that both modify
return receipt. Now they are both corporate e-mail systems and are
designed to do a lot more than just deliver mail (albeit not as good
as some would hope), but still, the MTA definitely has the power to
modify return receipts in both directions, and in these two cases at
least, it does.
Brett.
--
"At the source of every error which is blamed on the computer you will
find at least two human errors, including the error of blaming it on the
computer.
- Anonymous
Thaks, I know you said but the answer don't respond my question.
I have do this try.
I have send a email with netscape comunnicator 4.61 and i have put
"Request return receipt" to on. I have send these email over a sendmail
server, and when i received this email, i have been questioned if i want
replay confirmation.
If i do the same but over a qmail server, when i receive the email i
don't receive these question.
Do you understan me?
Thanks in advance.
Kai MacTane wrote:
>
> At 10/31/00 05:08 AM , Enrique wrote:
> >
> >I want use the features on my mail client (Netscape Communicator 4.61)
> >"Request return receipt" when i send a email, on my mail server (QMAIL).
> >But when i send a email whith these features to on, i don't receive
> >confirmation after i read these email.
>
> That is because this feature is supported by mail *clients* (such as
> Netscape, Outlook, Eudora, Pine, Pegasus, etc.), not the underlying mail
> *server* (Qmail and similar programs).
>
> I use Eudora, and when I receive a message with Return Receipt, I see a
> small dialog box saying:
>
> The sender of this message has requested a notification
> that you have seen this message. Send notification?
>
> [Now] [Later] [Never] [Help]
>
> I usually press the "Never" button. If you're trying to test this out, you
> might want to make sure that the user on the other end will press a button
> that will acknowledge the Return Receipt.
>
> Also, some mail clients don't understand Return Receipt at all, and so
> essentially "throw away" that information.
>
> --Kai MacTane
> ----------------------------------------------------------------------
> "Three o'clock in the morning/It's quiet and there's no-one around,
> Just the bang and the clatter/As an angel runs to ground,
> Just the bang and the clatter/As an angel hits the ground."
> --U2,
> "Stay (Faraway, So
> Close)"
--
Enrique Rodr�guez L�zaro
Dpo. T�cnico Xpress
Avd. P�rez Gald�s, 13 9�
Valencia - 46007
On Tue, Oct 31, 2000 at 11:05:17AM -0700, Andy Bradford wrote:
> On Tue, 31 Oct 2000 12:28:09 +0100, Enrique wrote:
>
> > Qmail doesn't support "return receipt". Any solution for this?.
>
> Return receipt is not at all a function of the underlying MTA. All you
Er - yes it is... Return-receipts in Netscape refer to Deliver-receipts and
Read-receipts (what I think you were refering to). Netscape and other MUAs
expect MTAs to support DSN for delivery-receipts - something Qmail does not
support.
--
Cheers
Jason Haar
Unix/Special Projects, Trimble NZ
Phone: +64 3 9635 377 Fax: +64 3 9635 417
Enrique wrote:
>
> Thaks, I know you said but the answer don't respond my question.
>
> I have do this try.
>
> I have send a email with netscape comunnicator 4.61 and i have put
> "Request return receipt" to on. I have send these email over a sendmail
> server, and when i received this email, i have been questioned if i want
> replay confirmation.
>
> If i do the same but over a qmail server, when i receive the email i
> don't receive these question.
>
> Do you understan me?
>
> Thanks in advance.
>
> .
> .
> .
I think what you're trying to do is related to DSN and MDN notification.
DSN is something like:
Original-Recipient: rfc822;[EMAIL PROTECTED]
Final-Recipient: RFC822; [EMAIL PROTECTED]
Action: relayed (to non-DSN-aware mailer)
Status: 2.0.0
Remote-MTA: DNS; mail.xxxx.com.br
Diagnostic-Code: SMTP; 250 OK <[EMAIL PROTECTED]>... Recipient ok
Last-Attempt-Date: Mon, 30 Oct 2000 20:43:03 -0200
And MDN is in the message headers like:
Disposition-Notification-To: Daniel Augusto Fernandes
<[EMAIL PROTECTED]>
--------------------------------------------------------------------
Daniel Augusto Fernandes (DAF tm) [EMAIL PROTECTED]
GCSNet http://www.gcsnet.com.br/
--------------------------------------------------------------------
Se voc� n�o encontra
o sentido das coisas
� porque este n�o
se encontra, se cria.
Antoine Saint-Exup�ry
Hi,
I am having some problems sorting out forwarding for virtual domains - What
is the correct way to set this up ? I have tried using fastforward, but
this rewrites the X-EnvelopeTo field to the 'real' recipients address which
obviously has certain effects that are undesireable. The envelope needs to
remain as the original to address...
Is there a way to implement this easily ?
Many Thanks,
Tristan Graham
On Tue, Oct 31, 2000 at 12:14:15PM +0000, Tristan Graham wrote:
> Hi,
>
> I am having some problems sorting out forwarding for virtual domains - What
> is the correct way to set this up ? I have tried using fastforward, but
> this rewrites the X-EnvelopeTo field to the 'real' recipients address which
> obviously has certain effects that are undesireable. The envelope needs to
> remain as the original to address...
If you forward, the envelope will of course change.
Otherwise the mail wouldn't be forwarded.
/magnus
--
http://x42.com/
Yes, but... On Sendmail, the headers for a virtual domain with forwarding
look as follows: (I have marked the line in question with asterisks). This
test forwards mail for [EMAIL PROTECTED] -> [EMAIL PROTECTED]
Received: by tele1 (mbox tristan)
(mipop (v1.31j) Tue Oct 31 13:39:45 2000)
X-From_: [EMAIL PROTECTED] Tue Oct 31 13:39:43 2000
Return-Path: <root>
Received: (from root@localhost)
by tele1.inweb.co.uk (8.8.8/8.8.5) id NAA01209
for [EMAIL PROTECTED]; Tue, 31 Oct 2000 13:39:43 GMT
Date: Tue, 31 Oct 2000 13:39:43 GMT
From: root <[EMAIL PROTECTED]>
*****X-EnvelopeTo: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: test
which works fine, but the recieved headers from qmail look like this:
Received: by tele1 (mbox tristan)
(mipop (v1.31j) Tue Oct 31 13:52:14 2000)
X-From_: [EMAIL PROTECTED] Tue Oct 31 13:52:10 2000
Return-Path: <[EMAIL PROTECTED]>
Received: from tele6.inweb.co.uk ([EMAIL PROTECTED] [213.210.6.2])
by tele1.inweb.co.uk (8.8.8/8.8.5) with SMTP id NAA03618
for <[EMAIL PROTECTED]>; Tue, 31 Oct 2000 13:52:10 GMT
From: [EMAIL PROTECTED]
*****X-EnvelopeTo: <[EMAIL PROTECTED]>
Received: (qmail 28103 invoked by alias); 31 Oct 2000 13:58:38 -0000
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 28099 invoked by uid 0); 31 Oct 2000 13:58:38 -0000
Date: 31 Oct 2000 13:58:38 -0000
Message-ID: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: test
I think that this will severely impair some of our mailing lists and other
intermediates.
Tris.
At 13:52 31/10/2000 +0100, Magnus Bodin wrote:
>On Tue, Oct 31, 2000 at 12:14:15PM +0000, Tristan Graham wrote:
> > Hi,
> >
> > I am having some problems sorting out forwarding for virtual domains -
> What
> > is the correct way to set this up ? I have tried using fastforward, but
> > this rewrites the X-EnvelopeTo field to the 'real' recipients address
> which
> > obviously has certain effects that are undesireable. The envelope needs to
> > remain as the original to address...
>
>If you forward, the envelope will of course change.
>Otherwise the mail wouldn't be forwarded.
>
>/magnus
>
>--
>http://x42.com/
I have problem with delivery report in Outlook ...
Outlook have cheking box which is checked i receive message about deviver
my mail to the remote or local SMTP server.
It is not working under Qmail SMTP server. In log i can monitoriong
delivering message but what chace have a simply user ???
Daniel POGAČ
Tech. Support
TatraSoft Group s.r.o
Sibírska 4
83102 Bratislava
tel: +421-7-55574033
fax: +421-7-55566385
[EMAIL PROTECTED]
> Outlook have cheking box which is checked i receive message about deviver
> my mail to the remote or local SMTP server.
This turns on Receipt-To: I think. There is no guaranteed way to get a
delivery notification.
If it absolutely needed ask your mail partner to send a short answer. This
establishes a simple end to end protocol.
Regards, Frank
Sorry, I'm very new to setting mail servers and I'm not sure what you mean!
Where do I put these settings? I don't really understand what is meant by a
virtual domain in this context.
My goal is to pruduce a mail server for a windows 98 network. All my users
will access by SMTP and POP3 and will not have IDs on the unix box. I
assume this makes them virtual users (yes?). I am having a lot of trouble
understanding how to do this. Any help at all will be appreciated.
Howard
At 11:13 31/10/00 +0100, you wrote:
>Hello Howard,
>
>Tuesday, October 31, 2000, 6:27:30 PM, you wrote:
>
> > I have installed qmail and it seems to more or less work.
>
> > I can connect to POP3 but my usernames/passwords are never authorised.
> I am
> > using the setup as described in the FAQ.
>
>If you run a virtuell domain you probably have to set the user login
>format like user%domain.com
>
>Hans-Juergen
Errr... thanks,
BUT I don't have any executables call "vadduser" or "vadddomain"!!!
Where do I find these? Does this work with the password checking program
that comes with the standard download of wmail?
Thanks again.
At 09:25 31/10/00 -0500, you wrote:
>If you've run
>vadduser some_user
>then it asked you for a password and that's how you will authenticate.
>user: user
>pass: pass
>
>If you've run
>vadddomain some_domain
>vadduser some_user@some_domain
>
>then you authenticate as follows:
>user: some_user%some_domain
>pass: pass
>
>Make sense?
>
>-----Original Messag
>e-----
>From: Howard Miller <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>Date: Tuesday, October 31, 2000 8:28 AM
>Subject: Re: Can't get POP3 Authorisation to work
>
>
> >Sorry, I'm very new to setting mail servers and I'm not sure what you mean!
> >
> >Where do I put these settings? I don't really understand what is meant by a
> >virtual domain in this context.
> >
> >My goal is to pruduce a mail server for a windows 98 network. All my users
> >will access by SMTP and POP3 and will not have IDs on the unix box. I
> >assume this makes them virtual users (yes?). I am having a lot of trouble
> >understanding how to do this. Any help at all will be appreciated.
> >
> >Howard
> >
> >At 11:13 31/10/00 +0100, you wrote:
> >>Hello Howard,
> >>
> >>Tuesday, October 31, 2000, 6:27:30 PM, you wrote:
> >>
> >> > I have installed qmail and it seems to more or less work.
> >>
> >> > I can connect to POP3 but my usernames/passwords are never authorised.
> >> I am
> >> > using the setup as described in the FAQ.
> >>
> >>If you run a virtuell domain you probably have to set the user login
> >>format like user%domain.com
> >>
> >>Hans-Juergen
> >
I'm sorry... I'm losing the plot here completely.
I got vpopmail. Installed it no problems, and off we go...
added a user 'fred' with password 'pass' using vadduser.. worked/
tried POP3 access from a PC on the network....made no difference
whatsoever, password/username incorrect still.
What might I be doing wrong?
I frankly don't understand this virtual domain thing, and I have been
reading about it for days. If you can indulge me...
We currently have a mailserver called (names changed to protect the
innocent) mail.somedomain.com. This machine has (a) problems and (b) no
documentation and needs to go. So I set up a machine at
test.somedomain.com. I installed qmail and can send mail from the new
machine to the old and back again, using an ordinary user on the new
machine to an arbitrary user on the old. I do this using the ordinary mail
program, it doesn't work with these "Maildir" things, something else that
isn't explained very well.
I won't be using local users on test.somedomain.com, users will connect
using SMTP and POP3 and don't need to have IDs on the linux box. I will
want their usernames to be [EMAIL PROTECTED]
What is the easiest way to do this? I have been at this for a week, and am
no further forward. I am ceasing to be impressed with qmail as it is FAR
too hard to set up. Win2000 and Exchange will have to be the answer if I
can't get this working very soon.
Cheers... Howard
PS Sorry if I sound grumpy... I just need to get this working and its like
hitting my head of a brick wall. Is there no decent documentation for this
stuff?
At 11:00 31/10/00 -0500, you wrote:
>Oh...you need to get the vpopmail package to do virtuals. Really, it's
>great.
>
>-----Original Message-----
>From: Howard Miller <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>Date: Tuesday, October 31, 2000 10:30 AM
>Subject: Re: Can't get POP3 Authorisation to work
>
>
> >Errr... thanks,
> >
> >BUT I don't have any executables call "vadduser" or "vadddomain"!!!
> >
> >Where do I find these? Does this work with the password checking program
> >that comes with the standard download of wmail?
> >
> >Thanks again.
> >
> >At 09:25 31/10/00 -0500, you wrote:
> >>If you've run
> >>vadduser some_user
> >>then it asked you for a password and that's how you will authenticate.
> >>user: user
> >>pass: pass
> >>
> >>If you've run
> >>vadddomain some_domain
> >>vadduser some_user@some_domain
> >>
> >>then you authenticate as follows:
> >>user: some_user%some_domain
> >>pass: pass
> >>
> >>Make sense?
> >>
> >>-----Original Messag
> >>e-----
> >>From: Howard Miller <[EMAIL PROTECTED]>
> >>To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> >>Date: Tuesday, October 31, 2000 8:28 AM
> >>Subject: Re: Can't get POP3 Authorisation to work
> >>
> >>
> >> >Sorry, I'm very new to setting mail servers and I'm not sure what you
>mean!
> >> >
> >> >Where do I put these settings? I don't really understand what is meant
>by a
> >> >virtual domain in this context.
> >> >
> >> >My goal is to pruduce a mail server for a windows 98 network. All my
>users
> >> >will access by SMTP and POP3 and will not have IDs on the unix box. I
> >> >assume this makes them virtual users (yes?). I am having a lot of
>trouble
> >> >understanding how to do this. Any help at all will be appreciated.
> >> >
> >> >Howard
> >> >
> >> >At 11:13 31/10/00 +0100, you wrote:
> >> >>Hello Howard,
> >> >>
> >> >>Tuesday, October 31, 2000, 6:27:30 PM, you wrote:
> >> >>
> >> >> > I have installed qmail and it seems to more or less work.
> >> >>
> >> >> > I can connect to POP3 but my usernames/passwords are never
>authorised.
> >> >> I am
> >> >> > using the setup as described in the FAQ.
> >> >>
> >> >>If you run a virtuell domain you probably have to set the user login
> >> >>format like user%domain.com
> >> >>
> >> >>Hans-Juergen
> >> >
> >
Yes, I tried [EMAIL PROTECTED] and [EMAIL PROTECTED], neither worked.
Can anybody explain to me what is supposed to be happening. Should I use
checkpassword or vcheckpw (or whatever it is), and if so where do these
programs actually get the authorisation information from. AND what do all
these files in qmail/control DO? PLEASE, PLEASE don't tell me to stick
this in there or that in the other, how does it work and I will figure it
out for myself.
If I want' to use POP3 do I use Mailbox or Maildir? Does it matter? Can I
use either? HOW DOES IT WORK? It can't be hard, surely?????
Yours, very frustrated
Howard
At 10:27 31/10/00 -0600, you wrote:
>Just to try the simple stuff first did you type in [EMAIL PROTECTED] and then
>the password ?
>
>
>
>Rick Harris
>UNIX Administrator
>Internet Global/Telares
>[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>
>"In a time of insanity, let a madman lead the way"
>
>
>
>-----Original Message-----
>From: Howard Miller [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, October 31, 2000 6:15 PM
>To: [EMAIL PROTECTED]
>Subject: Re: Can't get POP3 Authorisation to work
>
>
>I'm sorry... I'm losing the plot here completely.
>
>I got vpopmail. Installed it no problems, and off we go...
>
>added a user 'fred' with password 'pass' using vadduser.. worked/
>
>tried POP3 access from a PC on the network....made no difference
>whatsoever, password/username incorrect still.
>
>What might I be doing wrong?
>
>I frankly don't understand this virtual domain thing, and I have been
>reading about it for days. If you can indulge me...
>
>We currently have a mailserver called (names changed to protect the
>innocent) mail.somedomain.com. This machine has (a) problems and (b) no
>documentation and needs to go. So I set up a machine at
>test.somedomain.com. I installed qmail and can send mail from the new
>machine to the old and back again, using an ordinary user on the new
>machine to an arbitrary user on the old. I do this using the ordinary mail
>program, it doesn't work with these "Maildir" things, something else that
>isn't explained very well.
>
>I won't be using local users on test.somedomain.com, users will connect
>using SMTP and POP3 and don't need to have IDs on the linux box. I will
>want their usernames to be [EMAIL PROTECTED]
>
>What is the easiest way to do this? I have been at this for a week, and am
>no further forward. I am ceasing to be impressed with qmail as it is FAR
>too hard to set up. Win2000 and Exchange will have to be the answer if I
>can't get this working very soon.
>
>Cheers... Howard
>PS Sorry if I sound grumpy... I just need to get this working and its like
>hitting my head of a brick wall. Is there no decent documentation for this
>stuff?
>
>
>At 11:00 31/10/00 -0500, you wrote:
> >Oh...you need to get the vpopmail package to do virtuals. Really, it's
> >great.
> >
> >-----Original Message-----
> >From: Howard Miller <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> >Date: Tuesday, October 31, 2000 10:30 AM
> >Subject: Re: Can't get POP3 Authorisation to work
> >
> >
> > >Errr... thanks,
> > >
> > >BUT I don't have any executables call "vadduser" or "vadddomain"!!!
> > >
> > >Where do I find these? Does this work with the password checking program
> > >that comes with the standard download of wmail?
> > >
> > >Thanks again.
> > >
> > >At 09:25 31/10/00 -0500, you wrote:
> > >>If you've run
> > >>vadduser some_user
> > >>then it asked you for a password and that's how you will authenticate.
> > >>user: user
> > >>pass: pass
> > >>
> > >>If you've run
> > >>vadddomain some_domain
> > >>vadduser some_user@some_domain
> > >>
> > >>then you authenticate as follows:
> > >>user: some_user%some_domain
> > >>pass: pass
> > >>
> > >>Make sense?
> > >>
> > >>-----Original Messag
> > >>e-----
> > >>From: Howard Miller <[EMAIL PROTECTED]>
> > >>To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> > >>Date: Tuesday, October 31, 2000 8:28 AM
> > >>Subject: Re: Can't get POP3 Authorisation to work
> > >>
> > >>
> > >> >Sorry, I'm very new to setting mail servers and I'm not sure what you
> >mean!
> > >> >
> > >> >Where do I put these settings? I don't really understand what is meant
> >by a
> > >> >virtual domain in this context.
> > >> >
> > >> >My goal is to pruduce a mail server for a windows 98 network. All my
> >users
> > >> >will access by SMTP and POP3 and will not have IDs on the unix box. I
> > >> >assume this makes them virtual users (yes?). I am having a lot of
> >trouble
> > >> >understanding how to do this. Any help at all will be appreciated.
> > >> >
> > >> >Howard
> > >> >
> > >> >At 11:13 31/10/00 +0100, you wrote:
> > >> >>Hello Howard,
> > >> >>
> > >> >>Tuesday, October 31, 2000, 6:27:30 PM, you wrote:
> > >> >>
> > >> >> > I have installed qmail and it seems to more or less work.
> > >> >>
> > >> >> > I can connect to POP3 but my usernames/passwords are never
> >authorised.
> > >> >> I am
> > >> >> > using the setup as described in the FAQ.
> > >> >>
> > >> >>If you run a virtuell domain you probably have to set the user login
> > >> >>format like user%domain.com
> > >> >>
> > >> >>Hans-Juergen
> > >> >
> > >
To make sure we are checking all the stops can you please post unedited:
1) the line you use to start your pop3 server
2) the results of a telnet to port 110 including username/password
3) the log of that pop3 session
Thanks,
Tim
-----Original Message-----
From: Howard Miller [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 31, 2000 7:39 PM
To: [EMAIL PROTECTED]
Subject: RE: Can't get POP3 Authorisation to work
Yes, I tried [EMAIL PROTECTED] and [EMAIL PROTECTED], neither
worked.
Can anybody explain to me what is supposed to be happening. Should I use
checkpassword or vcheckpw (or whatever it is), and if so where do these
programs actually get the authorisation information from. AND what do all
these files in qmail/control DO? PLEASE, PLEASE don't tell me to stick
this in there or that in the other, how does it work and I will figure it
out for myself.
If I want' to use POP3 do I use Mailbox or Maildir? Does it matter? Can I
use either? HOW DOES IT WORK? It can't be hard, surely?????
Yours, very frustrated
Howard
At 10:27 31/10/00 -0600, you wrote:
>Just to try the simple stuff first did you type in [EMAIL PROTECTED] and then
>the password ?
>
>
>
>Rick Harris
>UNIX Administrator
>Internet Global/Telares
>[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>
>"In a time of insanity, let a madman lead the way"
>
>
>
>-----Original Message-----
>From: Howard Miller [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, October 31, 2000 6:15 PM
>To: [EMAIL PROTECTED]
>Subject: Re: Can't get POP3 Authorisation to work
>
>
>I'm sorry... I'm losing the plot here completely.
>
>I got vpopmail. Installed it no problems, and off we go...
>
>added a user 'fred' with password 'pass' using vadduser.. worked/
>
>tried POP3 access from a PC on the network....made no difference
>whatsoever, password/username incorrect still.
>
>What might I be doing wrong?
>
>I frankly don't understand this virtual domain thing, and I have been
>reading about it for days. If you can indulge me...
>
>We currently have a mailserver called (names changed to protect the
>innocent) mail.somedomain.com. This machine has (a) problems and (b) no
>documentation and needs to go. So I set up a machine at
>test.somedomain.com. I installed qmail and can send mail from the new
>machine to the old and back again, using an ordinary user on the new
>machine to an arbitrary user on the old. I do this using the ordinary mail
>program, it doesn't work with these "Maildir" things, something else that
>isn't explained very well.
>
>I won't be using local users on test.somedomain.com, users will connect
>using SMTP and POP3 and don't need to have IDs on the linux box. I will
>want their usernames to be [EMAIL PROTECTED]
>
>What is the easiest way to do this? I have been at this for a week, and am
>no further forward. I am ceasing to be impressed with qmail as it is FAR
>too hard to set up. Win2000 and Exchange will have to be the answer if I
>can't get this working very soon.
>
>Cheers... Howard
>PS Sorry if I sound grumpy... I just need to get this working and its like
>hitting my head of a brick wall. Is there no decent documentation for this
>stuff?
>
>
>At 11:00 31/10/00 -0500, you wrote:
> >Oh...you need to get the vpopmail package to do virtuals. Really, it's
> >great.
> >
> >-----Original Message-----
> >From: Howard Miller <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> >Date: Tuesday, October 31, 2000 10:30 AM
> >Subject: Re: Can't get POP3 Authorisation to work
> >
> >
> > >Errr... thanks,
> > >
> > >BUT I don't have any executables call "vadduser" or "vadddomain"!!!
> > >
> > >Where do I find these? Does this work with the password checking
program
> > >that comes with the standard download of wmail?
> > >
> > >Thanks again.
> > >
> > >At 09:25 31/10/00 -0500, you wrote:
> > >>If you've run
> > >>vadduser some_user
> > >>then it asked you for a password and that's how you will authenticate.
> > >>user: user
> > >>pass: pass
> > >>
> > >>If you've run
> > >>vadddomain some_domain
> > >>vadduser some_user@some_domain
> > >>
> > >>then you authenticate as follows:
> > >>user: some_user%some_domain
> > >>pass: pass
> > >>
> > >>Make sense?
> > >>
> > >>-----Original Messag
> > >>e-----
> > >>From: Howard Miller <[EMAIL PROTECTED]>
> > >>To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> > >>Date: Tuesday, October 31, 2000 8:28 AM
> > >>Subject: Re: Can't get POP3 Authorisation to work
> > >>
> > >>
> > >> >Sorry, I'm very new to setting mail servers and I'm not sure what
you
> >mean!
> > >> >
> > >> >Where do I put these settings? I don't really understand what is
meant
> >by a
> > >> >virtual domain in this context.
> > >> >
> > >> >My goal is to pruduce a mail server for a windows 98 network. All my
> >users
> > >> >will access by SMTP and POP3 and will not have IDs on the unix box.
I
> > >> >assume this makes them virtual users (yes?). I am having a lot of
> >trouble
> > >> >understanding how to do this. Any help at all will be appreciated.
> > >> >
> > >> >Howard
> > >> >
> > >> >At 11:13 31/10/00 +0100, you wrote:
> > >> >>Hello Howard,
> > >> >>
> > >> >>Tuesday, October 31, 2000, 6:27:30 PM, you wrote:
> > >> >>
> > >> >> > I have installed qmail and it seems to more or less work.
> > >> >>
> > >> >> > I can connect to POP3 but my usernames/passwords are never
> >authorised.
> > >> >> I am
> > >> >> > using the setup as described in the FAQ.
> > >> >>
> > >> >>If you run a virtuell domain you probably have to set the user
login
> > >> >>format like user%domain.com
> > >> >>
> > >> >>Hans-Juergen
> > >> >
> > >
Hello,
I�m running qmail 1.03 and vpopmail 4.9.4 everything works fine so
far but I still can�t get the messages for a user in the ./Maildir
they always get stucked in the queue. I checked every file and the
only point where I think there could be a mistake is the
../users/assign File wich looks like this:
+domain.com-:domain.com:508:103:/home/vpopmail/domains/domain.com:-::
.
I started qmail and vpopmail with the startup-scripts as described
in the vpopmail FAQ.
Normaly nothing should go wrong at that point, cause vpopmail
actually configures everything I need to receive messages. Is it
qmail-local or qmail-lspawn? The other
thing is that the authorisation to the Maildir is always working really slow.
So you got any ideas? I can�t find any more about it.
Viele Gruesse aus dem Allgaeu
Schwarz Hans-Juergen
--
HJS Internetdienste
Westerharter Weg 11
87700 Memmingen
Fon: 08331-901104
Fax: 08331-901105
Mail: [EMAIL PROTECTED]
Web: www.hjs.de
Do you any use qreceipt ??? From man pages i can't understand how it use.
Can you give me help how .qmail file in /home/ directory must look...
Thanks...
Daniel POGAČ
Tech. Support
TatraSoft Group s.r.o
Sibírska 4
83102 Bratislava
tel: +421-7-55574033
fax: +421-7-55566385
[EMAIL PROTECTED]
> From: Juan Calderon <[EMAIL PROTECTED]>
> Date: Mon, 30 Oct 2000 19:29:10 -0500
>
> hi guys. just a question.
>
> i've applied qmail-ldap-1.03-20000701.patch and it's working fine. i
> also have pop3 and imap working (courier-imap 1.2.1). Now i need to use
> SMTP AUTH so i can deal with roaming users.
> i've applied qmail-smtpd-auth-0.26, but i can't get it work. docs say
> that i need checkpassword and cmd5checkpw, but they don't user ldap.
> how can i make it work? does anybody has something like this?
>
> thanks in advance
Funny, I asked almost exactly the same question on the 26th...
I installed it last night and my netscape users complained this morning, so I
backed it out until I could test it properly.
Keep me apprised about anything you find and I'll do the same for you.
Chris
--
Chris Garrigues http://www.DeepEddy.Com/~cwg/
virCIO http://www.virCIO.Com
4314 Avenue C
Austin, TX 78751-3709 +1 512 374 0500
My email address is an experiment in SPAM elimination. For an
explanation of what we're doing, see http://www.DeepEddy.Com/tms.html
Nobody ever got fired for buying Microsoft,
but they could get fired for relying on Microsoft.
PGP signature
[ Added qmail-ldap list ]
> From: "Chris Garrigues" <[EMAIL PROTECTED]>
> Date: Tue, 31 Oct 2000 10:46:03 -0600
>
> > From: Juan Calderon <[EMAIL PROTECTED]>
> > Date: Mon, 30 Oct 2000 19:29:10 -0500
> >
> > hi guys. just a question.
> >
> > i've applied qmail-ldap-1.03-20000701.patch and it's working fine. i
> > also have pop3 and imap working (courier-imap 1.2.1). Now i need to use
> > SMTP AUTH so i can deal with roaming users.
> > i've applied qmail-smtpd-auth-0.26, but i can't get it work. docs say
> > that i need checkpassword and cmd5checkpw, but they don't user ldap.
> > how can i make it work? does anybody has something like this?
> >
> > thanks in advance
>
> Funny, I asked almost exactly the same question on the 26th...
>
> I installed it last night and my netscape users complained this morning, so I
> backed it out until I could test it properly.
>
> Keep me apprised about anything you find and I'll do the same for you.
Well, I've figured out at least part of my problem although I don't know what
to do about it.
>From QLDAPNEWS:
Created a new auth tool for pop3 and imap. The old checkpassword is not
needed anymore. The new programs are auth_pop and auth_imap.
To have the possibility to compare cleartextpasswords (password how are
stored clear text in ldap) define CLEARTEXTPASSWORD. Because this setting
is a security disaster it is normally off. All other modes (hashed MD4, MD5,
SHA and the standard DES crypt) are not affected.
I checked the date on my checkpassword executable and lo and behold, it dates
from April 21, well before I started working with LDAP.
So...what do I use instead of checkpassword?
I tried both auth_pop and auth_imap and in both cases, I get an out of memory
error written into the log (I have smtpd logging patches applied as well.)
Chris
--
Chris Garrigues http://www.DeepEddy.Com/~cwg/
virCIO http://www.virCIO.Com
4314 Avenue C
Austin, TX 78751-3709 +1 512 374 0500
My email address is an experiment in SPAM elimination. For an
explanation of what we're doing, see http://www.DeepEddy.Com/tms.html
Nobody ever got fired for buying Microsoft,
but they could get fired for relying on Microsoft.
PGP signature
hello:
i am a neophyte at installing qmail correctly. (please don't laugh too hard at my
questions!) :->
i am installing qmail on my linux 6.1 machine inside of the company i work for. it is
currently running sendmail that comes with redhat. the company has a policy of no
wildcard mx's. a "sendmail.cf" is provided to not use a wildcard mx. within that file
are the two lines that seem to pertinent (as i feebly understand sendmail!)
# Smart host
DSmail.server.domain.com
# Use this mailer to reach the Smart host
DNsmtp
# Restrict DNS to those domain only
CD
my question is how do i avoid the "wilcard mx" problem with qmail? whenever i attempt
a send to outside of my system using:
echo to: [EMAIL PROTECTED] | /var/qmail/bin/qmail-inject
i get a bounce like:
Hi. This is the qmail-send program at myclient.server.domain.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<[EMAIL PROTECTED]>:
1.2.3.4 does not like recipient.
Remote host said: 554 <myclient.server.domain.com[1.2.3.4]>: Client host rejected:
Will not relay via wildcard MX records - reference
http://www.server.domain.com/DNS/wildmx.html
Giving up on 1.2.3.4.
any ideas will be greatly appreciated.
regards,
allen wayne best, esq
[EMAIL PROTECTED]
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
> i am installing qmail on my linux 6.1 machine inside of the company
What is "linux 6.1?" (did you mean Redhat 6.1 by chance, hmm?). A
minor point, but be careful if you slip up like that on a list devoted
to linux.
> i work for. it is currently running sendmail that comes with
> redhat. the company has a policy of no wildcard mx's. a
> "sendmail.cf" is provided to not use a wildcard mx. within that file
> are the two lines that seem to pertinent (as i feebly understand
> sendmail!)
> # Smart host
> DSmail.server.domain.com
They might be even more pertinent if you had not decided to munge all
the useful data!
> my question is how do i avoid the "wilcard mx" problem with qmail?
> whenever i attempt a send to outside of my system using:
You are sending mail remotely from a qmail system to an alleged
sendmail system (I say alleged since you've again munged all useful
data, so I can't double-check), and the remote system is rejecting the
mail after the recipient is specified. Assuming that the remote
system is _not_ qmail, and I'm pretty sure it isn't, your problem has
absolutely nothing to do with qmail.
> <[EMAIL PROTECTED]>:
> 1.2.3.4 does not like recipient.
> Remote host said: 554 <myclient.server.domain.com[1.2.3.4]>: Client host rejected:
>Will not relay via wildcard MX records - reference
>http://www.server.domain.com/DNS/wildmx.html
> Giving up on 1.2.3.4.
atoka-software.com does not have any wildcard MXs. I'm pretty confused
as to what that mail server is thinking. I think some more info is
needed.
Aaron
>
> Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
> > i am installing qmail on my linux 6.1 machine inside of the company
>
> What is "linux 6.1?" (did you mean Redhat 6.1 by chance, hmm?). A
> minor point, but be careful if you slip up like that on a list devoted
> to linux.
apologies. yes. redhat 6.1
>
> > i work for. it is currently running sendmail that comes with
> > redhat. the company has a policy of no wildcard mx's. a
> > "sendmail.cf" is provided to not use a wildcard mx. within that file
> > are the two lines that seem to pertinent (as i feebly understand
> > sendmail!)
>
> > # Smart host
> > DSmail.server.domain.com
> > # Use this mailer to reach the Smart host
> > DNsmtp
> > # Restrict DNS to those domain only
> > CD
>
> They might be even more pertinent if you had not decided to munge all
> the useful data!
?munge? could you explain what this means. i am new at this (qmail, and
this mailing list, so far asking for info...)
>
> > my question is how do i avoid the "wilcard mx" problem with qmail?
> > whenever i attempt a send to outside of my system using:
>
> You are sending mail remotely from a qmail system to an alleged
> sendmail system (I say alleged since you've again munged all useful
> data, so I can't double-check), and the remote system is rejecting the
> mail after the recipient is specified. Assuming that the remote
> system is _not_ qmail, and I'm pretty sure it isn't, your problem has
> absolutely nothing to do with qmail.
yes, the remote system is a sendmail system. my machine also is
currently using sendmail. i want to migrate off that (as much as a
learning experience as any other reason).
when the company decided to not allow the wildcard mx's, my local
sendmail system had to change. and it looks like the new sendmail.cf
has the changes that i noted in the prior message.
>
> > <[EMAIL PROTECTED]>:
> > 1.2.3.4 does not like recipient.
> > Remote host said: 554 <myclient.server.domain.com[1.2.3.4]>: Client host rejected:
>Will not relay via wildcard MX records - reference
>http://www.server.domain.com/DNS/wildmx.html
> > Giving up on 1.2.3.4.
>
> atoka-software.com does not have any wildcard MXs. I'm pretty confused
> as to what that mail server is thinking. I think some more info is
> needed.
>
> Aaron
so far as i can determine, it is not that the receiving domain has
wildcard mx's; it is the dependence of the mail server on the local
machine that is somehow depending on a wildcard mx. (pardon me, i am
ignorant here! <s>) anyway, it does not matter where the destination
mailbox is (other than *.domain.com).
as i mentioned, it seems that the change is required on my machine,
as i had to change my sendmail.cf to fix the problem when using a
sendmail server on my machine. am i off base here?
again, thanks for your patience...
allen wayne best
[EMAIL PROTECTED]
also sprach best:
> > They might be even more pertinent if you had not decided to munge all
> > the useful data!
>
> ?munge? could you explain what this means. i am new at this (qmail, and
> this mailing list, so far asking for info...)
<http://www.tuxedo.org/~esr/jargon/html/entry/munge.html>. Basically, he
means that if you are going to ask for help with DNS, you shouldn't alter
domain information. If you need help with the atoka-software.com, then don't
say you need help with xxxxxxxxxxxxxxxx.com.
/pg
--
Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED]
---
"Many computer scientists have fallen into the trap of trying to define
languages like George Orwell's Newspeak, in which it is impossible to
think bad thoughts. What they end up doing is killing the creativity
of programming."
--- Larry Wall
On Tue, 31 Oct 2000, you wrote:
peter:
perhaps i am guilty of adding too much information.
> also sprach best:
> > > They might be even more pertinent if you had not decided to munge all
> > > the useful data!
> >
> > ?munge? could you explain what this means. i am new at this (qmail, and
> > this mailing list, so far asking for info...)
>
> <http://www.tuxedo.org/~esr/jargon/html/entry/munge.html>. Basically, he
> means that if you are going to ask for help with DNS, you shouldn't alter
> domain information. If you need help with the atoka-software.com, then don't
> say you need help with xxxxxxxxxxxxxxxx.com.
>
> /pg
> --
> Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED]
> ---
> "Many computer scientists have fallen into the trap of trying to define
> languages like George Orwell's Newspeak, in which it is impossible to
> think bad thoughts. What they end up doing is killing the creativity
> of programming."
> --- Larry Wall
i know that the problem is at my machine, and not on the remote email server. (
i xxx'd out the relevant things as i'm a contractor, and the company has very
specific policies of my using their name... i like to work, if you know what i
mean <s>)
anyway, i know it is at my machine as when to problem showed up under sendmail,
i checked internally, and was given the fix in the form of a sendmail.cf file
for my machine, not the remote server. so, naturally, i suspect the fix is
local for qmail as well.
since asking the original question, i have been reading further in "running
qmail" by richard blum. in the section on the smtproutes control file, it looks
like i should add a final line that says:
:mail.server.domain.com
it sounds like that line will automatically forward the mail to that server
when no prior lines in smtproutes match (and there will not be!)
does this sound reasonable?
--
regards,
allen wayne best, esq
Hello,
I hope this catches the interest of someone who can point me in the right
direction. I have a problem that is preventing me from converting from
sendmail to qmail. The problem is that I need to rewrite message headers and
smtp envelopes for all outgoing mail to something like [EMAIL PROTECTED],
regardless of whether users enter [EMAIL PROTECTED] or [EMAIL PROTECTED]
. Ok, now I need to be able to allow one user to do whatever he wants in
regards to his outgoing email addresses and I can not make him use
environment variables on his machine. Here is the setup of my system.
* qmail 1.03 with qmail-ldap patch
* all Maildirs owned by vmail:vmail
* Courier imap is the only way to read mail
* no logons to the machine by any users whatsoever, all username/passwords
are in the ldap directory
Somebody please help me! Reply by personal mail to [EMAIL PROTECTED] and to the
list if at all possible.
Thanks,
Mike
hi,
I have successfully set up qmail here.
Now I have patched qmail with this mysql patch,
no problems at all, the test to verify that
the connection between mysql and qmail works
(qmail-getpw username domain.tld) pretty fine.
But when I try to send a mail to a user it
does not work. See the logfiles:
973023765.349698 starting delivery 5: msg 492708 to local
@hostname.domain.tld
Oct 31 21:22:45 asterix qmail: 973023765.350128 status: local 1/10 remote
0/20
Oct 31 21:22:45 asterix qmail: 973023765.353740 delivery 5: success:
Oct 31 21:22:45 asterix qmail: 973023765.354152 status: local 0/10 remote
0/20
Oct 31 21:22:45 asterix qmail: 973023765.384631 end msg 492708
He does not report any success or failure reports. I turned the mysql
logs on but it seems as if qmail does not try to establish ANY connection
with mysql, although I have checked the sqlserver file (it's okay).
What could the problem might be? I have put the domain in my control
files and so on. And of course I copied the modified files /var/qmail/bin
;-)
Thanks
Sebastian
At 10/31/00 01:02 AM , Brett Randall wrote:
> > That's nice, but note also:
> > http://www.metasystema.org/essays/reply-to-useful.mhtml
>
>Well, I guess it comes down to personal preference. In my time, I've
>seen /many/ personal e-mails end up on mailing lists, and I've had it
>happen myself a few times.
I have as well, but still prefer the Reply-To: field to be set. It's a
default that matches the behavior I most often desire, namely, sending a
single response to the list alone.
>HOWEVER, in saying that, I would really like to see more MUA's with Reply
>(using Reply-To defaulting to From), Reply-To-All and Reply-To-List (reply
>to the mailing list field)...
I would also love to see that; most, IME, have simply Reply (to From:) and
Reply-to-All, which is unsatisfactory. On this list, for example, I can
either Reply and then edit the To: field to the list address instead of the
individual address, or Reply-to-All and then trim out all extraneous
addresses from the To: and possibly Cc: fields.
So, the widespread acceptance of mailers with that third option would
greatly brighten my day, and would make the whole "to munge or not to
munge" debate fairly moot.
Until then, though, I don't think that just posting the URL of the Munging
Considered Harmful page is a sufficient response to someone asking about
the best way to set up a system to munge headers. If we've established that
the decision to munge headers is a personal one, and that there are good
reasons to do it, then a response that basically says "Here's why you
shouldn't do that" is not a sufficient answer -- in fact, it's completely
un-useful.
BTW, I'm not trying to pick on you; I'm just picking on your answer, a bit.
<grin> I've seen a lot of anti-munging sentiment on this list, and as
someone who was initially swayed by Chip Rosenthal's arguments -- until I
started actually running some mailing lists! -- I've decided to try to
represent the other side a bit. Hope you don't mind.
>"See, you not only have to be a good coder to create a system like
>Linux, you have to be a sneaky bastard too."
>- Linus Torvalds
Too many of Linus' quotes just rock.
--Kai MacTane
----------------------------------------------------------------------
"Uh-oh... Gravity works."
--Batty Koda, "Ferngully"
(Hey, bats are gothic.)
Anyone had any success in logging Message-ID:s for (mostly) outgoing
messages and their corresponding send-log-lines?
I'm very interested in such a patch - and the solution is not to use
QUEUE_EXTRA. What I want to have is of course a mapping between a given
Message-ID and the delivery status lines from the log.
/magnus
--
http://x42.com/
On Tue, Oct 31, 2000 at 08:06:12PM +0100, Magnus Bodin wrote:
> Anyone had any success in logging Message-ID:s for (mostly) outgoing
> messages and their corresponding send-log-lines?
I have tried in the past and gave up :(
I tried it at qmail-queue, but only got success if the message is
injected via smtp (otherwise it logs to stdout/stderr and the record is
lost :((.
> I'm very interested in such a patch - and the solution is not to use
> QUEUE_EXTRA. What I want to have is of course a mapping between a given
> Message-ID and the delivery status lines from the log.
We currently use the QUEUE_EXTRA approach.
The extra delivery logs the Received line (for the IP address of the
sender) and the Message-Id (switched from awk to C recently for speedup).
I have hacked a perl script that groups lines like
Oct 31 23:59:48 mail qmail: 973033188.470903 new msg 376662
Oct 31 23:59:48 mail qmail: 973033188.471639 info msg 376662: bytes 5459
from <[EMAIL PROTECTED]> qp 15925 uid 101
Oct 31 23:59:48 mail qmail: 973033188.850856 starting delivery 2947822:
msg 376662 to local [EMAIL PROTECTED]
Oct 31 23:59:48 mail qmail: 973033188.852772 starting delivery 2947823:
msg 376662 to remote [EMAIL PROTECTED]
Oct 31 23:59:48 mail qmail: 973033188.852772 starting delivery 2947824:
msg 376662 to remote [EMAIL PROTECTED]
Oct 31 23:59:49 mail qmail: 973033189.495688 delivery 2947823: success:
195.30.0.14_accepted_message./Remote_host_said:_250_ok_973033189_qp_80774/
Oct 31 23:59:49 mail qmail: 973033189.496798 delivery 2947824: success:
195.30.0.14_accepted_message./Remote_host_said:_250_ok_973033189_qp_80775/
Oct 31 23:59:49 mail qmail: 973033189.755214 delivery 2947822: success:
Received:_from_mailhost.example.com_(1.2.3.4)/Message-ID:_<[EMAIL PROTECTED]>/did_0+0+1/
Oct 31 23:59:49 mail qmail: 973033189.810611 end msg 376662
and writes records (format: tstamp from to size ip message-id)
973033188 <[EMAIL PROTECTED]> [EMAIL PROTECTED] 5459 1.2.3.4
[EMAIL PROTECTED]
973033188 <[EMAIL PROTECTED]> [EMAIL PROTECTED] 5459 1.2.3.4
[EMAIL PROTECTED]
We need this for accounting, but I'm not happy with it at all, as it
slows down qmail alot (IMHO).
So if anyone has a better solution, I'd be really happy.
\Maex
--
SpaceNet GmbH | http://www.Space.Net/ | Stress is when you wake
Research & Development | mailto:[EMAIL PROTECTED] | up screaming and you
Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | realize you haven't
D-80807 Muenchen | Fax: +49 (89) 32356-299 | fallen asleep yet.
hi,
well I solved the last problem I mentioned here ;-)
but there is another one (only a very small one):
Qmail does use mysql as database now but
it does not work when you send mail using a mail program
or a directly telnet connection on the port 25,
it just works when you type "echo to: [EMAIL PROTECTED] |
/var/qmail/bin/qmail-inject".
I have turned the mysql log option on and he looks up the database correctly
when you type "echo to: ..." but it does not work when you make
a direct smtp connection. any ideas?
thanks & bye
sebastian
Hello.
Sorry my english is not very good. I''m newbie to linux and qmail. I try
to install qmail on my linux system and it work. But I can figure out
about the alias for ? Can someone help me ?
Thank's
---
Tomy
Tomy <[EMAIL PROTECTED]> writes on 1 November 2000 at 08:37:51 +0700
> Sorry my english is not very good. I''m newbie to linux and qmail. I try
> to install qmail on my linux system and it work. But I can figure out
> about the alias for ? Can someone help me ?
Is the issue that you can't figure out what the alias user is for?
It's for creating local email addresses that don't go to real users.
In particular you *must* handle root that way; qmail will not deliver
directly to root as a security measure (since qmail-local runs as the
user being delivered to). Postmaster is also usually handled through
an alias, though it would be perfectly possible to create a postmaster
user instead if that worked better for your needs.
Sorry if I've misunderstood your question. Your English is far better
than my, um; now I'm *really* embarassed; I don't even know what
language(s) are spoken in Indonesia.
--
David Dyer-Bennet / Welcome to the future! / [EMAIL PROTECTED]
Photos: http://dd-b.lighthunters.net/
SF: http://www.dd-b.net/dd-b/ Minicon: http://www.mnstf.org/minicon/
I wrote:
>> By the way, does anyone have any interest in comparing notes on really high
>> volume qmail configs? I'm looking for performance in the range of 200-250k
>> remote deliveries per hour. We're halfway there with relatively few
And Greg Cope replied:
>I've a similar issue (high performance required).
>
>We deceided to go for multiple smallish intel boxes due to cost for
>emails per hour ratios work in favour of intel on Linux (or FreeBSD but
>thats a different flame ;-).
>
>Lirking on this list I've seen people achieve between 30k to 150k and
>hour. The average appears to be 50k an hour.
We're getting 100k-110k per hour on a single Sun Ultra2/2167, 512MB RAM,
Solaris 2.7, and the queue directories mounted from a NetApp F740. This is
with an "isolated" queue, i.e., only one message in the queue and qmail-send
processing it as quickly as possible.
We have concurrencyremote set to 500 and the processor run queue is usually
around 10 deep. The machine is 100% busy, with about 30% of CPU time spent in
user code and the rest in the kernel. (More on this below.) We're going to
swap in some faster processors and see how much more work we can get done.
>If bandwidth is not an issue then next bottle neck is the queue and disk
>speed. As far as a I can see once you've moved from a simple DISK, you
>can either:
>
>a) Avoide the queue and talk direct to qmail-remote (and take care of
>bounces / process mgt yourself).
>
> This appears to be where people are getting above 100k and hour.
>
>b) Buy lots of fast disks - RAID 0+1 (due to write performance RAID 5
>appears a bad idea).
We're seeing very little disk I/O. At peak we're doing about 30 read ops/s and
30 write op/s, or around 300-500KB/s in both read and write. Service times are
near-zero and there's no blocking on disks. Again, we're using NetApp filers.
>If you've any nice patches I would be very interested - but my spin on
>the issue is KISS - i.e we will scale by adding small nodes - not
>expensive boxen, and also going with simple set-ups for the sanity of
>the people whom will run this.
>
>I would be very instered in anyone thoughts on theses issues.
The biggest issue I have with qmail's current architecture is that it's doing
a fork/exec for each delivery--and this is really expensive on some platforms.
Short of a threaded qmail-remote (or qmail-send/qmail-remote hybrid), a
pre-forked pool of qmail-remotes waiting on a common socket would probably be
a significant improvement. In short, Apache-style process management.
Ideally communication between qmail-send and qmail-remote would be done over
IP, permitting a distributed configuration with multiple small nodes running
qmail-remotes and a single queue server running qmail-send. Otherwise,
distributing across multiple small boxes running completely independent
instances of qmail is problematic.
-Jeff
Hi all,
I am trying to use maildir instead of mbox. To set maildir the
document guides me to
% maildirmake $HOME/Maildir
% echo ./Maildir/ > ~/.qmail
and and replace ./Mailbox with ./Maildir/ in /var/qmail/rc. I want
to use both .forward and .qmail. so my /var/qmail/rc is
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start '|dot-forward .forward
./Maildir/' splogger qmail
But I found that maildir is work but .forward doesn't work.
PS. Before I set maildir i use mbox format, .forward is normally work.
Thanks,
Effy
Is it possible to operate qmail on a bogus ip address with NAT and port
forwarding?
Thanks for the input.
BK
Yes, eminently so. I do it and it works marvelously. If you like, simply
place a forwarding rule at the firewall to point all smtp and or pop3
traffic to your private ip and the rest works by itself.
Anthony
> -----Original Message-----
> From: Boyd Kelly [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 31, 2000 11:01 PM
> To: [EMAIL PROTECTED]
> Subject: Behind firewall?
>
>
> Is it possible to operate qmail on a bogus ip address with NAT and port
> forwarding?
>
> Thanks for the input.
> BK
>
>
I get lots of these error messagess and lots of other bad behavior
I described in a recently previous email:...
Here are my settings..
Script started on Wed Nov 1 00:49:26 2000
w4:/tmp# cat /admin/bin/chkqmail
#!/bin/tcsh -f
/usr/local/bin/qmail-lint
/var/qmail/bin/qmail-showctl
w4:/tmp# /admin/bin/chkqmail
Warning: cannot receive mail (home directory writable by others): mail
Warning: cannot receive mail (does not own home directory): operator
Warning: cannot receive mail (does not own home directory): games
Warning: cannot receive mail (does not own home directory): ftp
Warning: cannot receive mail (does not own home directory): gdm
Warning: cannot receive mail (does not own home directory): nobody
[tons of these that are known to be for gone accounts]
Warning: cannot receive mail (does not own home directory): accounts
Warning: cannot receive mail (does not own home directory): _hostmaster
Warning: cannot receive mail (does not own home directory): _swbt
Warning: cannot receive mail (does not own home directory): _srl2
Warning: cannot receive mail (does not own home directory): _alias
Warning: cannot receive mail (does not own home directory): ___man2
Warning: cannot receive mail (does not own home directory): _barrngtn
Warning: cannot receive mail (does not own home directory): _ipi
[ 148 edited for brevity ]
Warning: cannot receive mail (does not own home directory): _dfwec
Warning: qmail-local replaces dot with a colon in .qmail filenames:
~dfwuug/.qmail-master.9906
Warning: qmail-local replaces dot with a colon in .qmail filenames:
~dfwuug/.qmail-newsl.9906
[4 edited for brevity]
Warning: cannot receive mail (does not own home directory): texed
Warning: delivery of the virtual domain theranch.org is implicitly controlled by alias
Warning: delivery of the virtual domain sltagency.com is implicitly controlled by alias
Warning: delivery of the virtual domain nccj.org is implicitly controlled by alias
Warning: delivery of the virtual domain foleygroup.com is implicitly controlled by
alias
Warning: delivery of the virtual domain dfwww.com is implicitly controlled by alias
Warning: delivery of the virtual domain gocertified.com is implicitly controlled by
alias
qmail home directory: /var/qmail.
user-ext delimiter: -.
paternalism (in decimal): 2.
silent concurrency limit: 120.
subdirectory split: 23.
user ids: 1005, 1006, 1007, 0, 1008, 1009, 1010, 1011.
!! grep qmail /etc/passwd
alias:*:1005:101::/var/qmail/alias:
qmaild:*:1006:101::/var/qmail:/bin/true
qmaill:*:1007:101::/var/qmail:/bin/true
qmailp:*:1008:101::/var/qmail:/bin/true
qmailq:*:1009:102::/var/qmail:/bin/true
qmailr:*:1010:102::/var/qmail:/bin/true
qmails:*:1011:102::/var/qmail:/bin/true
group ids: 101, 102.
badmailfrom:
[EMAIL PROTECTED] not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
bouncefrom: (Default.) Bounce user name is MAILER-DAEMON.
bouncehost: (Default.) Bounce host name is w4.metronet.com.
concurrencylocal: Local concurrency is 25.
concurrencyremote: Remote concurrency is 30.
databytes: (Default.) SMTP DATA limit is 0 bytes.
defaultdomain: Default domain name is metronet.com.
defaulthost: (Default.) Default host name is w4.metronet.com.
doublebouncehost: (Default.) 2B recipient host: w4.metronet.com.
doublebounceto: (Default.) 2B recipient user: postmaster.
envnoathost: (Default.) Presumed domain name is w4.metronet.com.
helohost: (Default.) SMTP client HELO host name is w4.metronet.com.
idhost: (Default.) Message-ID host name is w4.metronet.com.
localiphost: (Default.) Local IP address becomes w4.metronet.com.
locals:
Messages for LOCALHOST are delivered locally.
Messages for www14.metronet.com are delivered locally.
Messages for w6.metronet.com are delivered locally.
Messages for w5.metronet.com are delivered locally.
Messages for w4.metronet.com are delivered locally.
Messages for wnew.metronet.com are delivered locally.
Messages for accessology.com are delivered locally.
Messages for w3.metronet.com are delivered locally.
Messages for w3-2.metronet.com are delivered locally.
me: My name is w4.metronet.com.
percenthack: (Default.) The percent hack is not allowed.
plusdomain: Plus domain name is metronet.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 1861-1865.com.
SMTP clients may send messages to recipients at .1861-1865.com.
SMTP clients may send messages to recipients at 207.227.169.50.
SMTP clients may send messages to recipients at .207.227.169.50.
SMTP clients may send messages to recipients at 4hcs.com.
SMTP clients may send messages to recipients at .4hcs.com.
SMTP clients may send messages to recipients at DawsonSCHP.com.
SMTP clients may send messages to recipients at .DawsonSCHP.com.
SMTP clients may send messages to recipients at LOCALHOST.
SMTP clients may send messages to recipients at .LOCALHOST.
SMTP clients may send messages to recipients at LemonsAndAssociates.com.
SMTP clients may send messages to recipients at .LemonsAndAssociates.com.
SMTP clients may send messages to recipients at TheDiamondMine.com.
SMTP clients may send messages to recipients at .TheDiamondMine.com.
SMTP clients may send messages to recipients at a-cbt.com.
SMTP clients may send messages to recipients at .a-cbt.com.
SMTP clients may send messages to recipients at abog.org.
SMTP clients may send messages to recipients at .abog.org.
SMTP clients may send messages to recipients at aboutcruiseships.com.
SMTP clients may send messages to recipients at .aboutcruiseships.com.
SMTP clients may send messages to recipients at accentweb.com.
SMTP clients may send messages to recipients at .accentweb.com.
SMTP clients may send messages to recipients at accessology.com.
SMTP clients may send messages to recipients at .accessology.com.
SMTP clients may send messages to recipients at ads1.com.
SMTP clients may send messages to recipients at .ads1.com.
SMTP clients may send messages to recipients at ads1.com.
SMTP clients may send messages to recipients at .ads1.com.
SMTP clients may send messages to recipients at adv-internet-class.com.
SMTP clients may send messages to recipients at .adv-internet-class.com.
SMTP clients may send messages to recipients at advantagesalespromotion.com.
SMTP clients may send messages to recipients at .advantagesalespromotion.com.
SMTP clients may send messages to recipients at adventyouth.org.
SMTP clients may send messages to recipients at .adventyouth.org.
SMTP clients may send messages to recipients at aeroglen.com.
SMTP clients may send messages to recipients at .aeroglen.com.
SMTP clients may send messages to recipients at afcomm.com.
SMTP clients may send messages to recipients at .afcomm.com.
SMTP clients may send messages to recipients at air-texelectric.com.
SMTP clients may send messages to recipients at .air-texelectric.com.
SMTP clients may send messages to recipients at airrite.com.
SMTP clients may send messages to recipients at .airrite.com.
SMTP clients may send messages to recipients at alarm.to.
SMTP clients may send messages to recipients at .alarm.to.
SMTP clients may send messages to recipients at alliancelitigation.com.
SMTP clients may send messages to recipients at .alliancelitigation.com.
SMTP clients may send messages to recipients at antishyster.com.
SMTP clients may send messages to recipients at .antishyster.com.
SMTP clients may send messages to recipients at apfa.org.
SMTP clients may send messages to recipients at .apfa.org.
SMTP clients may send messages to recipients at ari-tex.com.
SMTP clients may send messages to recipients at .ari-tex.com.
SMTP clients may send messages to recipients at ari-texelectric.com.
SMTP clients may send messages to recipients at .ari-texelectric.com.
SMTP clients may send messages to recipients at ari-texelectric.net.
SMTP clients may send messages to recipients at .ari-texelectric.net.
SMTP clients may send messages to recipients at aromajet.com.
SMTP clients may send messages to recipients at .aromajet.com.
SMTP clients may send messages to recipients at arthurs-wine.com.
SMTP clients may send messages to recipients at .arthurs-wine.com.
SMTP clients may send messages to recipients at arts-e-gallery.com.
SMTP clients may send messages to recipients at .arts-e-gallery.com.
SMTP clients may send messages to recipients at aseschool.com.
SMTP clients may send messages to recipients at .aseschool.com.
SMTP clients may send messages to recipients at asesftw.org.
SMTP clients may send messages to recipients at .asesftw.org.
SMTP clients may send messages to recipients at atmintl.com.
SMTP clients may send messages to recipients at .atmintl.com.
SMTP clients may send messages to recipients at automation.to.
SMTP clients may send messages to recipients at .automation.to.
SMTP clients may send messages to recipients at awakeamerica.org.
SMTP clients may send messages to recipients at .awakeamerica.org.
SMTP clients may send messages to recipients at axswave.com.
SMTP clients may send messages to recipients at .axswave.com.
SMTP clients may send messages to recipients at aztekts.com.
SMTP clients may send messages to recipients at .aztekts.com.
SMTP clients may send messages to recipients at banchang.com.
SMTP clients may send messages to recipients at .banchang.com.
SMTP clients may send messages to recipients at banchang.net.
SMTP clients may send messages to recipients at .banchang.net.
SMTP clients may send messages to recipients at banchang.org.
SMTP clients may send messages to recipients at .banchang.org.
SMTP clients may send messages to recipients at bbbackhoe.com.
SMTP clients may send messages to recipients at .bbbackhoe.com.
SMTP clients may send messages to recipients at be-seen.net.
SMTP clients may send messages to recipients at .be-seen.net.
SMTP clients may send messages to recipients at beaconstat.com.
SMTP clients may send messages to recipients at .beaconstat.com.
SMTP clients may send messages to recipients at bigdmetal.com.
SMTP clients may send messages to recipients at .bigdmetal.com.
SMTP clients may send messages to recipients at blacklandjrt.com.
SMTP clients may send messages to recipients at .blacklandjrt.com.
SMTP clients may send messages to recipients at bloodcare.org.
SMTP clients may send messages to recipients at .bloodcare.org.
SMTP clients may send messages to recipients at boardcertified-implant.com.
SMTP clients may send messages to recipients at .boardcertified-implant.com.
SMTP clients may send messages to recipients at brandteng.com.
SMTP clients may send messages to recipients at .brandteng.com.
SMTP clients may send messages to recipients at caddomills.com.
SMTP clients may send messages to recipients at .caddomills.com.
SMTP clients may send messages to recipients at campbellcontract.com.
SMTP clients may send messages to recipients at .campbellcontract.com.
SMTP clients may send messages to recipients at carads.com.
SMTP clients may send messages to recipients at .carads.com.
SMTP clients may send messages to recipients at carry-safe.com.
SMTP clients may send messages to recipients at .carry-safe.com.
SMTP clients may send messages to recipients at cartwrightsigns.com.
SMTP clients may send messages to recipients at .cartwrightsigns.com.
SMTP clients may send messages to recipients at cdbargains.com.
SMTP clients may send messages to recipients at .cdbargains.com.
SMTP clients may send messages to recipients at cenotes.com.
SMTP clients may send messages to recipients at .cenotes.com.
SMTP clients may send messages to recipients at centuryinspection.com.
SMTP clients may send messages to recipients at .centuryinspection.com.
SMTP clients may send messages to recipients at chasedivers.com.
SMTP clients may send messages to recipients at .chasedivers.com.
SMTP clients may send messages to recipients at chateauprod.com.
SMTP clients may send messages to recipients at .chateauprod.com.
SMTP clients may send messages to recipients at cheezmo.com.
SMTP clients may send messages to recipients at .cheezmo.com.
SMTP clients may send messages to recipients at chinateapots.com.
SMTP clients may send messages to recipients at .chinateapots.com.
SMTP clients may send messages to recipients at chouteau.tmi.net.
SMTP clients may send messages to recipients at .chouteau.tmi.net.
SMTP clients may send messages to recipients at cimarron.net.
SMTP clients may send messages to recipients at .cimarron.net.
SMTP clients may send messages to recipients at city-garage.com.
SMTP clients may send messages to recipients at .city-garage.com.
SMTP clients may send messages to recipients at claybradfield.com.
SMTP clients may send messages to recipients at .claybradfield.com.
SMTP clients may send messages to recipients at club4lovers.com.
SMTP clients may send messages to recipients at .club4lovers.com.
SMTP clients may send messages to recipients at comp-solution.com.
SMTP clients may send messages to recipients at .comp-solution.com.
SMTP clients may send messages to recipients at computercrossroads.net.
SMTP clients may send messages to recipients at .computercrossroads.net.
SMTP clients may send messages to recipients at cool-games.com.
SMTP clients may send messages to recipients at .cool-games.com.
SMTP clients may send messages to recipients at coquest.com.
SMTP clients may send messages to recipients at .coquest.com.
SMTP clients may send messages to recipients at cottondome.org.
SMTP clients may send messages to recipients at .cottondome.org.
SMTP clients may send messages to recipients at cowchip.com.
SMTP clients may send messages to recipients at .cowchip.com.
SMTP clients may send messages to recipients at cramdown.com.
SMTP clients may send messages to recipients at .cramdown.com.
SMTP clients may send messages to recipients at crossroute.net.
SMTP clients may send messages to recipients at .crossroute.net.
SMTP clients may send messages to recipients at cwb.tmi.net.
SMTP clients may send messages to recipients at .cwb.tmi.net.
SMTP clients may send messages to recipients at cybercouch.com.
SMTP clients may send messages to recipients at .cybercouch.com.
SMTP clients may send messages to recipients at dallasbuildings.com.
SMTP clients may send messages to recipients at .dallasbuildings.com.
SMTP clients may send messages to recipients at dallaswebpros.com.
SMTP clients may send messages to recipients at .dallaswebpros.com.
SMTP clients may send messages to recipients at davidgriffin.com.
SMTP clients may send messages to recipients at .davidgriffin.com.
SMTP clients may send messages to recipients at davidwebbonline.com.
SMTP clients may send messages to recipients at .davidwebbonline.com.
SMTP clients may send messages to recipients at dbedell.com.
SMTP clients may send messages to recipients at .dbedell.com.
SMTP clients may send messages to recipients at designtransport.com.
SMTP clients may send messages to recipients at .designtransport.com.
SMTP clients may send messages to recipients at designtransport.net.
SMTP clients may send messages to recipients at .designtransport.net.
SMTP clients may send messages to recipients at designtransport.org.
SMTP clients may send messages to recipients at .designtransport.org.
SMTP clients may send messages to recipients at dfweb.com.
SMTP clients may send messages to recipients at .dfweb.com.
SMTP clients may send messages to recipients at dfwedi.org.
SMTP clients may send messages to recipients at .dfwedi.org.
SMTP clients may send messages to recipients at dfwlivemusic.com.
SMTP clients may send messages to recipients at .dfwlivemusic.com.
SMTP clients may send messages to recipients at dfwuug.org.
SMTP clients may send messages to recipients at .dfwuug.org.
SMTP clients may send messages to recipients at dfwww.com.
SMTP clients may send messages to recipients at .dfwww.com.
SMTP clients may send messages to recipients at dfwww.com.
SMTP clients may send messages to recipients at .dfwww.com.
SMTP clients may send messages to recipients at dgriffin.com.
SMTP clients may send messages to recipients at .dgriffin.com.
SMTP clients may send messages to recipients at dougbedell.com.
SMTP clients may send messages to recipients at .dougbedell.com.
SMTP clients may send messages to recipients at drs.propathlab.com.
SMTP clients may send messages to recipients at .drs.propathlab.com.
SMTP clients may send messages to recipients at ecaard.com.
SMTP clients may send messages to recipients at .ecaard.com.
SMTP clients may send messages to recipients at eduserveassociates.com.
SMTP clients may send messages to recipients at .eduserveassociates.com.
SMTP clients may send messages to recipients at eduserveassociates.net.
SMTP clients may send messages to recipients at .eduserveassociates.net.
SMTP clients may send messages to recipients at eduserveassociates.org.
SMTP clients may send messages to recipients at .eduserveassociates.org.
SMTP clients may send messages to recipients at eforest.com.
SMTP clients may send messages to recipients at .eforest.com.
SMTP clients may send messages to recipients at eforest.com.
SMTP clients may send messages to recipients at .eforest.com.
SMTP clients may send messages to recipients at electricrc.com.
SMTP clients may send messages to recipients at .electricrc.com.
SMTP clients may send messages to recipients at elisium.com.
SMTP clients may send messages to recipients at .elisium.com.
SMTP clients may send messages to recipients at elucidata.org.
SMTP clients may send messages to recipients at .elucidata.org.
SMTP clients may send messages to recipients at emmittsmith.com.
SMTP clients may send messages to recipients at .emmittsmith.com.
SMTP clients may send messages to recipients at entrepreneurstore.com.
SMTP clients may send messages to recipients at .entrepreneurstore.com.
SMTP clients may send messages to recipients at execon.com.
SMTP clients may send messages to recipients at .execon.com.
SMTP clients may send messages to recipients at faf.com.
SMTP clients may send messages to recipients at .faf.com.
SMTP clients may send messages to recipients at farace.com.
SMTP clients may send messages to recipients at .farace.com.
SMTP clients may send messages to recipients at fbc-mckinney.org.
SMTP clients may send messages to recipients at .fbc-mckinney.org.
SMTP clients may send messages to recipients at feenix.metronet.com.
SMTP clients may send messages to recipients at .feenix.metronet.com.
SMTP clients may send messages to recipients at fiinix.metronet.com.
SMTP clients may send messages to recipients at .fiinix.metronet.com.
SMTP clients may send messages to recipients at fleetwatch.com.
SMTP clients may send messages to recipients at .fleetwatch.com.
SMTP clients may send messages to recipients at fnbsachse.com.
SMTP clients may send messages to recipients at .fnbsachse.com.
SMTP clients may send messages to recipients at fohnix.metronet.com.
SMTP clients may send messages to recipients at .fohnix.metronet.com.
SMTP clients may send messages to recipients at foleygroup.com.
SMTP clients may send messages to recipients at .foleygroup.com.
SMTP clients may send messages to recipients at foneco.com.
SMTP clients may send messages to recipients at .foneco.com.
SMTP clients may send messages to recipients at freemanpos.com.
SMTP clients may send messages to recipients at .freemanpos.com.
SMTP clients may send messages to recipients at fulferandassociates.com.
SMTP clients may send messages to recipients at .fulferandassociates.com.
SMTP clients may send messages to recipients at fwmsh.org.
SMTP clients may send messages to recipients at .fwmsh.org.
SMTP clients may send messages to recipients at fwmsh.org.
SMTP clients may send messages to recipients at .fwmsh.org.
SMTP clients may send messages to recipients at fwmuseum.org.
SMTP clients may send messages to recipients at .fwmuseum.org.
SMTP clients may send messages to recipients at fwmuseum.org.
SMTP clients may send messages to recipients at .fwmuseum.org.
SMTP clients may send messages to recipients at gallerywall.com.
SMTP clients may send messages to recipients at .gallerywall.com.
SMTP clients may send messages to recipients at garlandlittleleague.com.
SMTP clients may send messages to recipients at .garlandlittleleague.com.
SMTP clients may send messages to recipients at gaybarguide.com.
SMTP clients may send messages to recipients at .gaybarguide.com.
SMTP clients may send messages to recipients at geckonet.cx.
SMTP clients may send messages to recipients at .geckonet.cx.
SMTP clients may send messages to recipients at geminihse.com.
SMTP clients may send messages to recipients at .geminihse.com.
SMTP clients may send messages to recipients at globalclothier.com.
SMTP clients may send messages to recipients at .globalclothier.com.
SMTP clients may send messages to recipients at gnadirect.com.
SMTP clients may send messages to recipients at .gnadirect.com.
SMTP clients may send messages to recipients at gocertified.com.
SMTP clients may send messages to recipients at .gocertified.com.
SMTP clients may send messages to recipients at gocertified.com.
SMTP clients may send messages to recipients at .gocertified.com.
SMTP clients may send messages to recipients at goddesssiren.com.
SMTP clients may send messages to recipients at .goddesssiren.com.
SMTP clients may send messages to recipients at granadamovieposters.com.
SMTP clients may send messages to recipients at .granadamovieposters.com.
SMTP clients may send messages to recipients at granburyoperahouse.org.
SMTP clients may send messages to recipients at .granburyoperahouse.org.
SMTP clients may send messages to recipients at greenvilletexas.net.
SMTP clients may send messages to recipients at .greenvilletexas.net.
SMTP clients may send messages to recipients at groundfloor.com.
SMTP clients may send messages to recipients at .groundfloor.com.
SMTP clients may send messages to recipients at guesthouses.net.
SMTP clients may send messages to recipients at .guesthouses.net.
SMTP clients may send messages to recipients at guestranches.com.
SMTP clients may send messages to recipients at .guestranches.com.
SMTP clients may send messages to recipients at gymbag.com.
SMTP clients may send messages to recipients at .gymbag.com.
SMTP clients may send messages to recipients at hamstra.org.
SMTP clients may send messages to recipients at .hamstra.org.
SMTP clients may send messages to recipients at harrell.com.
SMTP clients may send messages to recipients at .harrell.com.
SMTP clients may send messages to recipients at hartgaugler.com.
SMTP clients may send messages to recipients at .hartgaugler.com.
SMTP clients may send messages to recipients at hblawfirm.com.
SMTP clients may send messages to recipients at .hblawfirm.com.
SMTP clients may send messages to recipients at hblawfirm.net.
SMTP clients may send messages to recipients at .hblawfirm.net.
SMTP clients may send messages to recipients at hcvco.com.
SMTP clients may send messages to recipients at .hcvco.com.
SMTP clients may send messages to recipients at hebnet.com.
SMTP clients may send messages to recipients at .hebnet.com.
SMTP clients may send messages to recipients at hendrixnet.com.
SMTP clients may send messages to recipients at .hendrixnet.com.
SMTP clients may send messages to recipients at hightech.com.
SMTP clients may send messages to recipients at .hightech.com.
SMTP clients may send messages to recipients at hoperealty.com.
SMTP clients may send messages to recipients at .hoperealty.com.
SMTP clients may send messages to recipients at hornytoadsforever.com.
SMTP clients may send messages to recipients at .hornytoadsforever.com.
SMTP clients may send messages to recipients at hrnexus.com.
SMTP clients may send messages to recipients at .hrnexus.com.
SMTP clients may send messages to recipients at hsaa.org.
SMTP clients may send messages to recipients at .hsaa.org.
SMTP clients may send messages to recipients at hydro-carbon.net.
SMTP clients may send messages to recipients at .hydro-carbon.net.
SMTP clients may send messages to recipients at icanet.com.
SMTP clients may send messages to recipients at .icanet.com.
SMTP clients may send messages to recipients at icf-usa.com.
SMTP clients may send messages to recipients at .icf-usa.com.
SMTP clients may send messages to recipients at iigo.com.
SMTP clients may send messages to recipients at .iigo.com.
SMTP clients may send messages to recipients at image2000texas.com.
SMTP clients may send messages to recipients at .image2000texas.com.
SMTP clients may send messages to recipients at impact-plano.com.
SMTP clients may send messages to recipients at .impact-plano.com.
SMTP clients may send messages to recipients at informedcustomer.com.
SMTP clients may send messages to recipients at .informedcustomer.com.
SMTP clients may send messages to recipients at inner-i.com.
SMTP clients may send messages to recipients at .inner-i.com.
SMTP clients may send messages to recipients at integrityweb.com.
SMTP clients may send messages to recipients at .integrityweb.com.
SMTP clients may send messages to recipients at internet-seminar.com.
SMTP clients may send messages to recipients at .internet-seminar.com.
SMTP clients may send messages to recipients at jadpc.com.
SMTP clients may send messages to recipients at .jadpc.com.
SMTP clients may send messages to recipients at jasonlapoint.com.
SMTP clients may send messages to recipients at .jasonlapoint.com.
SMTP clients may send messages to recipients at javamug.org.
SMTP clients may send messages to recipients at .javamug.org.
SMTP clients may send messages to recipients at jbrousseau.com.
SMTP clients may send messages to recipients at .jbrousseau.com.
SMTP clients may send messages to recipients at kennedylicensing.com.
SMTP clients may send messages to recipients at .kennedylicensing.com.
SMTP clients may send messages to recipients at kennedylicensing.com.
SMTP clients may send messages to recipients at .kennedylicensing.com.
SMTP clients may send messages to recipients at kera.org.
SMTP clients may send messages to recipients at .kera.org.
SMTP clients may send messages to recipients at kevinmccarthy.com.
SMTP clients may send messages to recipients at .kevinmccarthy.com.
SMTP clients may send messages to recipients at kevinmccarthy.net.
SMTP clients may send messages to recipients at .kevinmccarthy.net.
SMTP clients may send messages to recipients at kevinscoggins.com.
SMTP clients may send messages to recipients at .kevinscoggins.com.
SMTP clients may send messages to recipients at klicker.net.
SMTP clients may send messages to recipients at .klicker.net.
SMTP clients may send messages to recipients at kryza.com.
SMTP clients may send messages to recipients at .kryza.com.
SMTP clients may send messages to recipients at laemcharoen.com.
SMTP clients may send messages to recipients at .laemcharoen.com.
SMTP clients may send messages to recipients at lancastermachine.com.
SMTP clients may send messages to recipients at .lancastermachine.com.
SMTP clients may send messages to recipients at lanzador.net.
SMTP clients may send messages to recipients at .lanzador.net.
SMTP clients may send messages to recipients at leader1.net.
SMTP clients may send messages to recipients at .leader1.net.
SMTP clients may send messages to recipients at legalshop.com.
SMTP clients may send messages to recipients at .legalshop.com.
SMTP clients may send messages to recipients at letshunt.com.
SMTP clients may send messages to recipients at .letshunt.com.
SMTP clients may send messages to recipients at levitt.com.
SMTP clients may send messages to recipients at .levitt.com.
SMTP clients may send messages to recipients at liturgicalpublishing.com.
SMTP clients may send messages to recipients at .liturgicalpublishing.com.
SMTP clients may send messages to recipients at liturgicalservices.com.
SMTP clients may send messages to recipients at .liturgicalservices.com.
SMTP clients may send messages to recipients at lmis-fw.com.
SMTP clients may send messages to recipients at .lmis-fw.com.
SMTP clients may send messages to recipients at logical-resources.com.
SMTP clients may send messages to recipients at .logical-resources.com.
SMTP clients may send messages to recipients at longviewgas.com.
SMTP clients may send messages to recipients at .longviewgas.com.
SMTP clients may send messages to recipients at lotterycall.com.
SMTP clients may send messages to recipients at .lotterycall.com.
SMTP clients may send messages to recipients at lozon.com.
SMTP clients may send messages to recipients at .lozon.com.
SMTP clients may send messages to recipients at lozon.com.
SMTP clients may send messages to recipients at .lozon.com.
SMTP clients may send messages to recipients at lshopping.com.
SMTP clients may send messages to recipients at .lshopping.com.
SMTP clients may send messages to recipients at lunabiz.com.
SMTP clients may send messages to recipients at .lunabiz.com.
SMTP clients may send messages to recipients at mail.metronet.com.
SMTP clients may send messages to recipients at .mail.metronet.com.
SMTP clients may send messages to recipients at maptaphut.com.
SMTP clients may send messages to recipients at .maptaphut.com.
SMTP clients may send messages to recipients at maptaphut.net.
SMTP clients may send messages to recipients at .maptaphut.net.
SMTP clients may send messages to recipients at maptaphut.org.
SMTP clients may send messages to recipients at .maptaphut.org.
SMTP clients may send messages to recipients at marnette.com.
SMTP clients may send messages to recipients at .marnette.com.
SMTP clients may send messages to recipients at matise.com.
SMTP clients may send messages to recipients at .matise.com.
SMTP clients may send messages to recipients at mcdavid.com.
SMTP clients may send messages to recipients at .mcdavid.com.
SMTP clients may send messages to recipients at mcgrathdesign.com.
SMTP clients may send messages to recipients at .mcgrathdesign.com.
SMTP clients may send messages to recipients at mcgrathdesign.com.
SMTP clients may send messages to recipients at .mcgrathdesign.com.
SMTP clients may send messages to recipients at mcwalters.net.
SMTP clients may send messages to recipients at .mcwalters.net.
SMTP clients may send messages to recipients at mediaprojects.org.
SMTP clients may send messages to recipients at .mediaprojects.org.
SMTP clients may send messages to recipients at medifund.com.
SMTP clients may send messages to recipients at .medifund.com.
SMTP clients may send messages to recipients at metronet.com.
SMTP clients may send messages to recipients at .metronet.com.
SMTP clients may send messages to recipients at metronet.com.
SMTP clients may send messages to recipients at .metronet.com.
SMTP clients may send messages to recipients at metroplexorthopedics.com.
SMTP clients may send messages to recipients at .metroplexorthopedics.com.
SMTP clients may send messages to recipients at mgicorp.com.
SMTP clients may send messages to recipients at .mgicorp.com.
SMTP clients may send messages to recipients at microfab.com.
SMTP clients may send messages to recipients at .microfab.com.
SMTP clients may send messages to recipients at mike-moncrief.com.
SMTP clients may send messages to recipients at .mike-moncrief.com.
SMTP clients may send messages to recipients at missionnet.org.
SMTP clients may send messages to recipients at .missionnet.org.
SMTP clients may send messages to recipients at mixsoftware.com.
SMTP clients may send messages to recipients at .mixsoftware.com.
SMTP clients may send messages to recipients at mixsoftware.com.
SMTP clients may send messages to recipients at .mixsoftware.com.
SMTP clients may send messages to recipients at mlmedia.com.
SMTP clients may send messages to recipients at .mlmedia.com.
SMTP clients may send messages to recipients at mm-network.com.
SMTP clients may send messages to recipients at .mm-network.com.
SMTP clients may send messages to recipients at mmit.com.
SMTP clients may send messages to recipients at .mmit.com.
SMTP clients may send messages to recipients at moonfishstudios.com.
SMTP clients may send messages to recipients at .moonfishstudios.com.
SMTP clients may send messages to recipients at mpgems.com.
SMTP clients may send messages to recipients at .mpgems.com.
SMTP clients may send messages to recipients at mr-moody.com.
SMTP clients may send messages to recipients at .mr-moody.com.
SMTP clients may send messages to recipients at mxdco.com.
SMTP clients may send messages to recipients at .mxdco.com.
SMTP clients may send messages to recipients at natlstaffingunltd.com.
SMTP clients may send messages to recipients at .natlstaffingunltd.com.
SMTP clients may send messages to recipients at nccj.org.
SMTP clients may send messages to recipients at .nccj.org.
SMTP clients may send messages to recipients at neelam.com.
SMTP clients may send messages to recipients at .neelam.com.
SMTP clients may send messages to recipients at nerdburger.com.
SMTP clients may send messages to recipients at .nerdburger.com.
SMTP clients may send messages to recipients at net-connections.com.
SMTP clients may send messages to recipients at .net-connections.com.
SMTP clients may send messages to recipients at news.metronet.com.
SMTP clients may send messages to recipients at .news.metronet.com.
SMTP clients may send messages to recipients at nightlifetalent.com.
SMTP clients may send messages to recipients at .nightlifetalent.com.
SMTP clients may send messages to recipients at norcabos.com.
SMTP clients may send messages to recipients at .norcabos.com.
SMTP clients may send messages to recipients at nordal.com.
SMTP clients may send messages to recipients at .nordal.com.
SMTP clients may send messages to recipients at northstarpaper.com.
SMTP clients may send messages to recipients at .northstarpaper.com.
SMTP clients may send messages to recipients at ns1.metronet.com.
SMTP clients may send messages to recipients at .ns1.metronet.com.
SMTP clients may send messages to recipients at nsullc.com.
SMTP clients may send messages to recipients at .nsullc.com.
SMTP clients may send messages to recipients at octeldesignpartners.com.
SMTP clients may send messages to recipients at .octeldesignpartners.com.
SMTP clients may send messages to recipients at omce.org.
SMTP clients may send messages to recipients at .omce.org.
SMTP clients may send messages to recipients at ondaweb.com.
SMTP clients may send messages to recipients at .ondaweb.com.
SMTP clients may send messages to recipients at optimalsuccess.com.
SMTP clients may send messages to recipients at .optimalsuccess.com.
SMTP clients may send messages to recipients at ow4.metronet.com.
SMTP clients may send messages to recipients at .ow4.metronet.com.
SMTP clients may send messages to recipients at pagerpal.com.
SMTP clients may send messages to recipients at .pagerpal.com.
SMTP clients may send messages to recipients at panache-plus.com.
SMTP clients may send messages to recipients at .panache-plus.com.
SMTP clients may send messages to recipients at pauli.to.
SMTP clients may send messages to recipients at .pauli.to.
SMTP clients may send messages to recipients at pcenterprise.com.
SMTP clients may send messages to recipients at .pcenterprise.com.
SMTP clients may send messages to recipients at pcjeep.com.
SMTP clients may send messages to recipients at .pcjeep.com.
SMTP clients may send messages to recipients at perlsoftware.com.
SMTP clients may send messages to recipients at .perlsoftware.com.
SMTP clients may send messages to recipients at persianoutpost.com.
SMTP clients may send messages to recipients at .persianoutpost.com.
SMTP clients may send messages to recipients at persianoutpost.com.
SMTP clients may send messages to recipients at .persianoutpost.com.
SMTP clients may send messages to recipients at plannersguide.com.
SMTP clients may send messages to recipients at .plannersguide.com.
SMTP clients may send messages to recipients at planohomes.com.
SMTP clients may send messages to recipients at .planohomes.com.
SMTP clients may send messages to recipients at planotile.com.
SMTP clients may send messages to recipients at .planotile.com.
SMTP clients may send messages to recipients at poetryinocean.com.
SMTP clients may send messages to recipients at .poetryinocean.com.
SMTP clients may send messages to recipients at portusa.com.
SMTP clients may send messages to recipients at .portusa.com.
SMTP clients may send messages to recipients at pr1.com.
SMTP clients may send messages to recipients at .pr1.com.
SMTP clients may send messages to recipients at prestigegarland.com.
SMTP clients may send messages to recipients at .prestigegarland.com.
SMTP clients may send messages to recipients at prj-cms.com.
SMTP clients may send messages to recipients at .prj-cms.com.
SMTP clients may send messages to recipients at propathlab.com.
SMTP clients may send messages to recipients at .propathlab.com.
SMTP clients may send messages to recipients at puttingdeck.com.
SMTP clients may send messages to recipients at .puttingdeck.com.
SMTP clients may send messages to recipients at r2now.com.
SMTP clients may send messages to recipients at .r2now.com.
SMTP clients may send messages to recipients at rayong.net.
SMTP clients may send messages to recipients at .rayong.net.
SMTP clients may send messages to recipients at rayong.org.
SMTP clients may send messages to recipients at .rayong.org.
SMTP clients may send messages to recipients at rayongbeer.com.
SMTP clients may send messages to recipients at .rayongbeer.com.
SMTP clients may send messages to recipients at rayongcoffee.com.
SMTP clients may send messages to recipients at .rayongcoffee.com.
SMTP clients may send messages to recipients at rayonggolf.com.
SMTP clients may send messages to recipients at .rayonggolf.com.
SMTP clients may send messages to recipients at rayongprovince.com.
SMTP clients may send messages to recipients at .rayongprovince.com.
SMTP clients may send messages to recipients at rayongsearch.com.
SMTP clients may send messages to recipients at .rayongsearch.com.
SMTP clients may send messages to recipients at rbnetdesigns.com.
SMTP clients may send messages to recipients at .rbnetdesigns.com.
SMTP clients may send messages to recipients at readingquote.com.
SMTP clients may send messages to recipients at .readingquote.com.
SMTP clients may send messages to recipients at realtybyrita.com.
SMTP clients may send messages to recipients at .realtybyrita.com.
SMTP clients may send messages to recipients at remtek.com.
SMTP clients may send messages to recipients at .remtek.com.
SMTP clients may send messages to recipients at retinafoundation.org.
SMTP clients may send messages to recipients at .retinafoundation.org.
SMTP clients may send messages to recipients at retinafoundation.org.
SMTP clients may send messages to recipients at .retinafoundation.org.
SMTP clients may send messages to recipients at rgnet.com.
SMTP clients may send messages to recipients at .rgnet.com.
SMTP clients may send messages to recipients at rhcc.org.
SMTP clients may send messages to recipients at .rhcc.org.
SMTP clients may send messages to recipients at richardsonsymphony.com.
SMTP clients may send messages to recipients at .richardsonsymphony.com.
SMTP clients may send messages to recipients at richardsonsymphony.org.
SMTP clients may send messages to recipients at .richardsonsymphony.org.
SMTP clients may send messages to recipients at riltec.com.
SMTP clients may send messages to recipients at .riltec.com.
SMTP clients may send messages to recipients at rjones.com.
SMTP clients may send messages to recipients at .rjones.com.
SMTP clients may send messages to recipients at rlewis.com.
SMTP clients may send messages to recipients at .rlewis.com.
SMTP clients may send messages to recipients at rockwalltexas.net.
SMTP clients may send messages to recipients at .rockwalltexas.net.
SMTP clients may send messages to recipients at roughcreek.com.
SMTP clients may send messages to recipients at .roughcreek.com.
SMTP clients may send messages to recipients at roysecity.com.
SMTP clients may send messages to recipients at .roysecity.com.
SMTP clients may send messages to recipients at roysecity.net.
SMTP clients may send messages to recipients at .roysecity.net.
SMTP clients may send messages to recipients at roysecity.org.
SMTP clients may send messages to recipients at .roysecity.org.
SMTP clients may send messages to recipients at roysecityonline.com.
SMTP clients may send messages to recipients at .roysecityonline.com.
SMTP clients may send messages to recipients at roysecitytx.com.
SMTP clients may send messages to recipients at .roysecitytx.com.
SMTP clients may send messages to recipients at rpmrecords.com.
SMTP clients may send messages to recipients at .rpmrecords.com.
SMTP clients may send messages to recipients at ruralmetro-tx.com.
SMTP clients may send messages to recipients at .ruralmetro-tx.com.
SMTP clients may send messages to recipients at safety4children.com.
SMTP clients may send messages to recipients at .safety4children.com.
SMTP clients may send messages to recipients at sai.it.
SMTP clients may send messages to recipients at .sai.it.
SMTP clients may send messages to recipients at saledays.com.
SMTP clients may send messages to recipients at .saledays.com.
SMTP clients may send messages to recipients at satellink.com.
SMTP clients may send messages to recipients at .satellink.com.
SMTP clients may send messages to recipients at satellink.com.
SMTP clients may send messages to recipients at .satellink.com.
SMTP clients may send messages to recipients at savanttech.com.
SMTP clients may send messages to recipients at .savanttech.com.
SMTP clients may send messages to recipients at sd-productions.com.
SMTP clients may send messages to recipients at .sd-productions.com.
SMTP clients may send messages to recipients at sd-productions.com.
SMTP clients may send messages to recipients at .sd-productions.com.
SMTP clients may send messages to recipients at seahoss.com.
SMTP clients may send messages to recipients at .seahoss.com.
SMTP clients may send messages to recipients at seahoss.org.
SMTP clients may send messages to recipients at .seahoss.org.
SMTP clients may send messages to recipients at self-image.com.
SMTP clients may send messages to recipients at .self-image.com.
SMTP clients may send messages to recipients at sintezo.com.
SMTP clients may send messages to recipients at .sintezo.com.
SMTP clients may send messages to recipients at skurf.com.
SMTP clients may send messages to recipients at .skurf.com.
SMTP clients may send messages to recipients at sltagency.com.
SMTP clients may send messages to recipients at .sltagency.com.
SMTP clients may send messages to recipients at smartideas.to.
SMTP clients may send messages to recipients at .smartideas.to.
SMTP clients may send messages to recipients at smtp.metronet.com.
SMTP clients may send messages to recipients at .smtp.metronet.com.
SMTP clients may send messages to recipients at solstar.com.
SMTP clients may send messages to recipients at .solstar.com.
SMTP clients may send messages to recipients at solstar.net.
SMTP clients may send messages to recipients at .solstar.net.
SMTP clients may send messages to recipients at solsticeinc.net.
SMTP clients may send messages to recipients at .solsticeinc.net.
SMTP clients may send messages to recipients at special-arrangements.net.
SMTP clients may send messages to recipients at .special-arrangements.net.
SMTP clients may send messages to recipients at stashu.com.
SMTP clients may send messages to recipients at .stashu.com.
SMTP clients may send messages to recipients at stefco.com.
SMTP clients may send messages to recipients at .stefco.com.
SMTP clients may send messages to recipients at stevehill.org.
SMTP clients may send messages to recipients at .stevehill.org.
SMTP clients may send messages to recipients at stoneagency.com.
SMTP clients may send messages to recipients at .stoneagency.com.
SMTP clients may send messages to recipients at straten.com.
SMTP clients may send messages to recipients at .straten.com.
SMTP clients may send messages to recipients at straten.com.
SMTP clients may send messages to recipients at .straten.com.
SMTP clients may send messages to recipients at stunt-show.com.
SMTP clients may send messages to recipients at .stunt-show.com.
SMTP clients may send messages to recipients at suzannerobertsgifts.com.
SMTP clients may send messages to recipients at .suzannerobertsgifts.com.
SMTP clients may send messages to recipients at svi.net.
SMTP clients may send messages to recipients at .svi.net.
SMTP clients may send messages to recipients at swautomated.com.
SMTP clients may send messages to recipients at .swautomated.com.
SMTP clients may send messages to recipients at system-is.com.
SMTP clients may send messages to recipients at .system-is.com.
SMTP clients may send messages to recipients at tajrish.com.
SMTP clients may send messages to recipients at .tajrish.com.
SMTP clients may send messages to recipients at takeupyourcross.com.
SMTP clients may send messages to recipients at .takeupyourcross.com.
SMTP clients may send messages to recipients at tbcltd.com.
SMTP clients may send messages to recipients at .tbcltd.com.
SMTP clients may send messages to recipients at tboneinc.com.
SMTP clients may send messages to recipients at .tboneinc.com.
SMTP clients may send messages to recipients at telecomrc.com.
SMTP clients may send messages to recipients at .telecomrc.com.
SMTP clients may send messages to recipients at telecomsearch.com.
SMTP clients may send messages to recipients at .telecomsearch.com.
SMTP clients may send messages to recipients at terzon.com.
SMTP clients may send messages to recipients at .terzon.com.
SMTP clients may send messages to recipients at testechinc.com.
SMTP clients may send messages to recipients at .testechinc.com.
SMTP clients may send messages to recipients at texasannouncements.com.
SMTP clients may send messages to recipients at .texasannouncements.com.
SMTP clients may send messages to recipients at texedol.com.
SMTP clients may send messages to recipients at .texedol.com.
SMTP clients may send messages to recipients at texedol.net.
SMTP clients may send messages to recipients at .texedol.net.
SMTP clients may send messages to recipients at texedol.org.
SMTP clients may send messages to recipients at .texedol.org.
SMTP clients may send messages to recipients at thaiautomate.com.
SMTP clients may send messages to recipients at .thaiautomate.com.
SMTP clients may send messages to recipients at thaibrew.com.
SMTP clients may send messages to recipients at .thaibrew.com.
SMTP clients may send messages to recipients at thaibrewery.com.
SMTP clients may send messages to recipients at .thaibrewery.com.
SMTP clients may send messages to recipients at thaibrewhouse.com.
SMTP clients may send messages to recipients at .thaibrewhouse.com.
SMTP clients may send messages to recipients at thaichem.com.
SMTP clients may send messages to recipients at .thaichem.com.
SMTP clients may send messages to recipients at thaicigar.com.
SMTP clients may send messages to recipients at .thaicigar.com.
SMTP clients may send messages to recipients at thaicontrol.com.
SMTP clients may send messages to recipients at .thaicontrol.com.
SMTP clients may send messages to recipients at thaiemulsion.com.
SMTP clients may send messages to recipients at .thaiemulsion.com.
SMTP clients may send messages to recipients at thaipaint.com.
SMTP clients may send messages to recipients at .thaipaint.com.
SMTP clients may send messages to recipients at thaipetro.com.
SMTP clients may send messages to recipients at .thaipetro.com.
SMTP clients may send messages to recipients at thaipetrochem.com.
SMTP clients may send messages to recipients at .thaipetrochem.com.
SMTP clients may send messages to recipients at thaiplant.com.
SMTP clients may send messages to recipients at .thaiplant.com.
SMTP clients may send messages to recipients at thaipolymer.com.
SMTP clients may send messages to recipients at .thaipolymer.com.
SMTP clients may send messages to recipients at thaisolar.com.
SMTP clients may send messages to recipients at .thaisolar.com.
SMTP clients may send messages to recipients at thaitea.com.
SMTP clients may send messages to recipients at .thaitea.com.
SMTP clients may send messages to recipients at thaiwine.com.
SMTP clients may send messages to recipients at .thaiwine.com.
SMTP clients may send messages to recipients at the-unforgiven.com.
SMTP clients may send messages to recipients at .the-unforgiven.com.
SMTP clients may send messages to recipients at theallergystore.com.
SMTP clients may send messages to recipients at .theallergystore.com.
SMTP clients may send messages to recipients at thebilgepumps.com.
SMTP clients may send messages to recipients at .thebilgepumps.com.
SMTP clients may send messages to recipients at thebizjet.net.
SMTP clients may send messages to recipients at .thebizjet.net.
SMTP clients may send messages to recipients at thefacilitator.com.
SMTP clients may send messages to recipients at .thefacilitator.com.
SMTP clients may send messages to recipients at theranch.org.
SMTP clients may send messages to recipients at .theranch.org.
SMTP clients may send messages to recipients at thestearfamily.org.
SMTP clients may send messages to recipients at .thestearfamily.org.
SMTP clients may send messages to recipients at tmi.net.
SMTP clients may send messages to recipients at .tmi.net.
SMTP clients may send messages to recipients at trademarkincentives.com.
SMTP clients may send messages to recipients at .trademarkincentives.com.
SMTP clients may send messages to recipients at train.metronet.com.
SMTP clients may send messages to recipients at .train.metronet.com.
SMTP clients may send messages to recipients at trinitypark.com.
SMTP clients may send messages to recipients at .trinitypark.com.
SMTP clients may send messages to recipients at troop57garland.org.
SMTP clients may send messages to recipients at .troop57garland.org.
SMTP clients may send messages to recipients at tve.com.
SMTP clients may send messages to recipients at .tve.com.
SMTP clients may send messages to recipients at txnewsmakers.com.
SMTP clients may send messages to recipients at .txnewsmakers.com.
SMTP clients may send messages to recipients at txtowns.com.
SMTP clients may send messages to recipients at .txtowns.com.
SMTP clients may send messages to recipients at typickett.com.
SMTP clients may send messages to recipients at .typickett.com.
SMTP clients may send messages to recipients at usaci.com.
SMTP clients may send messages to recipients at .usaci.com.
SMTP clients may send messages to recipients at usahelice.com.
SMTP clients may send messages to recipients at .usahelice.com.
SMTP clients may send messages to recipients at uug.metronet.com.
SMTP clients may send messages to recipients at .uug.metronet.com.
SMTP clients may send messages to recipients at valtur.com.
SMTP clients may send messages to recipients at .valtur.com.
SMTP clients may send messages to recipients at veralee.com.
SMTP clients may send messages to recipients at .veralee.com.
SMTP clients may send messages to recipients at veraleegarmentcompany.com.
SMTP clients may send messages to recipients at .veraleegarmentcompany.com.
SMTP clients may send messages to recipients at vinograd.com.
SMTP clients may send messages to recipients at .vinograd.com.
SMTP clients may send messages to recipients at virtvill.com.
SMTP clients may send messages to recipients at .virtvill.com.
SMTP clients may send messages to recipients at visualsimplicity.com.
SMTP clients may send messages to recipients at .visualsimplicity.com.
SMTP clients may send messages to recipients at w3-2.metronet.com.
SMTP clients may send messages to recipients at .w3-2.metronet.com.
SMTP clients may send messages to recipients at w3.metronet.com.
SMTP clients may send messages to recipients at .w3.metronet.com.
SMTP clients may send messages to recipients at w4.metronet.com.
SMTP clients may send messages to recipients at .w4.metronet.com.
SMTP clients may send messages to recipients at w5.metronet.com.
SMTP clients may send messages to recipients at .w5.metronet.com.
SMTP clients may send messages to recipients at w6.metronet.com.
SMTP clients may send messages to recipients at .w6.metronet.com.
SMTP clients may send messages to recipients at weirlaw.com.
SMTP clients may send messages to recipients at .weirlaw.com.
SMTP clients may send messages to recipients at weirlaw.com.
SMTP clients may send messages to recipients at .weirlaw.com.
SMTP clients may send messages to recipients at wf.metronet.com.
SMTP clients may send messages to recipients at .wf.metronet.com.
SMTP clients may send messages to recipients at wfbbs.com.
SMTP clients may send messages to recipients at .wfbbs.com.
SMTP clients may send messages to recipients at wildman-sable.com.
SMTP clients may send messages to recipients at .wildman-sable.com.
SMTP clients may send messages to recipients at wildwire.com.
SMTP clients may send messages to recipients at .wildwire.com.
SMTP clients may send messages to recipients at wildwire.com.
SMTP clients may send messages to recipients at .wildwire.com.
SMTP clients may send messages to recipients at winnsborotx.com.
SMTP clients may send messages to recipients at .winnsborotx.com.
SMTP clients may send messages to recipients at wnew.metronet.com.
SMTP clients may send messages to recipients at .wnew.metronet.com.
SMTP clients may send messages to recipients at www12.metronet.com.
SMTP clients may send messages to recipients at .www12.metronet.com.
SMTP clients may send messages to recipients at www129.metronet.com.
SMTP clients may send messages to recipients at .www129.metronet.com.
SMTP clients may send messages to recipients at www13.metronet.com.
SMTP clients may send messages to recipients at .www13.metronet.com.
SMTP clients may send messages to recipients at www130.metronet.com.
SMTP clients may send messages to recipients at .www130.metronet.com.
SMTP clients may send messages to recipients at www14.metronet.com.
SMTP clients may send messages to recipients at .www14.metronet.com.
SMTP clients may send messages to recipients at www15.metronet.com.
SMTP clients may send messages to recipients at .www15.metronet.com.
SMTP clients may send messages to recipients at www16.metronet.com.
SMTP clients may send messages to recipients at .www16.metronet.com.
SMTP clients may send messages to recipients at www17.metronet.com.
SMTP clients may send messages to recipients at .www17.metronet.com.
SMTP clients may send messages to recipients at www19.metronet.com.
SMTP clients may send messages to recipients at .www19.metronet.com.
SMTP clients may send messages to recipients at www20.metronet.com.
SMTP clients may send messages to recipients at .www20.metronet.com.
SMTP clients may send messages to recipients at www21.metronet.com.
SMTP clients may send messages to recipients at .www21.metronet.com.
SMTP clients may send messages to recipients at www22.metronet.com.
SMTP clients may send messages to recipients at .www22.metronet.com.
SMTP clients may send messages to recipients at www23.metronet.com.
SMTP clients may send messages to recipients at .www23.metronet.com.
SMTP clients may send messages to recipients at www24.metronet.com.
SMTP clients may send messages to recipients at .www24.metronet.com.
SMTP clients may send messages to recipients at www25.metronet.com.
SMTP clients may send messages to recipients at .www25.metronet.com.
SMTP clients may send messages to recipients at www26.metronet.com.
SMTP clients may send messages to recipients at .www26.metronet.com.
SMTP clients may send messages to recipients at www27.metronet.com.
SMTP clients may send messages to recipients at .www27.metronet.com.
SMTP clients may send messages to recipients at www28.metronet.com.
SMTP clients may send messages to recipients at .www28.metronet.com.
SMTP clients may send messages to recipients at www29.metronet.com.
SMTP clients may send messages to recipients at .www29.metronet.com.
SMTP clients may send messages to recipients at www30.metronet.com.
SMTP clients may send messages to recipients at .www30.metronet.com.
SMTP clients may send messages to recipients at www31.metronet.com.
SMTP clients may send messages to recipients at .www31.metronet.com.
SMTP clients may send messages to recipients at www32.metronet.com.
SMTP clients may send messages to recipients at .www32.metronet.com.
SMTP clients may send messages to recipients at www33.metronet.com.
SMTP clients may send messages to recipients at .www33.metronet.com.
SMTP clients may send messages to recipients at www34.metronet.com.
SMTP clients may send messages to recipients at .www34.metronet.com.
SMTP clients may send messages to recipients at www35.metronet.com.
SMTP clients may send messages to recipients at .www35.metronet.com.
SMTP clients may send messages to recipients at www36.metronet.com.
SMTP clients may send messages to recipients at .www36.metronet.com.
SMTP clients may send messages to recipients at www37.metronet.com.
SMTP clients may send messages to recipients at .www37.metronet.com.
SMTP clients may send messages to recipients at www38.metronet.com.
SMTP clients may send messages to recipients at .www38.metronet.com.
SMTP clients may send messages to recipients at www39.metronet.com.
SMTP clients may send messages to recipients at .www39.metronet.com.
SMTP clients may send messages to recipients at www40.metronet.com.
SMTP clients may send messages to recipients at .www40.metronet.com.
SMTP clients may send messages to recipients at www41.metronet.com.
SMTP clients may send messages to recipients at .www41.metronet.com.
SMTP clients may send messages to recipients at www42.metronet.com.
SMTP clients may send messages to recipients at .www42.metronet.com.
SMTP clients may send messages to recipients at www43.metronet.com.
SMTP clients may send messages to recipients at .www43.metronet.com.
SMTP clients may send messages to recipients at www44.metronet.com.
SMTP clients may send messages to recipients at .www44.metronet.com.
SMTP clients may send messages to recipients at www45.metronet.com.
SMTP clients may send messages to recipients at .www45.metronet.com.
SMTP clients may send messages to recipients at www46.metronet.com.
SMTP clients may send messages to recipients at .www46.metronet.com.
SMTP clients may send messages to recipients at www47.metronet.com.
SMTP clients may send messages to recipients at .www47.metronet.com.
SMTP clients may send messages to recipients at www48.metronet.com.
SMTP clients may send messages to recipients at .www48.metronet.com.
SMTP clients may send messages to recipients at www49.metronet.com.
SMTP clients may send messages to recipients at .www49.metronet.com.
SMTP clients may send messages to recipients at www50.metronet.com.
SMTP clients may send messages to recipients at .www50.metronet.com.
SMTP clients may send messages to recipients at www51.metronet.com.
SMTP clients may send messages to recipients at .www51.metronet.com.
SMTP clients may send messages to recipients at www52.metronet.com.
SMTP clients may send messages to recipients at .www52.metronet.com.
SMTP clients may send messages to recipients at www53.metronet.com.
SMTP clients may send messages to recipients at .www53.metronet.com.
SMTP clients may send messages to recipients at www54.metronet.com.
SMTP clients may send messages to recipients at .www54.metronet.com.
SMTP clients may send messages to recipients at www55.metronet.com.
SMTP clients may send messages to recipients at .www55.metronet.com.
SMTP clients may send messages to recipients at www56.metronet.com.
SMTP clients may send messages to recipients at .www56.metronet.com.
SMTP clients may send messages to recipients at www57.metronet.com.
SMTP clients may send messages to recipients at .www57.metronet.com.
SMTP clients may send messages to recipients at www58.metronet.com.
SMTP clients may send messages to recipients at .www58.metronet.com.
SMTP clients may send messages to recipients at www61.metronet.com.
SMTP clients may send messages to recipients at .www61.metronet.com.
SMTP clients may send messages to recipients at www62.metronet.com.
SMTP clients may send messages to recipients at .www62.metronet.com.
SMTP clients may send messages to recipients at www63.metronet.com.
SMTP clients may send messages to recipients at .www63.metronet.com.
SMTP clients may send messages to recipients at www64.metronet.com.
SMTP clients may send messages to recipients at .www64.metronet.com.
SMTP clients may send messages to recipients at www65.metronet.com.
SMTP clients may send messages to recipients at .www65.metronet.com.
SMTP clients may send messages to recipients at www66.metronet.com.
SMTP clients may send messages to recipients at .www66.metronet.com.
SMTP clients may send messages to recipients at www67.metronet.com.
SMTP clients may send messages to recipients at .www67.metronet.com.
SMTP clients may send messages to recipients at www68.metronet.com.
SMTP clients may send messages to recipients at .www68.metronet.com.
SMTP clients may send messages to recipients at www69.metronet.com.
SMTP clients may send messages to recipients at .www69.metronet.com.
SMTP clients may send messages to recipients at www70.metronet.com.
SMTP clients may send messages to recipients at .www70.metronet.com.
SMTP clients may send messages to recipients at www71.metronet.com.
SMTP clients may send messages to recipients at .www71.metronet.com.
SMTP clients may send messages to recipients at www72.metronet.com.
SMTP clients may send messages to recipients at .www72.metronet.com.
SMTP clients may send messages to recipients at www73.metronet.com.
SMTP clients may send messages to recipients at .www73.metronet.com.
SMTP clients may send messages to recipients at www74.metronet.com.
SMTP clients may send messages to recipients at .www74.metronet.com.
SMTP clients may send messages to recipients at www75.metronet.com.
SMTP clients may send messages to recipients at .www75.metronet.com.
SMTP clients may send messages to recipients at www76.metronet.com.
SMTP clients may send messages to recipients at .www76.metronet.com.
SMTP clients may send messages to recipients at www77.metronet.com.
SMTP clients may send messages to recipients at .www77.metronet.com.
SMTP clients may send messages to recipients at www78.metronet.com.
SMTP clients may send messages to recipients at .www78.metronet.com.
SMTP clients may send messages to recipients at www79.metronet.com.
SMTP clients may send messages to recipients at .www79.metronet.com.
SMTP clients may send messages to recipients at www80.metronet.com.
SMTP clients may send messages to recipients at .www80.metronet.com.
SMTP clients may send messages to recipients at www81.metronet.com.
SMTP clients may send messages to recipients at .www81.metronet.com.
SMTP clients may send messages to recipients at www82.metronet.com.
SMTP clients may send messages to recipients at .www82.metronet.com.
SMTP clients may send messages to recipients at www83.metronet.com.
SMTP clients may send messages to recipients at .www83.metronet.com.
SMTP clients may send messages to recipients at www84.metronet.com.
SMTP clients may send messages to recipients at .www84.metronet.com.
SMTP clients may send messages to recipients at www85.metronet.com.
SMTP clients may send messages to recipients at .www85.metronet.com.
SMTP clients may send messages to recipients at www86.metronet.com.
SMTP clients may send messages to recipients at .www86.metronet.com.
SMTP clients may send messages to recipients at www87.metronet.com.
SMTP clients may send messages to recipients at .www87.metronet.com.
SMTP clients may send messages to recipients at www88.metronet.com.
SMTP clients may send messages to recipients at .www88.metronet.com.
SMTP clients may send messages to recipients at www89.metronet.com.
SMTP clients may send messages to recipients at .www89.metronet.com.
SMTP clients may send messages to recipients at www90.metronet.com.
SMTP clients may send messages to recipients at .www90.metronet.com.
SMTP clients may send messages to recipients at www91.metronet.com.
SMTP clients may send messages to recipients at .www91.metronet.com.
SMTP clients may send messages to recipients at www92.metronet.com.
SMTP clients may send messages to recipients at .www92.metronet.com.
SMTP clients may send messages to recipients at www93.metronet.com.
SMTP clients may send messages to recipients at .www93.metronet.com.
SMTP clients may send messages to recipients at www94.metronet.com.
SMTP clients may send messages to recipients at .www94.metronet.com.
SMTP clients may send messages to recipients at www95.metronet.com.
SMTP clients may send messages to recipients at .www95.metronet.com.
SMTP clients may send messages to recipients at www96.metronet.com.
SMTP clients may send messages to recipients at .www96.metronet.com.
SMTP clients may send messages to recipients at www97.metronet.com.
SMTP clients may send messages to recipients at .www97.metronet.com.
SMTP clients may send messages to recipients at www98.metronet.com.
SMTP clients may send messages to recipients at .www98.metronet.com.
SMTP clients may send messages to recipients at www99.metronet.com.
SMTP clients may send messages to recipients at .www99.metronet.com.
SMTP clients may send messages to recipients at abog.org.
SMTP clients may send messages to recipients at .abog.org.
SMTP clients may send messages to recipients at avmaps.com.
SMTP clients may send messages to recipients at .avmaps.com.
SMTP clients may send messages to recipients at bigdmetal.com.
SMTP clients may send messages to recipients at .bigdmetal.com.
SMTP clients may send messages to recipients at cdbargains.com.
SMTP clients may send messages to recipients at .cdbargains.com.
SMTP clients may send messages to recipients at cimarron.net.
SMTP clients may send messages to recipients at .cimarron.net.
SMTP clients may send messages to recipients at city-garage.com.
SMTP clients may send messages to recipients at .city-garage.com.
SMTP clients may send messages to recipients at davidgriffin.com.
SMTP clients may send messages to recipients at .davidgriffin.com.
SMTP clients may send messages to recipients at dfwuug.org.
SMTP clients may send messages to recipients at .dfwuug.org.
SMTP clients may send messages to recipients at dgriffin.com.
SMTP clients may send messages to recipients at .dgriffin.com.
SMTP clients may send messages to recipients at foleygroup.com.
SMTP clients may send messages to recipients at .foleygroup.com.
SMTP clients may send messages to recipients at iedbc.com.
SMTP clients may send messages to recipients at .iedbc.com.
SMTP clients may send messages to recipients at integrityweb.com.
SMTP clients may send messages to recipients at .integrityweb.com.
SMTP clients may send messages to recipients at kids-play-it-safe.com.
SMTP clients may send messages to recipients at .kids-play-it-safe.com.
SMTP clients may send messages to recipients at lightsphere.com.
SMTP clients may send messages to recipients at .lightsphere.com.
SMTP clients may send messages to recipients at markkelly.com.
SMTP clients may send messages to recipients at .markkelly.com.
SMTP clients may send messages to recipients at perlsoftware.com.
SMTP clients may send messages to recipients at .perlsoftware.com.
SMTP clients may send messages to recipients at remtek.com.
SMTP clients may send messages to recipients at .remtek.com.
SMTP clients may send messages to recipients at rlewis.com.
SMTP clients may send messages to recipients at .rlewis.com.
SMTP clients may send messages to recipients at solsticeinc.net.
SMTP clients may send messages to recipients at .solsticeinc.net.
SMTP clients may send messages to recipients at telecomsearch.com.
SMTP clients may send messages to recipients at .telecomsearch.com.
SMTP clients may send messages to recipients at wfbbs.com.
SMTP clients may send messages to recipients at .wfbbs.com.
SMTP clients may send messages to recipients at stanleyremodeling.com.
SMTP clients may send messages to recipients at .stanleyremodeling.com.
morercpthosts: (Default.) No effect.
morercpthosts.cdb: (Default.) No effect.
smtpgreeting: (Default.) SMTP greeting: 220 w4.metronet.com.
smtproutes:
SMTP route: administaff.com:feenix.metronet.com
SMTP route: brinker.com:feenix.metronet.com
SMTP route: cpsgroup.com:feenix.metronet.com
SMTP route: dallas.beasys.com:feenix.metronet.com
SMTP route: earthlink.net:feenix.metronet.com
SMTP route: excite.com:feenix.metronet.com
SMTP route: expanets.com:feenix.metronet.com
SMTP route: hotmail.com:beanix.metronet.com
SMTP route: linuxtoday.com:feenix.metronet.com
SMTP route: mail.utexas.edu:feenix.metronet.com
SMTP route: marcgroup.com:feenix.metronet.com
SMTP route: marcresearch.com:feenix.metronet.com
SMTP route: risd.org:feenix.metronet.com
SMTP route: swanrivercorp.com:feenix.metronet.com
SMTP route: tandy.com:feenix.metronet.com
SMTP route: utexas.edu:feenix.metronet.com
SMTP route: pbs.org:feenix.metronet.com
SMTP route: ttu.edu:feenix.metronet.com
SMTP route: marriot.com:feenix.metronet.com
SMTP route: cpa.state.tx.us:feenix.metronet.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:
Virtual domain: LemonsAndAssociates.com:lemons
Virtual domain: abog.org:examadmn
Virtual domain: aboutcruiseships.com:seahoss
Virtual domain: ads1.com:ads1
Virtual domain: adv-internet-class.com:crb
Virtual domain: advantagesalespromotion.com:mhfinley
Virtual domain: adventyouth.org:pathfind
Virtual domain: aeroglen.com:aeroglen
Virtual domain: air-texelectric.com:icss
Virtual domain: airrite.com:airrite
Virtual domain: alarm.to:straten
Virtual domain: ari-tex.com:icss
Virtual domain: ari-texelectric.com:icss
Virtual domain: ari-texelectric.net:icss
Virtual domain: aromajet.com:mfab
Virtual domain: arts-e-gallery.com:riltec
Virtual domain: aseschool.com:ases
Virtual domain: asesftw.org:ases
Virtual domain: automation.to:straten
Virtual domain: avmaps.com:ads1
Virtual domain: axswave.com:axswave
Virtual domain: aztekts.com:lanzate
Virtual domain: banchang.com:gjjanak
Virtual domain: banchang.net:gjjanak
Virtual domain: banchang.org:gjjanak
Virtual domain: bbbackhoe.com:icss
Virtual domain: be-seen.net:rfry
Virtual domain: beaconstat.com:beacon
Virtual domain: bigdmetal.com:bigdmetl
Virtual domain: blacklandjrt.com:seahoss
Virtual domain: boardcertified-implant.com:alvin
Virtual domain: caddomills.com:ucsa
Virtual domain: campbellcontract.com:brycamp
Virtual domain: carry-safe.com:rwberry
Virtual domain: cartwrightsigns.com:cartwright
Virtual domain: cdbargains.com:zebra
Virtual domain: centuryinspection.com:cii
Virtual domain: chateauprod.com:msds
Virtual domain: chinateapots.com:teapot
Virtual domain: chouteau.tmi.net:chouteau
Virtual domain: cimarron.net:cimarron
Virtual domain: city-garage.com:crking
Virtual domain: claybradfield.com:crb
Virtual domain: club4lovers.com:ads1
Virtual domain: computercrossroads.net:freeman
Virtual domain: cowchip.com:logical
Virtual domain: cramdown.com:dougb
Virtual domain: crossroute.net:freeman
Virtual domain: dallaswebpros.com:dwp
Virtual domain: davidgriffin.com:dgriffin
Virtual domain: davidwebbonline.com:zradio
Virtual domain: designtransport.com:dts
Virtual domain: designtransport.net:dts
Virtual domain: designtransport.org:dts
Virtual domain: dfwlivemusic.com:badkarma
Virtual domain: dfwuug.org:dfwuug
Virtual domain: dfwww.com:dfwww
Virtual domain: dgriffin.com:dgriffin
Virtual domain: dougbedell.com:dougb
Virtual domain: drs.propathlab.com:propath1
Virtual domain: eduserveassociates.com:rcjoshua
Virtual domain: eduserveassociates.net:rcjoshua
Virtual domain: eduserveassociates.org:rcjoshua
Virtual domain: eforest.com:eforest
Virtual domain: electricrc.com:ads1
Virtual domain: elucidata.org:elucidat
Virtual domain: farace.com:dwp
Virtual domain: fnbsachse.com:icss
Virtual domain: foleygroup.com:foley
Virtual domain: foneco.com:foneco
Virtual domain: freemanpos.com:freeman
Virtual domain: fulferandassociates.com:fulfer
Virtual domain: fwmsh.org:fwmsh
Virtual domain: fwmuseum.org:fwmsh
Virtual domain: gallerywall.com:crb
Virtual domain: garlandlittleleague.com:ngll
Virtual domain: globalclothier.com:gjjanak
Virtual domain: gocertified.com:gocert
Virtual domain: goddesssiren.com:cheryl
Virtual domain: granadamovieposters.com:granmp
Virtual domain: granburyoperahouse.org:moody
Virtual domain: greenvilletexas.net:ucsa
Virtual domain: hamstra.org:pathfind
Virtual domain: hartgaugler.com:hganet
Virtual domain: hblawfirm.com:dougb
Virtual domain: hblawfirm.net:dougb
Virtual domain: hcvco.com:cvj
Virtual domain: hornytoadsforever.com:seahoss
Virtual domain: hrnexus.com:hrnexus
Virtual domain: hydro-carbon.net:ads1
Virtual domain: icf-usa.com:sdp
Virtual domain: iedbc.com:chuck
Virtual domain: image2000texas.com:henry
Virtual domain: impact-plano.com:sdp
Virtual domain: informedcustomer.com:rjack
Virtual domain: integrityweb.com:icss
Virtual domain: internet-seminar.com:crb
Virtual domain: jadpc.com:firm
Virtual domain: jasonlapoint.com:henry
Virtual domain: javamug.org:javamug
Virtual domain: jbrousseau.com:dougb
Virtual domain: kennedylicensing.com:kennedy
Virtual domain: kevinmccarthy.com:dougb
Virtual domain: kevinmccarthy.net:dougb
Virtual domain: kevinscoggins.com:kscoggin
Virtual domain: kids-play-it-safe.com:safety
Virtual domain: kryza.com:ftkryza
Virtual domain: laemcharoen.com:gjjanak
Virtual domain: lancastermachine.com:lms
Virtual domain: lanzador.net:lanzate
Virtual domain: leader1.net:ads1
Virtual domain: liturgicalpublishing.com:cvj
Virtual domain: liturgicalservices.com:cvj
Virtual domain: lmis-fw.com:lmisfw
Virtual domain: logical-resources.com:logical
Virtual domain: longviewgas.com:icss
Virtual domain: lozon.com:ljlozon
Virtual domain: lunabiz.com:lunabiz
Virtual domain: maptaphut.com:gjjanak
Virtual domain: maptaphut.net:gjjanak
Virtual domain: maptaphut.org:gjjanak
Virtual domain: mcdavid.com:mcdavid
Virtual domain: mcgrathdesign.com:mmdesign
Virtual domain: metroplexorthopedics.com:chouteau
Virtual domain: microfab.com:mfab
Virtual domain: mixsoftware.com:mixsft
Virtual domain: mr-moody.com:moody
Virtual domain: mxdco.com:rjack
Virtual domain: nsullc.com:nsullc
Virtual domain: natlstaffingunltd.com:njd
Virtual domain: nccj.org:natconf
Virtual domain: nerdburger.com:rfry
Virtual domain: nightlifetalent.com:od
Virtual domain: nordal.com:brad
Virtual domain: northstarpaper.com:nspaper
Virtual domain: octeldesignpartners.com:will
Virtual domain: optimalsuccess.com:dwp
Virtual domain: panache-plus.com:od
Virtual domain: pauli.to:straten
Virtual domain: pcenterprise.com:pcenter
Virtual domain: perlsoftware.com:perlsoft
Virtual domain: persianoutpost.com:persian
Virtual domain: plannersguide.com:plannersg
Virtual domain: planotile.com:kscoggin
Virtual domain: poetryinocean.com:seahoss
Virtual domain: portusa.com:alvin
Virtual domain: prj-cms.com:prjcms
Virtual domain: propathlab.com:propath1
Virtual domain: puttingdeck.com:dougb
Virtual domain: rayong.net:gjjanak
Virtual domain: rayong.org:gjjanak
Virtual domain: rayongbeer.com:gjjanak
Virtual domain: rayongcoffee.com:gjjanak
Virtual domain: rayonggolf.com:gjjanak
Virtual domain: rayongprovince.com:gjjanak
Virtual domain: rayongsearch.com:gjjanak
Virtual domain: readingquote.com:crb
Virtual domain: realtybyrita.com:realty
Virtual domain: remtek.com:ed
Virtual domain: retinafoundation.org:rfsw
Virtual domain: richardsonsymphony.com:mmdesign
Virtual domain: richardsonsymphony.org:mmdesign
Virtual domain: riltec.com:riltec
Virtual domain: rjones.com:brycamp
Virtual domain: rlewis.com:rlewis
Virtual domain: rockwalltexas.net:ucsa
Virtual domain: roughcreek.com:rcreek
Virtual domain: roysecity.com:ucsa
Virtual domain: roysecity.net:ucsa
Virtual domain: roysecity.org:ucsa
Virtual domain: roysecityonline.com:ucsa
Virtual domain: roysecitytx.com:ucsa
Virtual domain: rpmrecords.com:rpmrecor
Virtual domain: safety4children.com:safety
Virtual domain: satellink.com:satellnk
Virtual domain: sd-productions.com:sdp
Virtual domain: seahoss.com:seahoss
Virtual domain: seahoss.org:seahoss
Virtual domain: self-image.com:rjack
Virtual domain: sintezo.com:sintezo
Virtual domain: sltagency.com:sltainc
Virtual domain: smartideas.to:straten
Virtual domain: solstar.com:solstar
Virtual domain: solstar.net:solstar
Virtual domain: solsticeinc.net:solisdn
Virtual domain: special-arrangements.net:henry
Virtual domain: stanleyremodeling.com:seahoss
Virtual domain: stoneagency.com:ucsa
Virtual domain: straten.com:straten
Virtual domain: stunt-show.com:ibidis
Virtual domain: suzannerobertsgifts.com:riltec
Virtual domain: tajrish.com:persian
Virtual domain: takeupyourcross.com:freeman
Virtual domain: tboneinc.com:dougb
Virtual domain: telecomsearch.com:telecom
Virtual domain: texasannouncements.com:henry
Virtual domain: texedol.com:rcjoshua
Virtual domain: texedol.net:rcjoshua
Virtual domain: texedol.org:rcjoshua
Virtual domain: thaiautomate.com:gjjanak
Virtual domain: thaibrew.com:gjjanak
Virtual domain: thaibrewery.com:gjjanak
Virtual domain: thaibrewhouse.com:gjjanak
Virtual domain: thaichem.com:gjjanak
Virtual domain: thaicigar.com:gjjanak
Virtual domain: thaicontrol.com:gjjanak
Virtual domain: thaiemulsion.com:gjjanak
Virtual domain: thaipaint.com:gjjanak
Virtual domain: thaipetro.com:gjjanak
Virtual domain: thaipetrochem.com:gjjanak
Virtual domain: thaiplant.com:gjjanak
Virtual domain: thaipolymer.com:gjjanak
Virtual domain: thaisolar.com:gjjanak
Virtual domain: thaitea.com:gjjanak
Virtual domain: thaiwine.com:gjjanak
Virtual domain: thebilgepumps.com:ibidis
Virtual domain: thebizjet.net:ads1
Virtual domain: thefacilitator.com:fclttr
Virtual domain: theranch.org:pokey
Virtual domain: thestearfamily.org:buds
Virtual domain: trademarkincentives.com:icss
Virtual domain: trinitypark.com:henry
Virtual domain: troop57garland.org:logical
Virtual domain: txnewsmakers.com:crb
Virtual domain: txtowns.com:crb
Virtual domain: usahelice.com:wildwire
Virtual domain: uug.metronet.com:dfwuug
Virtual domain: veralee.com:henry
Virtual domain: veraleegarmentcompany.com:henry
Virtual domain: visualsimplicity.com:capture
Virtual domain: weirlaw.com:wpw
Virtual domain: wf.metronet.com:phas
Virtual domain: wfbbs.com:phas
Virtual domain: wildwire.com:wildwire
Virtual domain: winnsborotx.com:ucsa
OLD: I have no idea what this file does.
tochg: I have no idea what this file does.
relayclients: I have no idea what this file does.
bad: I have no idea what this file does.
me~: I have no idea what this file does.
chgs: I have no idea what this file does.
virtualdomains~: I have no idea what this file does.
rcpthosts~: I have no idea what this file does.
smtproutes.b4: I have no idea what this file does.
w4:/tmp# tail ~adm/messages
Nov 1 00:47:45 w6 qmail: 973061265.664999 delivery 15: success: did_1+0+0/
Nov 1 00:47:45 w6 qmail: 973061265.665047 status: local 2/25 remote 6/30
Nov 1 00:47:45 w6 qmail: 973061265.665090 new msg 179521
Nov 1 00:47:45 w6 qmail: 973061265.685865 info msg 179521: bytes 1520 from
<[EMAIL PROTECTED]> qp 26917 uid 1006
Nov 1 00:47:45 w6 qmail: 973061265.705228 end msg 176587
Nov 1 00:47:45 w6 qmail: 973061265.705872 new msg 179590
Nov 1 00:47:45 w6 qmail: 973061265.746007 info msg 179590: bytes 14253 from
<[EMAIL PROTECTED]> qp 32081 uid 1006
Nov 1 00:47:45 w6 qmail: 973061265.772952 starting delivery 19: msg 176591 to local
[EMAIL PROTECTED]
Nov 1 00:47:45 w6 qmail: 973061265.773134 status: local 3/25 remote 6/30
Nov 1 00:47:45 w6 qmail: 973061265.773492 delivery 17: failure:
Sorry,_I_couldn't_find_any_host_by_that_name._(#4.1.2)/I'm_not_going_to_try_again;_this_message_has_been_in_the_queue_too_long./
w4:/tmp# tail ~adm/messages[8D[Kdebug
Nov 1 00:46:03 w6 identd[11268]: Successful lookup: 1939 , 21 : root.root
Nov 1 00:46:04 w6 identd[11346]: Successful lookup: 1949 , 21 : root.root
Nov 1 00:46:05 w6 identd[11361]: Successful lookup: 1951 , 25 : root.root
Nov 1 00:46:06 w6 identd[11420]: Successful lookup: 1958 , 21 : root.root
Nov 1 00:46:07 w6 identd[11435]: Successful lookup: 1960 , 25 : root.root
Nov 1 00:46:11 w6 identd[11628]: Successful lookup: 1982 , 21 : root.root
Nov 1 00:46:12 w6 identd[11629]: Successful lookup: 1982 , 21 : root.root
Nov 1 00:46:12 w6 identd[11645]: Successful lookup: 1985 , 25 : root.root
Nov 1 00:46:12 w6 identd[11701]: Successful lookup: 1989 , 21 : root.root
Nov 1 00:46:13 w6 identd[11717]: Successful lookup: 1992 , 25 : root.root
w4:/tmp# tail ~adm/debug[5D[Ksyslog
Nov 1 00:48:25 w6 qmail: 973061305.772190 alert: unable to append to bounce message;
HELP! sleeping...
Nov 1 00:48:35 w6 qmail: 973061315.772210 alert: unable to append to bounce message;
HELP! sleeping...
Nov 1 00:48:45 w6 qmail: 973061325.772191 alert: unable to append to bounce message;
HELP! sleeping...
Nov 1 00:48:55 w6 qmail: 973061335.772188 alert: unable to append to bounce message;
HELP! sleeping...
Nov 1 00:49:05 w6 qmail: 973061345.772195 alert: unable to append to bounce message;
HELP! sleeping...
Nov 1 00:49:15 w6 qmail: 973061355.772189 alert: unable to append to bounce message;
HELP! sleeping...
Nov 1 00:49:25 w6 qmail: 973061365.772191 alert: unable to append to bounce message;
HELP! sleeping...
Nov 1 00:49:35 w6 qmail: 973061375.772203 alert: unable to append to bounce message;
HELP! sleeping...
Nov 1 00:49:45 w6 qmail: 973061385.772192 alert: unable to append to bounce message;
HELP! sleeping...
Nov 1 00:49:55 w6 qmail: 973061395.772199 alert: unable to append to bounce message;
HELP! sleeping...
w4:/tmp# ^Dexit
Script done on Wed Nov 1 00:50:01 2000
Steve Linebarger, Texas Metronet, 12200 Ford rd, Suite 170, Dallas Tx, 75234
[EMAIL PROTECTED]
Vmail 972-705-2900 fax: 972-484-2173 Office: 972-488-2170
beep: 214/332-0448 Home1: 972-857-2368 Home2: 972-488-8566
Cell: 972-478-2269 alt pager 800-420-0572
http://www.metronet.com/~s (send me a cell phone/SMS text message)
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
I have a question about .qmail file.
I want to leaf the mails in local Mailbox and also deliver to some other
addresses. I setup the following lines in .qmail under my home directory,
alan@localhost
[EMAIL PROTECTED]
It delivered mails to [EMAIL PROTECTED] but not leaving any mails
locally. So I ends up without any mail while checking. I even tried real
domain name (which is the domain name of the mail server, also is the local
host), but got the below error message,
This message is looping: it already has my Delivered-To line. (#5.4.6)
How do I perform this?
Any idea?
Alan
Hi,
is there a good tutorial to install the qmail-scanner. The page linked in qmail.org
contents only the requirements and the patch QMAILQUEUE. By replacing
qmail-queue after the lines mentioned in the page the setup stops with an
error that it could not find QMAILQUEUE.
Which files must to be edit to find QMAILQUEUE?
Is there a good virusscanner based on Linux for qmail (good if it easy to
install)?
Regards,
Ruprecht
