I would like to configure Exim to send all of my non-local outgoing mail
through an external relay on port 465. The relay host requires TLS and
SMTP authentication. I do not need to use TLS for incoming mail.
I am confused as to whether I need to set up a private key and certificate
to send
Matthew Ford [EMAIL PROTECTED] wrote:
I would like to configure Exim to send all of my non-local outgoing mail
through an external relay on port 465. The relay host requires TLS and
SMTP authentication. I do not need to use TLS for incoming mail.
I am confused as to whether I need to set up
Andreas Metzler wrote:
Matthew Ford [EMAIL PROTECTED] wrote:
SMTP timeout while connected to smtp.myrelay.com [111.222.333.444]
after initial connection: Connection timed out
What should I do to get my TLS and authentication working?
Looks like your remote host is not providing
Matthew Ford wrote:
I would like to configure Exim to send all of my non-local outgoing mail
through an external relay on port 465. The relay host requires TLS and
SMTP authentication. I do not need to use TLS for incoming mail.
Are you _sure_ it requires TLS on 465? 465 is traditionally
Matthew Ford wrote:
When I telnet to my remote host on port 465, I just get the following, and
nothing more...
Does this confirm that my host is using ssl-on-connect? (NB I know the
It's likely, but it does only confirm that the port is not closed. To
test for SSL, use:
openssl s_client
On Sun, 26 Feb 2006, Matthew Ford wrote:
What should I do to get my TLS and authentication working?
Looks like your remote host is not providing TLS (using the
STARTTLS command) but the (non-standard) ssl-on-connect. Exim does not
support SSL-on connect as client, you'd need to
Hello List,
i have much trouble sending to comcast Mailservers. The comcast Servers
returns 450 [TEMPFAIL] comcast.net requires valid sender domain.
Sometimes the mail goes thru after a few hours but mostly not. What i
can see with ngrep is that my exim must wait a long time for Return
Tom Fischer wrote:
i have much trouble sending to comcast Mailservers. The comcast Servers
returns 450 [TEMPFAIL] comcast.net requires valid sender domain.
So, what domain does the envelope-from have on a typical mail
that gets rejected? Does that domain exist, have proper rDNS
and matching
On 26 Feb 2006, at 05:12, John W. Baxter wrote:
Here, we have elected to relax the requirement for the purpose of
flagging
suspicious servers, accepting any result from reverse lookup as less
suspicious than no result. We do that with a Python daemon which
follows
the rules we want to
Hello all,
I posted on this topic back in late January to no resolution. After
spending most all of this weekend doing research, I still am at a total
loss, but do have clues on getting my problem resolved.
Just a brief history. I currently use the DirectAdmin (www.directadmin.com)
Hi,
How to integrate blacklists is well documented. And also how to pass by
these blacklists by
having local configuration files with trusted mail servers can be found on
the mailing lists.
I however cannot find how to use a DNS based whitelist like the nlwhitelist
or the bewhitelist.
I
Is there a simple way to change a username for received mail only?
In other words, a user [EMAIL PROTECTED] does not want to see any mail
addressed to [EMAIL PROTECTED] but *does* want to receive mail addressed
to [EMAIL PROTECTED] Obviously an alias will add the second username,
but how do you
Jeremy Harris wrote:
Tom Fischer wrote:
i have much trouble sending to comcast Mailservers. The comcast
Servers returns 450 [TEMPFAIL] comcast.net requires valid sender domain.
So, what domain does the envelope-from have on a typical mail
that gets rejected? Does that domain exist,
Pascal wrote:
accept message= X-Blacklist-Whitelisted: $sender_host_address
warn message = X-Blacklist-Warning: $sender_host_address is
The accept matches before the warn, so the warn will not be used.
Reverse the two statements.
--
## List details at
Tom Fischer wrote:
It is artedona.de. The Domain exist. They relay about our Mail-Server
Yes, but the resolving is not only overly indirect (artedona.de -
ns{1,2}.ebuz-kunden.de - ns{1,2}.dns-resolver.net), the TTL for the MX
and NS RR is 1 (one!) second. You should really fix both of that.
On 2006-02-26 at 17:19 -0500, Jay Rouman wrote:
Is there a simple way to change a username for received mail only?
Block it in a RCPT ACL but still route it normally.
Aliases handle the externally visible value, you route it normally to
the real user, but the real user can't be directly sent to
On 2/26/06 12:36 PM, Giuliano Gavazzi [EMAIL PROTECTED] wrote:
[Here, Giuliano is quoting me:]
Here, we have elected to relax the requirement for the purpose of
flagging
suspicious servers, accepting any result from reverse lookup as less
suspicious than no result. We do that with a Python
17 matches
Mail list logo
