
kyle-qmail at memoryhole
Nov 30, 2009, 7:55 AM
Post #6 of 6
(1426 views)
Permalink
|
|
Re: I cannot send mail from one of my internal hosts to another one
[In reply to]
|
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Sunday, November 29 at 08:26 PM, quoth dihewo [at] gmx: >> Well, what do your logs say? >I just did a > qmail-inject -fsender [at] my recipient [at] remote >recipient [at] my < /dev/shm/testmail.eml > > and the log is the following: Okay... The problem you originally described was that messages to hosts on your internal network would not be delivered if you had the authentication information for your ISP in place, but that (obviously) messages destined outside of your internal network that had to go through your ISP could not be delivered if you didn't have that information in place. Which of those two situations was the case for this test? Which of these recipients is destined for another host on your internal network? > Nov 29 20:07:51 fw qmail: 1259521671.062669 new msg 3288 >Nov 29 20:07:51 fw qmail: 1259521671.063845 info msg 3288: bytes 390 from ><sender [at] my> qp 13668 uid 0 >Nov 29 20:07:51 fw qmail: 1259521671.232167 starting delivery 150: msg 3288 >to local recipient [at] my >Nov 29 20:07:51 fw qmail: 1259521671.233688 status: local 1/10 remote 0/2 >Nov 29 20:07:51 fw qmail: 1259521671.235445 starting delivery 151: msg 3288 >to remote recpient [at] remote >Nov 29 20:07:51 fw qmail: 1259521671.236594 status: local 1/10 remote 1/20 >Nov 29 20:07:51 fw qmail: 1259521671.776654 delivery 150: success: >did_1+0+0/ This says that the message was successfully delivered *locally* (using qmail-local, which is to say, not via the network) to recipient [at] my >Nov 29 20:07:51 fw qmail: 1259521671.781868 status: local 0/10 remote 1/20 >Nov 29 20:07:52 fw qmail: 1259521672.129374 delivery 151: success: >www.xxx.yyy.zzz./Remote_host_said:_250_2.0.0_Ok:_queued_as_03EC348067/ >Nov 29 20:07:52 fw qmail: 1259521672.133025 status: local 0/10 remote 0/20 >Nov 29 20:07:52 fw qmail: 1259521672.134493 end msg 3288 And this says that the message was successfully delivered remotely to what I assume is your ISP. These logs show two successful deliveries, and therefore, no problem. Did either of these messages not get to where it was supposed to go? What problem occurred in this test? >> My next guess would be that qmail is attempting to authenticate to the >> internal hosts. Since those hosts do not understand the authentication >> commands, perhaps those connections are being marked as errors. I >> don't know which authentication patch you're using, but perhaps you >> need to tell it to ignore authentication for your internal hosts. >Shouldn't there be any error message, if that occurs. Yes, there should be an error message of some kind if that occurs. >> If that's true, then your logs should indicate that delivery (to >> your >> internal hosts) was attempted but failed. >As you can see, there is no single error message currently. If there's no error message, then as far as your server knows, the deliveries occurred successfully. Do the recipients receive these messages? Are the messages simply disappearing? Do you get bounce messages? What are you seeing that illustrates the problem? ~Kyle - -- The greatest thing in family life is to take a hint when a hint is intended---and not to take a hint when a hint isn't intended. -- Robert Frost -----BEGIN PGP SIGNATURE----- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLE+sAAAoJECuveozR/AWeofYQAK9RaUxlN0D/Dqqm3a03VbMj 0jIT0KHF7wPocmTCRGzZaH2CEJ4kw619fDA9BF7QWawY59ooSPQYi4YUfW7AAWTq u7YC4Gyx8F7I1gIQvCfRMxcJaetuUijq74IMdWeCR8PKD37FiSK/mhGeFah/x01T OMLueHHMkmuI4M6JbSl/VmhSicGmEzgLKCn5Vfz8AJhhs+A/2lv5NFk5gQeC6ZfN aq+Cseh+D8Le0xrTw5cYfR2GK3SyNrrK4MTDplHn4uZeR5YYlYkvBbw1rS0m7TZC +WTwb5QPdLckyRyljQQme7G0xM4YASHG/vhMdG2fyW4FG0xmGMZMf/Ty8Xil3hT0 WhPx8CtP+UI2AhoRo8de4xSaZs13SoB/fLWuNXrgxLPAMIwgfJ0LPgVwKsIesube q/XeDXLB+LtOyUx0HPrMXJaJdoh/QOi0WT8+3Rd5s7pfPNBMfBFdBlfHOwQgoXiy 5x2CuccAc54cY1V+G2jTHhbHKEIKM5hoM59RcRVzwCrBvBma/g11NSceicSoXiWZ tBDP5GDMXc9Oz6wZd8TNZEPCGGnLhisyemwxzPSG4DRQZEyCHaEbMb80H8xHDGha K21OMR6S4M5BwcwcWkE3C4YPva5HeqYjiAEwqXDhjahLAq3YnlONxXTCVciLnOLp kpF5Buxmt23f1pTYgawD =EcK6 -----END PGP SIGNATURE-----
|