Freesco, NND, CDN, EOS

http://www.freesco.pl
Dzisiaj jest piątek, 15 sierpnia 2025, 15:50

Strefa czasowa UTC+2godz.




Nowy temat Odpowiedz w temacie  [ Posty: 12 ] 
Autor Wiadomość
Post: czwartek, 28 listopada 2002, 12:44 
Witam !

Jestem początkującym użytkownikiem Freesco. Zaistalowałem sobie EXIM i TEAPOP żeby mieć własną skrzynkę pocztową dla siebie i znajomych. Mam problem z ustawieniem tych programów. Próbowałem już różne konfiguracje i opisy z forum jak i FAQ ze strony ARX.PL. Nie wiem jakie mają być konkretne ustawienia. Może mnie ktoś naprowadzi krok po kroku jak to zrobić.

nazwa servera : xnet,
domena : pl
IP freesco : 10.0.0.1
stacje robocze Ip : 10.0.0.2 i 3

Mam stworzone konto użytkownika (artur) "adduserem" i według opisu to mój mail powinien wyglądać tak : artur@xnet.pl lub 10.0.0.1@xnet.pl.
Natomiast gdy ustawię taki adres i założę taką skrzynkę pocztową na stacji roboczej pod OUTLOOK EXPRESS - żadne maile nie dochodzą - wywala mi błąd, że nie ma takiego hosta i maile wracają do mnie spowrotem. PROSZĘ O POMOC !!!! jak to zrobić i jak to skonfigurować pod OUTLOOKIEM.

Pozdrawiam - Smyf


Na górę
  
 
 Tytuł:
Post: czwartek, 28 listopada 2002, 13:17 
Offline
Honorowy Admin

Rejestracja: piątek, 5 lipca 2002, 17:30
Posty: 7800
Lokalizacja: Słupsk
Używając standardowego adduser z Freesco masz identyczny numer usera dla każdego dodanego - jest to numer 500, taki sam jak user ppp. Stąd problemy. Poza tym numery ip które podałeś dotyczą wewnętrznej sieci i tylko wewnątrz taka poczta będzie działać.
Zobacz http://miniwebportal.and.pl


Na górę
 Wyświetl profil  
 
 Tytuł: EXIM
Post: piątek, 29 listopada 2002, 15:01 
Ok! Dzięki z userami już się uporałem, ale jak teraz to ustawić ,żeby działała poczta nie tylko w obrębie LAN. Ustawienia EXIMA robiłem dokładnie według opisu an stronie miniwebportal i nic. Może to jest wina tego, że nie mam stałego IP, bo moje frresco działa na zwykłym połączeniu modemowym.

Pozdrawiam - Smyf


Na górę
  
 
 Tytuł:
Post: piątek, 29 listopada 2002, 16:20 
Offline
Honorowy Admin

Rejestracja: piątek, 5 lipca 2002, 17:30
Posty: 7800
Lokalizacja: Słupsk
W zasadzie nie jest potrzebny stały IP - można skorzystać z usługi dyndns lub czegoś podobnego. Jednak zestawiać exima na modemie to nie ma sensu, bo jak się rozłączysz, to nikt ci poczty nie przyśle.


Na górę
 Wyświetl profil  
 
 Tytuł:
Post: sobota, 30 listopada 2002, 01:49 
Offline
Użytkownik

Rejestracja: poniedziałek, 4 listopada 2002, 00:50
Posty: 147
A ja mam taki problem z mam exima i teapop zainstalowane i nie chce mi przyjmowac zadnej poczty. wysyla na zewnatrz bez problemu. co trzeba zrobic aby dochodzila poczta z zewnatrz na moj serwer. mam zalozone konto pod dyn dns z adresem serwer.ath.cx. Jak dobrze to skonfigorowac aby przychodzila poczta.


Na górę
 Wyświetl profil  
 
 Tytuł:
Post: sobota, 30 listopada 2002, 12:51 
Offline
Honorowy Admin

Rejestracja: piątek, 5 lipca 2002, 17:30
Posty: 7800
Lokalizacja: Słupsk
Za mało danych.
Przyczyn może być wiele:
- niewłaściwie wpisany primary host
- źle skonfigurowany dyndns
- nieuruchomiony named
- źle skonfigurowane inne elementy exima i teapopa


Na górę
 Wyświetl profil  
 
 Tytuł:
Post: sobota, 30 listopada 2002, 16:40 
Offline
Użytkownik

Rejestracja: poniedziałek, 4 listopada 2002, 00:50
Posty: 147
Prosze o pomoc co zrobic aby dzialal exim. On wysyBa poczte lecz jej nie odbiera. Konto na dyn dns dziala na 100 % gdyz uzywam ftp z zewnatrz sieci do przesylania plikow. moj adres na dyndns to serwer.ath.cx. ponizej caly plik config exim


######################################################################
# Runtime configuration file for Exim #
######################################################################


# This is a default configuration file which will operate correctly in
# uncomplicated installations. Please see the manual for a complete list
# of all the runtime configuration options that can be included in a
# configuration file. There are many more than are mentioned here. The
# manual is in the file doc/spec.txt in the Exim distribution as a plain
# ASCII file. Other formats (PostScript, Texinfo, HTML, PDF) are available
# from the Exim ftp sites. The manual is also online via the Exim web sites.

### Minor changes have been made to the defualt configuration
### for an "easier" out of the box Freesco install
### These have been commented using three hashes ### for clarity. -- DG

# This file is divided into several parts, all but the last of which are
# terminated by a line containing the word "end". The parts must appear
# in the correct order, and all must be present (even if some of them are
# in fact empty). Blank lines, and lines starting with # are ignored.


############ IMPORTANT ########## IMPORTANT ########### IMPORTANT ############
# #
# Whenever you change Exim's configuration file, you *must* remember to HUP #
# the Exim daemon, because it will not pick up the new configuration until #
# until you do this. It is usually a good idea to test a new configuration #
# for syntactic correctness (e.g. using "exim -C /config/file -bV") first. #
# #
############ IMPORTANT ########## IMPORTANT ########### IMPORTANT ############



######################################################################
# MAIN CONFIGURATION SETTINGS #
######################################################################

# Specify your host's canonical name here. This should normally be the fully
# qualified "official" name of your host. If this option is not set, the
# uname() function is called to obtain the name.

### If left blank this only seems to obtain the Freesco host name, not the
### fully qualified name. *Some* mail servers do not allow you to connect
### unless you have a fully qualified domain name here. Personally I
### found that everything was fine with "router" 90% of the time, I
### use my dyndns.org domain now--which has never had problems.

primary_hostname = serwer.ath.cx


# Specify the domain you want to be added to all unqualified addresses
# here. An unqualified address is one that does not contain an "@" character
# followed by a domain. For example, "caesar@rome.ex" is a fully qualified
# address, but the string "caesar" (i.e. just a login name) is an unqualified
# email address. Unqualified addresses are accepted only from local callers by
# default. See the receiver_unqualified_{hosts,nets} options if you want
# to permit unqualified addresses from remote sources. If this option is
# not set, the primary_hostname value is used for qualification.

# qualify_domain =


# If you want unqualified recipient addresses to be qualified with a different
# domain to unqualified sender addresses, specify the recipient domain here.
# If this option is not set, the qualify_domain value is used.

# qualify_recipient =


# Specify your local domains as a colon-separated list here. If this option
# is not set (i.e. not mentioned in the configuration file), the
# qualify_recipient value is used as the only local domain. If you do not want
# to do any local deliveries, uncomment the following line, but do not supply
# any data for it. This sets local_domains to an empty string, which is not
# the same as not mentioning it at all. An empty string specifies that there
# are no local domains; not setting it at all causes the default value (the
# setting of qualify_recipient) to be used.

local_domains = localhost:serwer.ath.cx:serwer.ath.cx

### Multidrop users should probably add their multi drop domain to the list of
### local hosts!


# If you want to accept mail addressed to your host's literal IP address, for
# example, mail addressed to "user@[111.111.111.111]", then uncomment the
# following line, or supply the literal domain(s) as part of "local_domains"
# above. You also need to comment "forbid_domain_literals" below. This is not
# recommended for today's Internet.

# local_domains_include_host_literals


# The following line prevents Exim from recognizing addresses of the form
# "user@[111.111.111.111]" that is, with a "domain literal" (an IP address)
# instead of a named domain. The RFCs still require this form, but it makes
# little sense to permit mail to be sent to specific hosts by their IP address
# in the modern Internet, and this ancient format has been used by those
# seeking to abuse hosts by using them for unwanted relaying. If you really
# do want to support domain literals, remove the following line, and see
# also the "domain_literal" router below.

forbid_domain_literals


# No local deliveries will ever be run under the uids of these users (a colon-
# separated list). An attempt to do so gets changed so that it runs under the
# uid of "nobody" instead. This is a paranoic safety catch. Note the default
# setting means you cannot deliver mail addressed to root as if it were a
# normal user. This isn't usually a problem, as most sites have an alias for
# root that redirects such mail to a human administrator.

never_users = root
### This never_users option IS NOT for preventing mail delivery. Please read
### the above comment carefully. Mail delivery WILL be attempted but as the
### user "nobody" this is a security feature for root. You should NOT change
### it!!

# The use of your host as a mail relay by any host, including the local host
# calling its own SMTP port, is locked out by default. If you want to permit
# relaying from the local host, you should set
#
# host_accept_relay = localhost
#
# If you want to permit relaying through your host from certain hosts or IP
# networks, you need to set the option appropriately, for example
#
# host_accept_relay = my.friends.host : 192.168.0.0/16
#
# If you are an MX backup or gateway of some kind for some domains, you must
# set relay_domains to match those domains. This will allow any host to
# relay through your host to those domains.
#
# relay_domains =
#
# See the section of the manual entitled "Control of relaying" for more
# information.

### I included the address of my subnet here, so I can send mail out from
### any account, without needing to use SMTP AUTH (having to use a Freesco
### name and password to be able to send mail)

host_accept_relay = localhost:192.168.0.0/16

### The following setting prevents anyone from being able to authenticate
### themselves with a username and password from your freesco box.
### It is the default setting because it is more secure.

host_auth_accept_relay = *

### However if you do wish to allow users from the internet to send mail
### using exim on your freesco box, you should use the following instead
### as this requires them to use a username and password from your freesco
### box unless their host, IP or an IP range which includes their IP is
### listed in the host_accept_relay setting, above. Please see the file
### auth.txt for more details on this. NOTE: please make sure your
### obvious usernames do not have obvious passwords or you are just asking
### for someone to abuse your mail server. The user "ppp" IS blocked by
### the authentication code as it's default password is know.

# host_auth_accept_relay = *


# The setting below causes Exim to do a reverse DNS lookup on all incoming
# IP calls, in order to get the true host name. If you feel this is too
# expensive, you can specify the networks for which a lookup is done, or
# remove the setting entirely.

host_lookup = *


# By default, Exim expects all envelope addresses to be fully qualified, that
# is, they must contain both a local part and a domain. If you want to accept
# unqualified addresses (just a local part) from certain hosts, you can specify
# these hosts by setting one or both of
#
# receiver_unqualified_hosts =
# sender_unqualified_hosts =
#
# to control sender and receiver addresses, respectively. When this is done,
# unqualified addresses are qualified using the settings of qualify_domain
# and/or qualify_recipient (see above).
sender_unqualified_hosts = localhost
### This is needed so Fetchmail can send its warnings for oversized messages.
### so don't remove the "localhost" from it, even if you want to add
### other hosts on the end (a colon seperated list, as usual).


# By default, Exim does not make any checks, other than syntactic ones, on
# incoming addresses during the SMTP dialogue. This reduces delays in SMTP
# transactions, but it does mean that you might accept messages with unknown
# recipients, and/or bad senders.

# Uncomment this line if you want incoming recipient addresses to be verified
# during the SMTP dialogue. Unknown recipients are then rejected at this stage,
# and the generation of a failure message is the job of the sending host.

# receiver_verify

# Uncomment this line if you want incoming sender addresses (return-paths) to
# be verified during the SMTP dialogue. Verification can normally only check
# that the domain exists.

# sender_verify

# Exim contains support for the Realtime Blackhole List (RBL) that is being
# maintained as part of the DNS. See http://mail-abuse.org/rbl/ for background.
# Uncommenting the first line below will make Exim reject mail from any
# host whose IP address is blacklisted in the RBL at blackholes.mail-abuse.org.
# Some others have followed the RBL lead and have produced other lists: DUL is
# a list of dial-up addresses, and there are also a number of other lists
# of various kinds at orbs.org.

# rbl_domains = blackholes.mail-abuse.org
# rbl_domains = blackholes.mail-abuse.org:dialups.mail-abuse.org

# If you want Exim to support the "percent hack" for all your local domains,
# uncomment the following line. This is the feature by which mail addressed
# to x%y@z (where z is one of your local domains) is locally rerouted to
# x@y and sent on. Otherwise x%y is treated as an ordinary local part.

# percent_hack_domains = *


# When Exim can neither deliver a message nor return it to sender, it "freezes"
# the delivery error message (aka "bounce message"). There are also other
# circumstances in which messages get frozen. They will stay on the queue for
# ever unless one of the following options is set.

# This option unfreezes unfreezes bounce messages after two days, tries
# once more to deliver them, and ignores any delivery failures.

ignore_errmsg_errors_after = 2d

# This option cancels (removes) frozen messages that are older than a week.

timeout_frozen_after = 7d

### As Freesco boxes usually have less resources, I have included these
### other options to reduce the burden a little, they are not set by default
### with a normal exim installation.

### Do not perform any delieveries if the loadavg is above this figure
deliver_load_max = 1.5

### Only ever use 3 threads at once for delieveries
smtp_accept_queue= 3
smtp_accept_queue_per_connection = 3

### Set this to 6 if those pesky messages about the queue runs are filling
### up your log and annoying you.
log_queue_run_level = 0

### You can decrease this setting to further reduce the logging on exim,
### however I'd recommened not going below 3; 4 should reduce the messages
### sufficently
log_level = 5

### Set your freesco Timezone offset here, don't forget you will need to change
### it if you change the freesco setting (eg to allow for daylight savings)

timezone = +0000

### NOTE That this timezone setting has been patched for freesco, it does not
### work quite the way it is described on the exim webpage, please keep that
### in mind if you read the website documentation, and/or use a normal version
### of exim elsewhere!


### If you want exim to use GMT for its timestamps then uncomment the following
### line

#timestamps_utc = true

### Now included in this package is a system filter which attempts to
### block mail which has executable (and hence potentially dangerous)
### attatchment(s). It is not fool proof but you may find it helpfull.
### If you wish to use your own system filter in conjunction with this
### you will have to combine the two into one file and add any additional
### filter configuration that your filter may need.
### If you wish to use the system filter provided just uncomment the following
### two lines. You might prefer to use the mailgate package (comming soon)

#message_body_visible = 5000
#message_filter = /mnt/router/packages/exim/attachments.filter


end



######################################################################
# TRANSPORTS CONFIGURATION #
######################################################################
# ORDER DOES NOT MATTER #
# Only one appropriate transport is called for each delivery. #
######################################################################

# A transport is used only when referenced from a director or a router that
# successfully handles an address.


# This transport is used for delivering messages over SMTP connections.

remote_smtp:
driver = smtp
### It is usefull to put your ISP's mailserver here as a fallback host,
### then if delivery fails, exim attempts to pass the message to that
### mail server--reducing the amount in your queue.
### IF your isp blocks OUTGOING smtp connections (i.e. connections to port 25
### on machines which are not your IPS's mail server) you will *have* to use
### this setting to be able to send external mail.
# fallback_hosts =

# This transport is used for local delivery to user mailboxes in traditional
# BSD mailbox format. By default it will be run under the uid and gid of the
# local user, and requires the sticky bit to be set on the /var/mail directory.
# Some systems use the alternative approach of running mail deliveries under a
# particular group instead of using the sticky bit. The commented options below
# show how this can be done.

### Default config would not normally use maildir--I've opted for it for this
### package and the teapop package after some locking problems, maildir
### apparently doesn't even need locking :))
local_delivery:
driver = appendfile
maildir_format = true
directory = /var/mail/$local_part
require_lockfile = true
use_fcntl_lock = true
use_lockfile = true
delivery_date_add
envelope_to_add
return_path_add
group = mail
# mode = 0660
prefix =
headers_add = "Lines: $body_linecount"
quota_warn_threshold = 75%
maildir_tag = ,S=$message_size
quota_size_regex = S=(\d+)($|:.+$)
### If you want to use quota's for users mail (usefull for IMAP) uncomment
### the next line, and edit the value to your needs (decimal point allowed)
# quota = 10M

# This transport is used for handling pipe deliveries generated by alias
# or .forward files. If the pipe generates any standard output, it is returned
# to the sender of the message as a delivery error. Set return_fail_output
# instead of return_output if you want this to happen only when the pipe fails
# to complete normally. You can set different transports for aliases and
# forwards if you want to - see the references to address_pipe in the directors
# section below.

address_pipe:
driver = pipe
return_output


# This transport is used for handling deliveries directly to files that are
# generated by aliasing or forwarding.

address_file:
driver = appendfile
delivery_date_add
envelope_to_add
return_path_add


# This transport is used for handling autoreplies generated by the filtering
# option of the forwardfile director.

address_reply:
driver = autoreply


end



######################################################################
# DIRECTORS CONFIGURATION #
# Specifies how local addresses are handled #
######################################################################
# ORDER DOES MATTER #
# A local address is passed to each in turn until it is accepted. #
######################################################################

# Local addresses are those with a domain that matches some item in the
# "local_domains" setting above, or those which are passed back from the
# routers because of a "self=local" setting (not used in this configuration).


# This director handles aliasing using a traditional /etc/aliases file.
# If any of your aliases expand to pipes or files, you will need to set
# up a user and a group for these deliveries to run under. You can do
# this by uncommenting the "user" option below (changing the user name
# as appropriate) and adding a "group" option if necessary. Alternatively, you
# can specify "user" on the transports that are used. Note that those
# listed below are the same as are used for .forward files; you might want
# to set up different ones for pipe and file deliveries from aliases.

### This has been extended to also allow you to have aliases at
### different domains so user@domain1 and user@domain2 can both be aliases which
### end up in different locations (as long as the domains are listed in
### local_domains near the start of this file)

system_aliases_domains:
driver = aliasfile
file = /etc/aliases
search_type = lsearch
# user = exim
file_transport = address_file
pipe_transport = address_pipe
include_domain

system_aliases:
driver = aliasfile
file = /etc/aliases
search_type = lsearch
# user = exim
file_transport = address_file
pipe_transport = address_pipe

# This director handles forwarding using traditional .forward files.
# If you want it also to allow mail filtering when a forward file
# starts with the string "# Exim filter", uncomment the "filter" option.

# The no_verify setting means that this director will be skipped when
# verifying addresses if sender_verify or receiver_verify is set (though
# they are not set by default). Similarly, no_expn means that this director
# will be skipped if smtp_expn_hosts is set to allow any hosts to use the
# EXPN command.

# The check_ancestor option means that if the forward file generates an
# address that is an ancestor of the current one, the current one gets
# passed on instead. This covers the case where A is aliased to B and B
# has a .forward file pointing to A.

# The three transports specified at the end are those that are used when
# forwarding generates a direct delivery to a file, or to a pipe, or sets
# up an auto-reply, respectively.

userforward:
driver = forwardfile
file = .forward
no_verify
no_expn
check_ancestor
# filter
file_transport = address_file
pipe_transport = address_pipe
reply_transport = address_reply

# This director matches local user mailboxes.

localuser:
driver = localuser
transport = local_delivery


### If all else has failed check if there is a * alias for a default
### mailbox, rather than bouncing the mail. You can have different defaults for
### different domains if you like so *@domain1 goes somewhere different to
### *@domain2 (assuming both domains are listed under your local_domains)

unknown_alias_domains:
driver = aliasfile
file = /etc/aliases
search_type = lsearch*@
# user = exim
file_transport = address_file
pipe_transport = address_pipe

unknown_alias:
driver = aliasfile
file = /etc/aliases
search_type = lsearch*
# user = exim
file_transport = address_file
pipe_transport = address_pipe


end



######################################################################
# ROUTERS CONFIGURATION #
# Specifies how remote addresses are handled #
######################################################################
# ORDER DOES MATTER #
# A remote address is passed to each in turn until it is accepted. #
######################################################################

# Remote addresses are those with a domain that does not match any item
# in the "local_domains" setting above.


# This router routes to remote hosts over SMTP using a DNS lookup. Any domain
# that resolves to an IP address on the loopback interface (127.0.0.0/8) is
# treated as if it had no DNS entry.

lookuphost:
driver = lookuphost
transport = remote_smtp
ignore_target_hosts = 127.0.0.0/8

# This router routes to remote hosts over SMTP by explicit IP address,
# when an email address is given in "domain literal" form, for example,
# <user@[192.168.35.64]>. The RFCs require this facility. However, it is
# little-known these days, and has been exploited by evil people seeking
# to abuse SMTP relays. Consequently it is commented out in the default
# configuration. If you uncomment this router, you also need to comment out
# "forbid_domain_literals" above, so that Exim can recognize the syntax of
# domain literal addresses.

# domain_literal:
# driver = ipliteral
# transport = remote_smtp


end



######################################################################
# RETRY CONFIGURATION #
######################################################################

# This single retry rule applies to all domains and all errors. It specifies
# retries every 15 minutes for 2 hours, then increasing retry intervals,
# starting at 1 hour and increasing each time by a factor of 1.5, up to 16
# hours, then retries every 8 hours until 4 days have passed since the first
# failed delivery.

# Domain Error Retries
# ------ ----- -------

* * F,2h,15m; G,16h,1h,1.5; F,4d,8h

end



######################################################################
# REWRITE CONFIGURATION #
######################################################################

# There are no rewriting specifications in this default configuration file.

end



######################################################################
# AUTHENTICATION CONFIGURATION #
######################################################################

# There are no authenticator specifications in this default configuration file.

### However for Freesco we have some to read the freesco password file
### (but ignore the user ppp), this only occurs for hosts, IP's or IP ranges
### listed in the host_auth_accept_relay setting near the start of this file.

login:
driver = plaintext
public_name = LOGIN
server_prompts = "Username:: : Password::"
server_condition = "${if and {{!eq{${lc:$1}}{ppp}}{!eq{$1}{}}{!eq{$2}{}} \
{crypteq{$2}{${extract{1}{:} \
{${lookup{$1}lsearch{/etc/passwd}{$value}{*:*}}}}}}}{1}{0}}"
server_set_id = $1

plain:
driver = plaintext
public_name = PLAIN
server_condition = "${if and {{!eq{${lc:$2}}{ppp}}{!eq{$2}{}}{!eq{$3}{}} \
{crypteq{$3}{${extract{1}{:} \
{${lookup{$2}lsearch{/etc/passwd}{$value}{*:*}}}}}}}{1}{0}}"
server_set_id = $2

# End of Exim configuration file


Na górę
 Wyświetl profil  
 
 Tytuł:
Post: sobota, 30 listopada 2002, 18:54 
Offline
Honorowy Admin

Rejestracja: piątek, 5 lipca 2002, 17:30
Posty: 7800
Lokalizacja: Słupsk
Wg mnie konfiguracja exima dobra, poczta testowa poszła - serwer ją przyjął - powinna dojść. Pliki z listami są w katalogu /mnt/router/packages/mail/spool - są tam katalogi o nazwie użytkownika a w nich podkatalogi: cur new temp - w katalogu new są pliki z listami...
Żeby odebrać pocztę na swoim kompie z ulubionym windowsem i ulubionym outlookiem potrzebny będzie jeszcze teapop lub courier na serwerze...
Czy masz??


Na górę
 Wyświetl profil  
 
 Tytuł:
Post: niedziela, 1 grudnia 2002, 01:13 
Offline
Użytkownik

Rejestracja: poniedziałek, 4 listopada 2002, 00:50
Posty: 147
owszem mam zainstalowany teapop. A zapomnialem dodac ze poczta nie dziala nawet po lanie. Gdy wysle na moja poczte maila z zewnatrz wraca po 4 godzinach. Nie mam pojecia ale moze trzeba jeszcze cos zmienic w teapop


Na górę
 Wyświetl profil  
 
 Tytuł:
Post: niedziela, 1 grudnia 2002, 01:46 
Offline
Honorowy Admin

Rejestracja: piątek, 5 lipca 2002, 17:30
Posty: 7800
Lokalizacja: Słupsk
Mail wysłany przeze mnie nie wrócił. Standardowo w teapopie nie trzeba zmieniać konfiguracji. Poczta w LANie w tym wypadku działa na takiej samej zasadzie jak ta zewnętrzna. Chyba żeby dodać do ustawień exima nazwe wewnętrzną serwera lub adresować po numerach IP...
TAk jak powiedziałem, list na twój serwer nie został cofnięty - choć pisałem na postmaster, więc jeśli podasz nazwę użytkownika mogę spróbować jeszcze raz...


Na górę
 Wyświetl profil  
 
 Tytuł:
Post: niedziela, 1 grudnia 2002, 09:44 
Offline
Użytkownik

Rejestracja: poniedziałek, 4 listopada 2002, 00:50
Posty: 147
To jest mail jakiego ja uzywac bym chcial rafcio@serwer.ath.cx. A moze zrobiBem jeszcze blad ze nie dodalem uzytkownika no exima. Czytalem na forum ze trzeba to moze to jest przyczyna ?


Na górę
 Wyświetl profil  
 
 Tytuł:
Post: niedziela, 1 grudnia 2002, 15:34 
Offline
Honorowy Admin

Rejestracja: piątek, 5 lipca 2002, 17:30
Posty: 7800
Lokalizacja: Słupsk
Wysłałem z dwóch kont...
Mój exim zakomunikował:
: [/] [] ()
Dec  1 14:41:36 - exim[23309]: 2002-12-01 14:41:36 18IVHo-00063v-00 => rafcio@serwer.ath.cx R=lookuphost T=remote_smtp H=serwer.ath.cx [80.48.78.14]
Dec  1 14:41:36 - exim[23309]: 2002-12-01 14:41:36 18IVHo-00063v-00 Completed

Czyli wszystko w porządku od strony exima. Żadnych dodatkowych użytkowników poza tymi, których trzeba mieć, nie trzeba.


Na górę
 Wyświetl profil  
 
Wyświetl posty nie starsze niż:  Sortuj wg  
Nowy temat Odpowiedz w temacie  [ Posty: 12 ] 

Strefa czasowa UTC+2godz.


Kto jest online

Użytkownicy przeglądający to forum: Bing [Bot] i 13 gości


Nie możesz tworzyć nowych tematów
Nie możesz odpowiadać w tematach
Nie możesz zmieniać swoich postów
Nie możesz usuwać swoich postów
Nie możesz dodawać załączników

Szukaj:
Przejdź do:  
cron
Technologię dostarcza phpBB® Forum Software © phpBB Group
Hosting: Compus-Net
RobertKonik.pl