| View previous topic :: View next topic |
| Author |
Message |
Vogateer
n00b
Joined: 27 Jul 2004
Posts: 49
Location: Oklahoma
|
 Posted: Wed Jan 26, 2005 8:56 pm Post subject: Pine messages not relayed, Postfix, Courier-IMAP, Cyrus-SASL |
 |
|
I recently followed the splendid Email System For The Home Network - Version 2.1 guide, and I am able to access the imap folders from any client I choose. I cannot, however, send mail with pine. I can send e-mail through the server just fine using Sylpheed-Claws, and that e-mail is relayed through my ISP's server, arriving at its destination as expected. When I attempt to send an email with pine, it seems that it does not get forwarded through my ISP, and just ends up in my mailq, going nowhere.
All settings were copied directly from the guide, except for a few little things like the name of my server and location. I have tried several different settings for the smtp server in pine, usually something like:
smtp-server=192.168.1.5/username=vogateer/tls
Using the "novalidate-cert" option or naming the server by it's local name has no effect, either.
I can find very little difference in the logs between the mail sent by pine and Sylpheed-Claws, as seen below in what I believe to be the relevant information:
| Code: | Jan 25 23:27:05 [postfix/smtpd] 0030 e0 48 6a 5d b8 6a 56 52|0b bc 54 .Hj].jVR ..T
Jan 25 23:27:05 [postfix/smtpd] SSL_accept:SSLv3 flush data
Jan 25 23:27:05 [postfix/smtpd] TLS connection established from (mailserver name)[192.168.1.10]: TLSv
1 with cipher DHE-RSA-AES256-SHA (256/256 bits)
Jan 25 23:27:07 [postfix/smtpd] 26C165A743: client=(client computer name)[192.168.1.10], sasl_method=LOGIN
, sasl_username=vogateer
Jan 25 23:27:07 [postfix/cleanup] 26C165A743: message-id=<20050125232614.0bc0141c@(client computer name)>
Jan 25 23:27:07 [postfix/smtpd] disconnect from (client computer name)[192.168.1.10]
Jan 25 23:27:07 [postfix/qmgr] 26C165A743: from=<(myemail@somewhere.net)>, size=730, nrcpt=1 (queue active)
Jan 25 23:27:08 [postfix/smtp] 26C165A743: to=<(someone_else@somewhere.net)>, relay=mail.okccu.edu[66.210.186.139], delay
=2, status=sent (250 2.6.0 <20050125232614.0bc0141c@(client computer name)> Queued mail for delivery)
Jan 25 23:27:08 [postfix/qmgr] 26C165A743: removed
Jan 25 23:27:19 [imapd-ssl] Unexpected SSL connection shutdown.
Jan 25 23:27:19 [imapd-ssl] DISCONNECTED, user=vogateer, ip=[192.168.1.10], headers=10071, body=321651, time=112
, starttls=1 |
Log for non-working pine setup:
| Code: | Jan 26 12:45:54 [postfix/smtpd] 0030 dd 3f 0b 96 90 d8 3b 7a|8e 43 ea .?....;z .C.
Jan 26 12:45:54 [postfix/smtpd] SSL_accept:SSLv3 flush data
Jan 26 12:45:54 [postfix/smtpd] TLS connection established from (client computer name)[192.168.1.10]: TLSv
1 with cipher DHE-RSA-AES256-SHA (256/256 bits)
Jan 26 12:45:55 [postfix/smtpd] 76E475A714: client=(client computer name)[192.168.1.10], sasl_method=LOGIN
, sasl_username=vogateer
Jan 26 12:45:55 [postfix/cleanup] 76E475A714: message-id=<Pine.LNX.4.61.0501261240240.16031@(client computer name)>
Jan 26 12:45:55 [postfix/smtpd] disconnect from (client computer name)[192.168.1.10]
Jan 26 12:45:56 [postfix/qmgr] 76E475A714: from=<(myemail@somewhere.net)>, size=660, nrcpt=1 (queue active)
Jan 26 12:46:21 [postfix/postsuper] 76E475A714: removed
Jan 26 12:46:21 [postfix/postsuper] Deleted: 1 message
Jan 26 12:46:27 [postfix/smtp] connect to smtp1.somwhereelse.com[204.44.11.8]: Connection timed out (port 25)
Jan 26 12:46:57 [postfix/smtp] connect to smtp3.somwhereelse.com[204.44.11.11]: Connection timed out (port 25)
Jan 26 12:46:58 [postfix/smtp] 76E475A714: to=<someone_else@somewhere.net>, relay=none, delay=63, status=deferred (connect to smtp3.somewhereelse.com[204.xxx.xx.xx]: Connection timed out)
Jan 26 12:46:58 [postfix/qmgr] warning: qmgr_active_corrupt: save corrupt file queue active id 76E475A714: No
such file or directory
|
The differences seem to begin on the line where, in the working part, one sees:
[postfix/smtp] .... to=<someone_else@somewhereelse.com>
while in the non-working (pine) part, it reads:
[postfix/smtp] .... connect to smtp1.somewhereelse.com[204.xxx.xx.xx]: Connection timed out (Port 25)
Perhaps I missed something earlier in the logs, or perhaps I'm looking in the wrong place, but I can't find anything telling me why sylpheed's sent mail is relayed to my ISP while pine's sent mail is not. Just to warn anyone reading, I am a newbie, so there's a good chance I'm doing something stupid.
Last edited by Vogateer on Wed Jan 26, 2005 9:16 pm; edited 1 time in total |
|
| Back to top |
|
 |
adaptr
Watchman
Joined: 06 Oct 2002
Posts: 6730
Location: Rotterdam, Netherlands
|
| Posted: Wed Jan 26, 2005 9:14 pm Post subject: |
|
|
One thing I can think of, is that maybe the pine-relayed message was also forwarded to the ISP using TLS - which will obviously fail to connect.
But then I have no idea why your mail server would or should attempt that.
_________________
>>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen |
|
| Back to top |
|
|
Vogateer
n00b
Joined: 27 Jul 2004
Posts: 49
Location: Oklahoma
|
| Posted: Thu Jan 27, 2005 4:54 pm Post subject: Does this soung possible? |
|
|
That's interesting, but I'm afraid I'm not sure how to fing out if that's the case. Anything I could look at?
I'm still assuming there is a problem with my pine setup, since postfix does route the email correctly when using Sylpheed Claws. I may be able to narrow it down if someone could verify this line of thinking for me.
I have the following settings in Postfix:
| Code: |
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
smtpd_sasl_local_domain =
broken_sasl_auth_clients = yes
smtpd_client_restrictions = permit_sasl_authenticated, reject
smtpd_use_tls = yes
smtpd_tls_auth_only = yes
smtpd_tls_key_file = /etc/ssl/postfix/server.key
smtpd_tls_cert_file = /etc/ssl/postfix/server.crt
smtpd_tls_CAfile = /etc/ssl/postfix/server.pem
smtpd_tls_loglevel = 3
smtpd_tls_received_header = yes
smtpd_tls_session_cache_timeout = 3600s
tls_random_source = dev:/dev/urandom
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/saslpass
smtp_sasl_security_options = noanonymous
|
The last three settings send out the e-mail through my ISP's server, with the hash giving those settings, if I understand it correctly. So, with these settings, Postfix will only allow a client to send mail if they verify with TLS, right?
Well, pine doesn't seem to handle self-signed certificates very well, and I initially used the "novalidate-cert" option in order to check my e-mail. I prefer to get things working, so I attempted to apply some of what I read here: Pine+OpenSSL HowTo Well for some reason now I receive no error messages when retrieving my mail, but I still receive error messages when I attempt to send. So, my main question is that, with the postfix settings above, am I correct to assume this problem pine has with self-signed certificates would prevent pine from using TLS correctly, and then in turn for some reason try to send e-mail directly instead of through my ISP's smtp server?
If so, why does the sending of the e-mail not simply fail? It appears to me that postfix tries to communicate with the server directly when I send with pine, which to me would make some sense of the logs, since I would think such communication would time out due to Cox blocking port 25, but I thought my settings would prevent even an attempt to send mail without TLS authentication. So could a simple certificate problem cause these things, or am I barking up the wrong tree? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
