[xmail] Re: Strange error after upgrade
-Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Davide Libenzi Envoy=E9 : vendredi 25 mai 2007 02:54 =C0 : xmail@xmailserver.org Objet : [xmail] Re: Strange error after upgrade On Thu, 24 May 2007, Edinilson - ATINET wrote: Davide, I think so because these clients do not called us=20 about this error=20 before migration. =20 Some behavior was changed in server.tab about smtp=20 authentication (I don=B4t=20 found nothing that could lead to these errors reading changelog) ? Your SMTP logs should tell you if it was XMail... - Davide Yes, and smail logs too if outgoing mails out off xmail handled domains This will show that xmail really tried to send out. Question : did you get the ndr message from your customers as attached = file to keep it's smtp headers intact ? Then study the ndr smtp headers to see the original mta sending it and = it's route (Receveived by). That will help you convince the customer that = it's not your xmail serve that refuse to relay :) Francis - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Strange error after upgrade
OK, thanks Davide and Clement. I will catalog some logs (smtp and slog) and report if I found something strange. Edinilson - ATINET-Professional Web Hosting Tel Voz: (0xx11) 4412-0876 http://www.atinet.com.br - Original Message - From: CLEMENT Francis [EMAIL PROTECTED] To: xmail@xmailserver.org Sent: Friday, May 25, 2007 3:46 AM Subject: [xmail] Re: Strange error after upgrade -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Davide Libenzi Envoy=E9 : vendredi 25 mai 2007 02:54 =C0 : xmail@xmailserver.org Objet : [xmail] Re: Strange error after upgrade On Thu, 24 May 2007, Edinilson - ATINET wrote: Davide, I think so because these clients do not called us=20 about this error=20 before migration. =20 Some behavior was changed in server.tab about smtp=20 authentication (I don=B4t=20 found nothing that could lead to these errors reading changelog) ? Your SMTP logs should tell you if it was XMail... - Davide Yes, and smail logs too if outgoing mails out off xmail handled domains This will show that xmail really tried to send out. Question : did you get the ndr message from your customers as attached = file to keep it's smtp headers intact ? Then study the ndr smtp headers to see the original mta sending it and = it's route (Receveived by). That will help you convince the customer that = it's not your xmail serve that refuse to relay :) Francis - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Strange error after upgrade
-Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Edinilson - ATINET Envoy=E9 : vendredi 25 mai 2007 16:02 =C0 : xmail@xmailserver.org Objet : [xmail] Re: Strange error after upgrade OK, thanks Davide and Clement. I will catalog some logs (smtp and slog) and report if I found=20 something=20 strange. Edinilson - ATINET-Professional Web Hosting Tel Voz: (0xx11) 4412-0876 http://www.atinet.com.br As the 'bad' server is not your Xmail, the xmail logs will only say to = you if the mail was 'routed' or not by your xmail and the 'bad' side = (before your xmail or minimum second hop after it). The NDR headers will give = you the last successfull hop. I really think that getting the complete NDR message (headers included) = is important as it will give you the name of the ndr sending server, so = the last server that successfully received the original mail. And if this server is not the last customer server/firwall/security appliance/... just before your xmail server, the problem is not your = xmail server (Davide allready proved it by the 'Relay denied' message 'case', = but it's more 'by chance' that the reason is different ...). PS : Remember that the 'relay' problem can be before your xmail server :) As an example : the sending customer send to an internal server, = chained or not with other internal servers, then routed to a security and control appliance server, a firewall, a proxy, ..., then finaly the last mail gateway in customer network send to your xmail for Internet delivery. = In this case, the only way to find the culprit is the complete NDR = message. Francis - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Relocate .pid file on *BSD
Hi, is there a way to relocate the XMail.pid file from /var/run to another location ? This would allow to use XMail as e.g. a proxy with user rights only, startable from a simple script - all files in a single folder. -- Harald - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Relocate .pid file on *BSD
Hi Harald -
It's all about the startup script on *BSD. There is no standard package
for Xmail (something I have thought about setting up numerous times) in
FreeBSD, so modifying a default template is not an issue. I place my
custom startup script in /usr/local/etc/rc.d - I believe this is at
least somewhat similar in the other *BSDs. It specifiers the location
of the .pid file - here is the script I use, pidfile being declared
explicitly:
#!/bin/sh
#
# $FreeBSD: XMail - non-standard port
#
# PROVIDE: xmail
#
# Add the fellowing line to /etc/rc.conf.local or /etc/rc.conf
# to enable xmail
#
# xmail_enable (bool):Set it to YES to enable
.. /etc/rc.subr
MAIL_ROOT=/server/MailRoot
export MAIL_ROOT
name=xmail
rcvar=`set_rcvar`
command=${MAIL_ROOT}/bin/XMail
command_args=-B- -W- -X- -F- -Ms /server/MailRoot -MM -Qr 50 -Ql -Pl
-Sl -SI 127.0.0.1:25 -Ll -Mr 240 -Sr 300
pidfile=/var/run/XMail.pid
sig_stop=-kill $pidfile
# read configuration and set defaults
load_rc_config $name
: ${xmail_enable=NO}
run_rc_command $1
I hope that helps!
Jeff
Harald Schneider wrote:
Hi,
is there a way to relocate the XMail.pid file from /var/run to another
location ?
This would allow to use XMail as e.g. a proxy with user rights only,
startable from a simple script - all files in a single folder.
-- Harald
-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]
