On 16 Jul 2002, Aaron Johnson wrote:
> > On Tue, 2002-07-16 at 19:45, Davide Libenzi wrote: > > > > On 16 Jul 2002, Aaron Johnson wrote: > > > > > > > > On Tue, 2002-07-16 at 14:43, Aaron Johnson wrote: > > > > > > > > On Tue, 2002-07-16 at 12:15, Davide Libenzi wrote: > > > > > > > > > > On 16 Jul 2002, Aaron Johnson wrote: > > > > > > > > > > > > > > > > > On Tue, 2002-07-16 at 12:02, Davide Libenzi wrote: > > > > > > [snip] > > > > > > > > > > > > > > are you sure the XMail machine upon which the redirect is setup is able >to > > > > > > > talk to the redirect target ? > > > > > > > > > > > > > > > > > > > > > > > > > > That seems to be where my admin skills are lacking. I have used > > > > > > nslookup in the past, but I have never worked in a masqueraded > > > > > > environment so I am not sure what it should return or what tools would > > > > > > be better suited for diagnosing the cause of the problem. > > > > > > > > > > > > I realize now this problem is not directly XMail related, but more a > > > > > > network setup issue, any information ( even a URL ) as to where to learn > > > > > > more would be helpful. > > > > > > > > > > try to simulate an smtp session from the XMail machine to the redirect > > > > > target machine > > > > > > > > > > > > > > > > > > I used some scripts to assign the SMTP server for sending the emails and > > > > all of them worked correctly and worked through the SMTP server. > > > > > > > > Here is the output from the Debug: > > > > > > > > MIME::Lite::SMTP=GLOB(0x83158e4)<<< 220 > > > > <[EMAIL PROTECTED]> [XMail 1.9 (Linux/Ix86) > > > > ESMTP Server] service ready; Tue, 16 Jul 2002 14:14:17 -0400 > > > > MIME::Lite::SMTP=GLOB(0x83158e4)>>> EHLO localhost.localdomain > > > > MIME::Lite::SMTP=GLOB(0x83158e4)<<< 250-xmailserver.test > > > > MIME::Lite::SMTP=GLOB(0x83158e4)<<< 250-VRFY > > > > MIME::Lite::SMTP=GLOB(0x83158e4)<<< 250-ETRN > > > > MIME::Lite::SMTP=GLOB(0x83158e4)<<< 250-8BITMIME > > > > MIME::Lite::SMTP=GLOB(0x83158e4)<<< 250-PIPELINING > > > > MIME::Lite::SMTP=GLOB(0x83158e4)<<< 250-AUTH LOGIN PLAIN CRAM-MD5 > > > > MIME::Lite::SMTP=GLOB(0x83158e4)<<< 250 SIZE > > > > > > > > The server it was directed to go through was not the pointofcaretest so > > > > I assuming that XMail resolved to the correct server. > > > > > > > > Aaron > > > > > > > > > > I added another user and had it redirect to my account (outside of the > > > server involved) and everything worked fine. Could it be an MX record > > > conflict causing the problem with the other address? I say this because > > > the other redirected mail is attempting to go to a domain that is > > > controlled with in the same local (192.168) IP loop. > > > > the fact that the domain is handled by the server itself does not imply > > automatically a mail loop. > > > Thank you for your patience/persistence on this Davide. > > I didn't state that very well previously. I am not saying there is a > mail loop, but rather that an MX record/server on the LAN could be > effecting the ability to deliver to certain domains that exist in that > same LAN, but on different servers. > > The redirect is attempting to send a message to a server that is on the > same LAN, those messages are received on the other end. Internal > redirect between sites controlled by the XMail server and ones to > domains outside of the LAN are allowed. > > Another oddity is that the XMail SMTP log show successful deliver to the > LAN address, when in fact they are not being sent. A grep through the > spool revealed the initial -471 error. delivery is logged inside smail logs, not smtp > I don't think there is any long term issue because all domains will be > hosted on the single server once correct function of the XMail server > can be verified. I have run XMail on other servers for the last two > years and not had any issue similar to this, but in none of the other > cases was a LAN IP address involved, so it is possible I am just > focusing on the unfamiliar and don't see the real issue that is clogging > up the works, but I don't want to commit to moving 20 odd domains if > there is a possibility one or more won't work. try to use smtprelay instead of redirect - Davide - 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]
