How to find out what port is Exim 4 using for SMTP?
I'm trying to debug a problem with email sending on my home machine, possibly a router related problem.
This is on Debian squeeze with Exim 4.72-6+squeeze3 (the default Exim 4 Debian package for this release).
I'm getting a Relaying denied. Proper authentication required error.
A reasonable first step is to determine what port my Exim 4 client is currently attempting to use.
However, this seems to be surprisingly difficult to find out.
The Debian documentation tells me that the Debian Exim tries to use TLS if available,
but I don't know how to confirm that either.
Here is an example from my Exim client log (/var/log/exim4/mainlog), when mail sending was still working.
2013-04-28 15:04:30 1UWNzx-00084Y-EO => foo@bar.com R=smarthost T=remote_smtp_smarthost H=email32.luxsci.com [
64.39.7.160] X=TLS1.0:RSA_AES_256_CBC_SHA1:32 DN="serialNumber=OeuJg-G-8alU-6KqWL5z-WwlWFVKQgwj,C=US,ST=Massachusetts,L=Dedham,O=Lux
Scientiae,OU=Secure Services,CN=*.luxsci.com"
Does the TLS1 mean TLS is being used, or is it just a meaningless string?
Assuming it is using TLS, then that suggests that port 465 is used, since that is apparently the default.
But how can I confirm any of this?
Here is a version of the currently failing mail sending.
2013-05-05 22:11:28 1UZ0OM-0003SM-6Z ** faheem@faheem.info R=smarthost T=remote_smtp_smarthost: SMTP error from remote mail server after RCPT
TO:<faheem@faheem.info
>: host secure-email-32.luxsci.com [64.39.7.160]: 550 5.7.1 <faheem@faheem.info>... Relaying denied. Proper authentication required.
linux email debian smtp exim
asked May 5 '13 at 20:13
Faheem MithaFaheem Mitha
348313
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm trying to debug a problem with email sending on my home machine, possibly a router related problem.
This is on Debian squeeze with Exim 4.72-6+squeeze3 (the default Exim 4 Debian package for this release).
I'm getting a Relaying denied. Proper authentication required error.
A reasonable first step is to determine what port my Exim 4 client is currently attempting to use.
However, this seems to be surprisingly difficult to find out.
The Debian documentation tells me that the Debian Exim tries to use TLS if available,
but I don't know how to confirm that either.
Here is an example from my Exim client log (/var/log/exim4/mainlog), when mail sending was still working.
2013-04-28 15:04:30 1UWNzx-00084Y-EO => foo@bar.com R=smarthost T=remote_smtp_smarthost H=email32.luxsci.com [
64.39.7.160] X=TLS1.0:RSA_AES_256_CBC_SHA1:32 DN="serialNumber=OeuJg-G-8alU-6KqWL5z-WwlWFVKQgwj,C=US,ST=Massachusetts,L=Dedham,O=Lux
Scientiae,OU=Secure Services,CN=*.luxsci.com"
Does the TLS1 mean TLS is being used, or is it just a meaningless string?
Assuming it is using TLS, then that suggests that port 465 is used, since that is apparently the default.
But how can I confirm any of this?
Here is a version of the currently failing mail sending.
2013-05-05 22:11:28 1UZ0OM-0003SM-6Z ** faheem@faheem.info R=smarthost T=remote_smtp_smarthost: SMTP error from remote mail server after RCPT
TO:<faheem@faheem.info
>: host secure-email-32.luxsci.com [64.39.7.160]: 550 5.7.1 <faheem@faheem.info>... Relaying denied. Proper authentication required.
linux email debian smtp exim
asked May 5 '13 at 20:13
Faheem MithaFaheem Mitha
348313
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
1
The proper thing to do is test the routing withexim -bt user@domainfirst. To check what port is being usedlsof -i -P | grep exim
– dawud
May 5 '13 at 20:43
For the former, I getexim -bt user@domain R: smarthost for user@domain user@domain router = smarthost, transport = remote_smtp_smarthost host email32.luxsci.com [64.39.7.160]For the latter, I getlsof -i -P | grep exim exim4 25829 Debian-exim 3u IPv4 784099 0t0 TCP orwell:25 (LISTEN). Forgive my ignorance, but does that mean the connection is happening on port 25? I thought the port referred to that on the remote machine, though.
– Faheem Mitha
May 5 '13 at 21:06
It is not clear from the info you provided in the question where are you trying to connect to, nor if the remote server uses authentication or TLS. Theuser@domainpart wasn't meant to be written literally, rather replaced by the actual mail address you are supposed to be using.
– dawud
May 5 '13 at 21:09
I'm trying to pass my messages on to a smarthost, which does provide TLS. As far as theexim -btcommand goes, I get the same result as already posted, with any email address I use. It appears emails are being both being accepted, and not being accepted, in a single queue run, so there may be something funky going on with the smarthost.
– Faheem Mitha
May 5 '13 at 21:15
add a comment |
I'm trying to debug a problem with email sending on my home machine, possibly a router related problem.
This is on Debian squeeze with Exim 4.72-6+squeeze3 (the default Exim 4 Debian package for this release).
I'm getting a Relaying denied. Proper authentication required error.
A reasonable first step is to determine what port my Exim 4 client is currently attempting to use.
However, this seems to be surprisingly difficult to find out.
The Debian documentation tells me that the Debian Exim tries to use TLS if available,
but I don't know how to confirm that either.
Here is an example from my Exim client log (/var/log/exim4/mainlog), when mail sending was still working.
2013-04-28 15:04:30 1UWNzx-00084Y-EO => foo@bar.com R=smarthost T=remote_smtp_smarthost H=email32.luxsci.com [
64.39.7.160] X=TLS1.0:RSA_AES_256_CBC_SHA1:32 DN="serialNumber=OeuJg-G-8alU-6KqWL5z-WwlWFVKQgwj,C=US,ST=Massachusetts,L=Dedham,O=Lux
Scientiae,OU=Secure Services,CN=*.luxsci.com"
Does the TLS1 mean TLS is being used, or is it just a meaningless string?
Assuming it is using TLS, then that suggests that port 465 is used, since that is apparently the default.
But how can I confirm any of this?
Here is a version of the currently failing mail sending.
2013-05-05 22:11:28 1UZ0OM-0003SM-6Z ** faheem@faheem.info R=smarthost T=remote_smtp_smarthost: SMTP error from remote mail server after RCPT
TO:<faheem@faheem.info
>: host secure-email-32.luxsci.com [64.39.7.160]: 550 5.7.1 <faheem@faheem.info>... Relaying denied. Proper authentication required.
linux email debian smtp exim
asked May 5 '13 at 20:13
Faheem MithaFaheem Mitha
348313
I'm trying to debug a problem with email sending on my home machine, possibly a router related problem.
This is on Debian squeeze with Exim 4.72-6+squeeze3 (the default Exim 4 Debian package for this release).
I'm getting a Relaying denied. Proper authentication required error.
A reasonable first step is to determine what port my Exim 4 client is currently attempting to use.
However, this seems to be surprisingly difficult to find out.
The Debian documentation tells me that the Debian Exim tries to use TLS if available,
but I don't know how to confirm that either.
Here is an example from my Exim client log (/var/log/exim4/mainlog), when mail sending was still working.
2013-04-28 15:04:30 1UWNzx-00084Y-EO => foo@bar.com R=smarthost T=remote_smtp_smarthost H=email32.luxsci.com [
64.39.7.160] X=TLS1.0:RSA_AES_256_CBC_SHA1:32 DN="serialNumber=OeuJg-G-8alU-6KqWL5z-WwlWFVKQgwj,C=US,ST=Massachusetts,L=Dedham,O=Lux
Scientiae,OU=Secure Services,CN=*.luxsci.com"
Does the TLS1 mean TLS is being used, or is it just a meaningless string?
Assuming it is using TLS, then that suggests that port 465 is used, since that is apparently the default.
But how can I confirm any of this?
Here is a version of the currently failing mail sending.
2013-05-05 22:11:28 1UZ0OM-0003SM-6Z ** faheem@faheem.info R=smarthost T=remote_smtp_smarthost: SMTP error from remote mail server after RCPT
TO:<faheem@faheem.info
>: host secure-email-32.luxsci.com [64.39.7.160]: 550 5.7.1 <faheem@faheem.info>... Relaying denied. Proper authentication required.
linux email debian smtp exim
linux email debian smtp exim
asked May 5 '13 at 20:13
Faheem MithaFaheem Mitha
348313
asked May 5 '13 at 20:13
Faheem MithaFaheem Mitha
348313
asked May 5 '13 at 20:13
Faheem MithaFaheem Mitha
348313
asked May 5 '13 at 20:13
Faheem MithaFaheem Mitha
348313
asked May 5 '13 at 20:13
Faheem MithaFaheem Mitha
348313
348313
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
1
The proper thing to do is test the routing withexim -bt user@domainfirst. To check what port is being usedlsof -i -P | grep exim
– dawud
May 5 '13 at 20:43
For the former, I getexim -bt user@domain R: smarthost for user@domain user@domain router = smarthost, transport = remote_smtp_smarthost host email32.luxsci.com [64.39.7.160]For the latter, I getlsof -i -P | grep exim exim4 25829 Debian-exim 3u IPv4 784099 0t0 TCP orwell:25 (LISTEN). Forgive my ignorance, but does that mean the connection is happening on port 25? I thought the port referred to that on the remote machine, though.
– Faheem Mitha
May 5 '13 at 21:06
It is not clear from the info you provided in the question where are you trying to connect to, nor if the remote server uses authentication or TLS. Theuser@domainpart wasn't meant to be written literally, rather replaced by the actual mail address you are supposed to be using.
– dawud
May 5 '13 at 21:09
I'm trying to pass my messages on to a smarthost, which does provide TLS. As far as theexim -btcommand goes, I get the same result as already posted, with any email address I use. It appears emails are being both being accepted, and not being accepted, in a single queue run, so there may be something funky going on with the smarthost.
– Faheem Mitha
May 5 '13 at 21:15
add a comment |
1
The proper thing to do is test the routing withexim -bt user@domainfirst. To check what port is being usedlsof -i -P | grep exim
– dawud
May 5 '13 at 20:43
For the former, I getexim -bt user@domain R: smarthost for user@domain user@domain router = smarthost, transport = remote_smtp_smarthost host email32.luxsci.com [64.39.7.160]For the latter, I getlsof -i -P | grep exim exim4 25829 Debian-exim 3u IPv4 784099 0t0 TCP orwell:25 (LISTEN). Forgive my ignorance, but does that mean the connection is happening on port 25? I thought the port referred to that on the remote machine, though.
– Faheem Mitha
May 5 '13 at 21:06
It is not clear from the info you provided in the question where are you trying to connect to, nor if the remote server uses authentication or TLS. Theuser@domainpart wasn't meant to be written literally, rather replaced by the actual mail address you are supposed to be using.
– dawud
May 5 '13 at 21:09
I'm trying to pass my messages on to a smarthost, which does provide TLS. As far as theexim -btcommand goes, I get the same result as already posted, with any email address I use. It appears emails are being both being accepted, and not being accepted, in a single queue run, so there may be something funky going on with the smarthost.
– Faheem Mitha
May 5 '13 at 21:15
1
1
The proper thing to do is test the routing with
exim -bt user@domain first. To check what port is being used lsof -i -P | grep exim– dawud
May 5 '13 at 20:43
The proper thing to do is test the routing with
exim -bt user@domain first. To check what port is being used lsof -i -P | grep exim– dawud
May 5 '13 at 20:43
For the former, I get
exim -bt user@domain R: smarthost for user@domain user@domain router = smarthost, transport = remote_smtp_smarthost host email32.luxsci.com [64.39.7.160] For the latter, I get lsof -i -P | grep exim exim4 25829 Debian-exim 3u IPv4 784099 0t0 TCP orwell:25 (LISTEN). Forgive my ignorance, but does that mean the connection is happening on port 25? I thought the port referred to that on the remote machine, though.– Faheem Mitha
May 5 '13 at 21:06
For the former, I get
exim -bt user@domain R: smarthost for user@domain user@domain router = smarthost, transport = remote_smtp_smarthost host email32.luxsci.com [64.39.7.160] For the latter, I get lsof -i -P | grep exim exim4 25829 Debian-exim 3u IPv4 784099 0t0 TCP orwell:25 (LISTEN). Forgive my ignorance, but does that mean the connection is happening on port 25? I thought the port referred to that on the remote machine, though.– Faheem Mitha
May 5 '13 at 21:06
It is not clear from the info you provided in the question where are you trying to connect to, nor if the remote server uses authentication or TLS. The
user@domainpart wasn't meant to be written literally, rather replaced by the actual mail address you are supposed to be using.– dawud
May 5 '13 at 21:09
It is not clear from the info you provided in the question where are you trying to connect to, nor if the remote server uses authentication or TLS. The
user@domainpart wasn't meant to be written literally, rather replaced by the actual mail address you are supposed to be using.– dawud
May 5 '13 at 21:09
I'm trying to pass my messages on to a smarthost, which does provide TLS. As far as the
exim -bt command goes, I get the same result as already posted, with any email address I use. It appears emails are being both being accepted, and not being accepted, in a single queue run, so there may be something funky going on with the smarthost.– Faheem Mitha
May 5 '13 at 21:15
I'm trying to pass my messages on to a smarthost, which does provide TLS. As far as the
exim -bt command goes, I get the same result as already posted, with any email address I use. It appears emails are being both being accepted, and not being accepted, in a single queue run, so there may be something funky going on with the smarthost.– Faheem Mitha
May 5 '13 at 21:15
add a comment |
2 Answers
2
active
oldest
votes
It seems that
1) your exim sends outgoing email via smart host
2) the smart host refuses to relay (accept to send send further) without SMTP AUTH
Your Exim (by default) should use port 25.
secure-email-32.luxsci.com offers STARTTLS extension of ESMTP protocol => your MTA/exim can turn unencrypted SMTP connection into encrypted one (the same TCP connection).
secure-email-32.luxsci.com offers only "plain text" methods of SMTP AUTH (LOGIN and PLAIN) so your exim SHOULD use them after STARTTLS command
answered May 5 '13 at 21:19
AnFiAnFi
69739
It seems that my setup is basically Ok, because the messages get accepted at least some of the time. However, the messages are also getting rejected some of the time, sometimes in the same delivery attempt. In any case, I'd like to know how to determine what port Exim is using to attempt to deliver these messages via SMTP.
– Faheem Mitha
May 5 '13 at 21:41
The host may accept its "local email domains" without authentication.
– AnFi
May 6 '13 at 6:04
I've been testing using disposable email addresses, and these go through. These aren't local email domains by any definition.
– Faheem Mitha
May 6 '13 at 10:37
Well, when I say they go through, they do some of the time. The authentication intermittently fails, for no apparent reason.
– Faheem Mitha
May 6 '13 at 10:56
add a comment |
You may want to add a log line showing the port that is actually used during this very connection. Something like (not sure if you really need the condition)
warn condition = yes
log_message = Port: $received_port
in the beginning of your check_helo acl.
answered Apr 2 '14 at 10:45
HardyHardy
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f591855%2fhow-to-find-out-what-port-is-exim-4-using-for-smtp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
It seems that
1) your exim sends outgoing email via smart host
2) the smart host refuses to relay (accept to send send further) without SMTP AUTH
Your Exim (by default) should use port 25.
secure-email-32.luxsci.com offers STARTTLS extension of ESMTP protocol => your MTA/exim can turn unencrypted SMTP connection into encrypted one (the same TCP connection).
secure-email-32.luxsci.com offers only "plain text" methods of SMTP AUTH (LOGIN and PLAIN) so your exim SHOULD use them after STARTTLS command
answered May 5 '13 at 21:19
AnFiAnFi
69739
It seems that my setup is basically Ok, because the messages get accepted at least some of the time. However, the messages are also getting rejected some of the time, sometimes in the same delivery attempt. In any case, I'd like to know how to determine what port Exim is using to attempt to deliver these messages via SMTP.
– Faheem Mitha
May 5 '13 at 21:41
The host may accept its "local email domains" without authentication.
– AnFi
May 6 '13 at 6:04
I've been testing using disposable email addresses, and these go through. These aren't local email domains by any definition.
– Faheem Mitha
May 6 '13 at 10:37
Well, when I say they go through, they do some of the time. The authentication intermittently fails, for no apparent reason.
– Faheem Mitha
May 6 '13 at 10:56
add a comment |
It seems that
1) your exim sends outgoing email via smart host
2) the smart host refuses to relay (accept to send send further) without SMTP AUTH
Your Exim (by default) should use port 25.
secure-email-32.luxsci.com offers STARTTLS extension of ESMTP protocol => your MTA/exim can turn unencrypted SMTP connection into encrypted one (the same TCP connection).
secure-email-32.luxsci.com offers only "plain text" methods of SMTP AUTH (LOGIN and PLAIN) so your exim SHOULD use them after STARTTLS command
answered May 5 '13 at 21:19
AnFiAnFi
69739
It seems that my setup is basically Ok, because the messages get accepted at least some of the time. However, the messages are also getting rejected some of the time, sometimes in the same delivery attempt. In any case, I'd like to know how to determine what port Exim is using to attempt to deliver these messages via SMTP.
– Faheem Mitha
May 5 '13 at 21:41
The host may accept its "local email domains" without authentication.
– AnFi
May 6 '13 at 6:04
I've been testing using disposable email addresses, and these go through. These aren't local email domains by any definition.
– Faheem Mitha
May 6 '13 at 10:37
Well, when I say they go through, they do some of the time. The authentication intermittently fails, for no apparent reason.
– Faheem Mitha
May 6 '13 at 10:56
add a comment |
It seems that
1) your exim sends outgoing email via smart host
2) the smart host refuses to relay (accept to send send further) without SMTP AUTH
Your Exim (by default) should use port 25.
secure-email-32.luxsci.com offers STARTTLS extension of ESMTP protocol => your MTA/exim can turn unencrypted SMTP connection into encrypted one (the same TCP connection).
secure-email-32.luxsci.com offers only "plain text" methods of SMTP AUTH (LOGIN and PLAIN) so your exim SHOULD use them after STARTTLS command
answered May 5 '13 at 21:19
AnFiAnFi
69739
It seems that
1) your exim sends outgoing email via smart host
2) the smart host refuses to relay (accept to send send further) without SMTP AUTH
Your Exim (by default) should use port 25.
secure-email-32.luxsci.com offers STARTTLS extension of ESMTP protocol => your MTA/exim can turn unencrypted SMTP connection into encrypted one (the same TCP connection).
secure-email-32.luxsci.com offers only "plain text" methods of SMTP AUTH (LOGIN and PLAIN) so your exim SHOULD use them after STARTTLS command
answered May 5 '13 at 21:19
AnFiAnFi
69739
answered May 5 '13 at 21:19
AnFiAnFi
69739
answered May 5 '13 at 21:19
AnFiAnFi
69739
answered May 5 '13 at 21:19
AnFiAnFi
69739
69739
It seems that my setup is basically Ok, because the messages get accepted at least some of the time. However, the messages are also getting rejected some of the time, sometimes in the same delivery attempt. In any case, I'd like to know how to determine what port Exim is using to attempt to deliver these messages via SMTP.
– Faheem Mitha
May 5 '13 at 21:41
The host may accept its "local email domains" without authentication.
– AnFi
May 6 '13 at 6:04
I've been testing using disposable email addresses, and these go through. These aren't local email domains by any definition.
– Faheem Mitha
May 6 '13 at 10:37
Well, when I say they go through, they do some of the time. The authentication intermittently fails, for no apparent reason.
– Faheem Mitha
May 6 '13 at 10:56
add a comment |
It seems that my setup is basically Ok, because the messages get accepted at least some of the time. However, the messages are also getting rejected some of the time, sometimes in the same delivery attempt. In any case, I'd like to know how to determine what port Exim is using to attempt to deliver these messages via SMTP.
– Faheem Mitha
May 5 '13 at 21:41
The host may accept its "local email domains" without authentication.
– AnFi
May 6 '13 at 6:04
I've been testing using disposable email addresses, and these go through. These aren't local email domains by any definition.
– Faheem Mitha
May 6 '13 at 10:37
Well, when I say they go through, they do some of the time. The authentication intermittently fails, for no apparent reason.
– Faheem Mitha
May 6 '13 at 10:56
It seems that my setup is basically Ok, because the messages get accepted at least some of the time. However, the messages are also getting rejected some of the time, sometimes in the same delivery attempt. In any case, I'd like to know how to determine what port Exim is using to attempt to deliver these messages via SMTP.
– Faheem Mitha
May 5 '13 at 21:41
It seems that my setup is basically Ok, because the messages get accepted at least some of the time. However, the messages are also getting rejected some of the time, sometimes in the same delivery attempt. In any case, I'd like to know how to determine what port Exim is using to attempt to deliver these messages via SMTP.
– Faheem Mitha
May 5 '13 at 21:41
The host may accept its "local email domains" without authentication.
– AnFi
May 6 '13 at 6:04
The host may accept its "local email domains" without authentication.
– AnFi
May 6 '13 at 6:04
I've been testing using disposable email addresses, and these go through. These aren't local email domains by any definition.
– Faheem Mitha
May 6 '13 at 10:37
I've been testing using disposable email addresses, and these go through. These aren't local email domains by any definition.
– Faheem Mitha
May 6 '13 at 10:37
Well, when I say they go through, they do some of the time. The authentication intermittently fails, for no apparent reason.
– Faheem Mitha
May 6 '13 at 10:56
Well, when I say they go through, they do some of the time. The authentication intermittently fails, for no apparent reason.
– Faheem Mitha
May 6 '13 at 10:56
add a comment |
You may want to add a log line showing the port that is actually used during this very connection. Something like (not sure if you really need the condition)
warn condition = yes
log_message = Port: $received_port
in the beginning of your check_helo acl.
answered Apr 2 '14 at 10:45
HardyHardy
1
add a comment |
You may want to add a log line showing the port that is actually used during this very connection. Something like (not sure if you really need the condition)
warn condition = yes
log_message = Port: $received_port
in the beginning of your check_helo acl.
answered Apr 2 '14 at 10:45
HardyHardy
1
add a comment |
You may want to add a log line showing the port that is actually used during this very connection. Something like (not sure if you really need the condition)
warn condition = yes
log_message = Port: $received_port
in the beginning of your check_helo acl.
answered Apr 2 '14 at 10:45
HardyHardy
1
You may want to add a log line showing the port that is actually used during this very connection. Something like (not sure if you really need the condition)
warn condition = yes
log_message = Port: $received_port
in the beginning of your check_helo acl.
answered Apr 2 '14 at 10:45
HardyHardy
1
answered Apr 2 '14 at 10:45
HardyHardy
1
answered Apr 2 '14 at 10:45
HardyHardy
1
answered Apr 2 '14 at 10:45
HardyHardy
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f591855%2fhow-to-find-out-what-port-is-exim-4-using-for-smtp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
The proper thing to do is test the routing with
exim -bt user@domainfirst. To check what port is being usedlsof -i -P | grep exim– dawud
May 5 '13 at 20:43
For the former, I get
exim -bt user@domain R: smarthost for user@domain user@domain router = smarthost, transport = remote_smtp_smarthost host email32.luxsci.com [64.39.7.160]For the latter, I getlsof -i -P | grep exim exim4 25829 Debian-exim 3u IPv4 784099 0t0 TCP orwell:25 (LISTEN). Forgive my ignorance, but does that mean the connection is happening on port 25? I thought the port referred to that on the remote machine, though.– Faheem Mitha
May 5 '13 at 21:06
It is not clear from the info you provided in the question where are you trying to connect to, nor if the remote server uses authentication or TLS. The
user@domainpart wasn't meant to be written literally, rather replaced by the actual mail address you are supposed to be using.– dawud
May 5 '13 at 21:09
I'm trying to pass my messages on to a smarthost, which does provide TLS. As far as the
exim -btcommand goes, I get the same result as already posted, with any email address I use. It appears emails are being both being accepted, and not being accepted, in a single queue run, so there may be something funky going on with the smarthost.– Faheem Mitha
May 5 '13 at 21:15