Re: Installed test/production e-mail stopped working

surgemail-listnetwinsite.com wrote:
> Surgemail was recommended as a replacement for our
existing sendmail so I installed it as a test system.  
> 
> Unfortunately this is a remotely managed server and I
cannot open the internal LAN for access to port 7026 on the
test machine.  I need to be able to configure it manually
through the command line and not the browser interface. 
Does anyone know the file name that conatins the g_ type of
configuration?
> 

surgemail.ini in /etc or the windows directory.

> Also, I have a ***serious*** problem.  This server uses
e-mail (outgoing) to notify users of automated process
results.   The existing 'sendmail' accounts are not being
recognized and so e-mail turnarounds on 127.0.0.1 are not
available.  This is a crucial problem!  I need to find out
how to add a user through the command line pdq!
> 

tellmail add_user userdomain

SurgeMail uses its own user database by default (nwauth) so
yes it won't 
be recognising existing accounts as it doesn't know about
them.


> Finally, it appears that the Surgemail server is
interfering with incoming e-mail on the production mail
server on the same LAN.  How do I get Surgemail to send but
not receive mail except from port 127.0.0.1?
> 

I'm not sure what you mean here....I assume you mean you
only want it to 
bind to one ip on the server?

SurgeMail binds to all ip's on the machines interface, you
can make it 
bind to one ip by setting

g_smtp_port "ip:25"

You will need to stop and restart it..

Regards,
Stuart


> Regards,
> 
> John


-- 
When replying please quote original message to save time and
always let
us know what OS and version of SurgeMail you are using.

************************************************************
****************
If you wish to communicate with other users and talk about
SurgeMail and
also get news about updates etc then join the SurgeMail
List.
Send an email to surgemail-list-requestnetwinsite.com with only 
"subscribe" in the message body

FAQ - http
://www.netwinsite.com/surgemail/help/faq.htm
************************************************************
**************** 

surgemail-listnetwinsite.com wrote:
> SurgeMail Support <surgemail-supportnetwinsite.com> wrote:
> Thanks very much for the prompt response.
> 
> OK, I didn't write it very clearly.  Guess panic is
setting in!
> 
> here's what I have done and the problems that
resulted:
> 
> 1) installed SM last Saturday and as expected it
replaced 'sendmail' on the same machine.  This is a
automated production/test server on the internal LAN.  
> 
> 2) the server notifies various users by sending out
e-mails and attachment files.  This seems to work IF the
receiving mail system accepts the mail.  If not, then the
normal bounces do not come back - ie I type 'mail' at the
command line and get "No mail for John".
Previously I would have got the error back.  
>


This depends on the mail command line client giving the
correct return 
address. The trick for this is to ensure the user in
question exists in 
surgemail's primary (first) domain. Then if it still fails
examine 
msg*.rec to see what surgemail does with the bounce and
why.



> 3) system generated messages, one example would be the
'cron' reports for auto batch runs, do not turn up in the
user's mail.  
> 

Again, check msg*.rec to see  why the message is rejected or
not delivered.

> 4) I have added all the users using 'tellmail' and the
domain 'mail.rac.ca' which is the domain I set it up for. 
This is NOT the domain of the production mail server on the
same LAN.  If I try to alias the users to send to their
'real' mailboxes, then I get an 'invalid domain' message
from tellmail.  As an example, I try this command: 'tellmail
add_user_alias john john.iliffesympatico.ca' and the
response is 'Failed alias not added (Alias john.iliffesympatico.ca) does not match a valid domain.  It
should, this is my 'real' e-mail address. 
> 

This command creates a local alias for a locally existing
user, so it's 
for redirecting email to a local account, it seems you want
to redirect 
email for a local account to a remote account, so instead
use 
surgemail.ini and add a rule like this in the appropriate
domain section
	redirect was="john" to="john.iliffesympatico.ca"

> 5) our domain is 'rac.ca' but the mail.log shows that
some incoming messages are being grabbed by Surgemail and
rejected as 'no such user'.   (Port 25 traffic on the LAN is
not directed to a specific server).  I never had this
problem with 'sendmail'.   The production server is handling
about 4000 e-mails/day and about 10 a day get caught, based
on 3 days observations.
> 

This sounds like these are messages sent to the wrong
server, the simple 
solution is to configure surgemail so it will forward email
for that 
domain to the real server, add this rule to surgemail.ini in
the global 
settings:

	g_relay_to "rac.ca"

or if you need to tell surgemail the actual host name or ip
address of 
the email server use:
	g_gateway domain="rac.ca"
to="smtp.rac.ca" 	

Regards,
Stuart

> I think that I have a major misunderstanding of how
this should work but I haven't figured out what I did
wrong!
> 
> Regards,
> 
> John
> 
> 
> 
> 
> 
> 
> 


-- 
When replying please quote original message to save time and
always let
us know what OS and version of SurgeMail you are using.

************************************************************
****************
If you wish to communicate with other users and talk about
SurgeMail and
also get news about updates etc then join the SurgeMail
List.
Send an email to surgemail-list-requestnetwinsite.com with only 
"subscribe" in the message body

FAQ - http
://www.netwinsite.com/surgemail/help/faq.htm
************************************************************
**************** 

Just wanted to chime in real quick here. I think one of the
issues is that John is expecting Surgemail to store the
email in the standard location for email on the mail
server... where sendmail would store it. Users could then
just check their mail with the mail command. I think now
because Surgemail is there, you would need to use a
POP3/IMAP client to access the email which is stored in a
new location. The mail program is not picking up on this as
it's just looking in a directory that it is expecting mail
to be in. This is just a guess... 

SurgeMail Support wrote:
> 
> 
> surgemail-listnetwinsite.com wrote:
>> SurgeMail Support <surgemail-supportnetwinsite.com> wrote:
>> Thanks very much for the prompt response.
>>
>> OK, I didn't write it very clearly.  Guess panic is
setting in!
>>
>> here's what I have done and the problems that
resulted:
>>
>> 1) installed SM last Saturday and as expected it
replaced 'sendmail'
>> on the same machine.  This is a automated
production/test server on
>> the internal LAN. 
>> 2) the server notifies various users by sending out
e-mails and
>> attachment files.  This seems to work IF the
receiving mail system
>> accepts the mail.  If not, then the normal bounces
do not come back -
>> ie I type 'mail' at the command line and get
"No mail for John".
>> Previously I would have got the error back. 
> 
> 
> This depends on the mail command line client giving the
correct return
> address. The trick for this is to ensure the user in
question exists in
> surgemail's primary (first) domain. Then if it still
fails examine
> msg*.rec to see what surgemail does with the bounce and
why.
> 
> 
> 
>> 3) system generated messages, one example would be
the 'cron' reports
>> for auto batch runs, do not turn up in the user's
mail. 
> 
> Again, check msg*.rec to see  why the message is
rejected or not delivered.
> 
>> 4) I have added all the users using 'tellmail' and
the domain
>> 'mail.rac.ca' which is the domain I set it up for. 
This is NOT the
>> domain of the production mail server on the same
LAN.  If I try to
>> alias the users to send to their 'real' mailboxes,
then I get an
>> 'invalid domain' message from tellmail.  As an
example, I try this
>> command: 'tellmail add_user_alias john
john.iliffesympatico.ca' and
>> the response is 'Failed alias not added (Alias
>> john.iliffesympatico.ca) does not match a valid
domain.  It should,
>> this is my 'real' e-mail address.
> 
> This command creates a local alias for a locally
existing user, so it's
> for redirecting email to a local account, it seems you
want to redirect
> email for a local account to a remote account, so
instead use
> surgemail.ini and add a rule like this in the
appropriate
> domain section
>     redirect was="john"
to="john.iliffesympatico.ca"
> 
>> 5) our domain is 'rac.ca' but the mail.log shows
that some incoming
>> messages are being grabbed by Surgemail and
rejected as 'no such
>> user'.   (Port 25 traffic on the LAN is not
directed to a specific
>> server).  I never had this problem with 'sendmail'.
  The production
>> server is handling about 4000 e-mails/day and about
10 a day get
>> caught, based on 3 days observations.
>>
> 
> This sounds like these are messages sent to the wrong
server, the simple
> solution is to configure surgemail so it will forward
email for that
> domain to the real server, add this rule to
surgemail.ini in the global
> settings:
> 
>     g_relay_to "rac.ca"
> 
> or if you need to tell surgemail the actual host name
or ip address of
> the email server use:
>     g_gateway domain="rac.ca"
to="smtp.rac.ca"    
> 
> Regards,
> Stuart
> 
>> I think that I have a major misunderstanding of how
this should work
>> but I haven't figured out what I did wrong!
>>
>> Regards,
>>
>> John
>>
>>
>>
>>
>>
>>
>>
> 
> 

-- 

Vinny Abello
Network Engineer
vinnytellurian.com
(973)940-6100 (NOC)
PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0  E935 5325
FBCB 0100 977A

Tellurian Networks - The Ultimate Internet Connection
http://www.tellurian.com
(888)TELLURIAN

"There is no objective reality. Only that which is
measured exists.
We construct reality, and only in the moment of measurement
or observation." -- Niels Bohr