So?
Recently switched to Sylpheed from Thunderbird (reasons not relevant here)
Everything seemed to be okay till I had to send mail to someone outside mailserver: Sylpheed receives "Relay access denied"
I do receive mail, can read it and manage it (I mean, delete, move it to other folder et cetera)
It's definitely not server-side problem since Thunderbird is able to send e-mail:
example.net is my server, example.pl being that remote onepostfix log of mailserver; Thunderbird can send e-mails with no problems
When Sylpheed tries to do the same:
"ambassador" is me computer's hostnamepostfix log again; Sylpheed connects to SMTP but gets rejected when sending
I see that postfix logs don't mention anything 'bout SASL in case of Sylpheed, so I guess it's where it fails
If important, server uses mandatory TLS both for IMAP and SMTP and Sylpheed is configured to use it (TLS for IMAP, STARTTLS for SMTP)
Any clues? It's matter of configuration or Sylpheed simply doesn't support SASL at all?
(Just in case: I made public IPs from logs invalid and IDs (iod36g75zkeg-like things) here got changed as well)
Recently switched to Sylpheed from Thunderbird (reasons not relevant here)
Everything seemed to be okay till I had to send mail to someone outside mailserver: Sylpheed receives "Relay access denied"
I do receive mail, can read it and manage it (I mean, delete, move it to other folder et cetera)
It's definitely not server-side problem since Thunderbird is able to send e-mail:
example.net is my server, example.pl being that remote one
Code:
Feb 16 15:24:07 mejl postfix/submission/smtpd[74578]: connect from unknown[10.50.44.9]Feb 16 15:24:07 mejl postfix/submission/smtpd[74578]: B799D5A0B3B: client=unknown[10.50.44.9], sasl_method=PLAIN, sasl_username=senderFeb 16 15:24:07 mejl postfix/cleanup[74579]: B799D5A0B3B: message-id=<kebab502-3d27-49d9-a2e4-021b397632ca@example.net>Feb 16 15:24:07 mejl postfix/qmgr[74076]: B799D5A0B3B: from=<sender@example.net>, size=117369, nrcpt=1 (queue active)Feb 16 15:24:11 mejl postfix/smtp[74580]: B799D5A0B3B: to=<recipient@example.pl>, relay=mx.example.pl[282.77.101.4]:25, delay=3.4, delays=0.11/0.05/0.28/3, dsn=2.0.0, status=sent (250 ok 1708093456 qp 36751 mailid 478b435adf1d2240f4e0dbus6a67185c)Feb 16 15:24:11 mejl postfix/qmgr[74076]: B799D5A0B3B: removedFeb 16 15:24:17 mejl postfix/submission/smtpd[74578]: disconnect from unknown[10.50.44.9] ehlo=2 starttls=1 auth=1 mail=1 rcpt=1 data=1 commands=7When Sylpheed tries to do the same:
"ambassador" is me computer's hostname
Code:
Feb 16 15:22:42 mejl postfix/smtpd[74552]: connect from unknown[10.50.44.9]Feb 16 15:22:42 mejl postfix/smtpd[74552]: NOQUEUE: reject: RCPT from unknown[10.50.44.9]: 454 4.7.1 <recipient@example.pl>: Relay access denied; from=<sender@example.net> to=<recipient@example.pl> proto=ESMTP helo=<ambassador>Feb 16 15:22:51 mejl postfix/smtpd[74552]: lost connection after RCPT from unknown[10.50.44.9]Feb 16 15:22:51 mejl postfix/smtpd[74552]: disconnect from unknown[10.50.44.9] ehlo=2 starttls=1 mail=1 rcpt=0/1 commands=4/5I see that postfix logs don't mention anything 'bout SASL in case of Sylpheed, so I guess it's where it fails
If important, server uses mandatory TLS both for IMAP and SMTP and Sylpheed is configured to use it (TLS for IMAP, STARTTLS for SMTP)
Any clues? It's matter of configuration or Sylpheed simply doesn't support SASL at all?
(Just in case: I made public IPs from logs invalid and IDs (iod36g75zkeg-like things) here got changed as well)
Statistics: Posted by Hetzer — 2024-02-16 16:47 — Replies 4 — Views 94