Sponsored Content
Full Discussion: not activated yet?
Contact Us Forum Support Area for Unregistered Users & Account Problems not activated yet? Post 302204055 by reborg on Tuesday 10th of June 2008 12:17:33 PM
Old 06-10-2008
mcraul,

I just checked on the server and it seems that your mail server is not accepting the mails from the site. I have manually activated you account, but you will not be able to use the subscription and other mail features with that address. Unfortunately your server is not reporting a reason for the failed delivery so we cannot do anything about it from out end.
 

4 More Discussions You Might Find Interesting

1. HP-UX

Activated accounts

Hello all, I am trying to list all accounts that are still activated on a HP-UX trusted system. I have tried to do something with the modprpw command but can't think of any way. Can someone give me a hint? I am not looking for a whole script, this I can do it, but just a way to get that into a... (1 Reply)
Discussion started by: qfwfq
1 Replies

2. Solaris

Solaris user account de-activated, command to activate again

My admin has set password policy to de-activate user account if there is not login for 90 days. How can i re-activate user account w/o deleting, or changing user password. Thanks in advance Deeps (6 Replies)
Discussion started by: admin@solaris
6 Replies

3. Solaris

Why ACL is getting activated on NFS mount..??

Hello All, I am facing a strange problem ( for first time in it's own for the matter of fact ) : Thanks. (1 Reply)
Discussion started by: Reboot
1 Replies

4. Red Hat

Volume group not activated at boot after SAN migration

I have an IBM blade running RHEL 5.4 server, connected to two Hitachi SANs using common fibre cards & Brocade switches. It has two volume groups made from old SAN LUNs. The old SAN needs to be retired so we allocated LUNs from the new SAN, discovered the LUNs as multipath disks (4 paths) and grew... (4 Replies)
Discussion started by: rbatte1
4 Replies
masqmail.get(5) 						   File Formats 						   masqmail.get(5)

NAME
masqmail.get - masqmail get configuration file DESCRIPTION
This man page describes the options available for the masqmail get configuration. OPTIONS
protocol = string The protocol with which you retrieve your mail. Currently only `pop3' and `apop' are supported. There is no default. server = string The server you get your mail from. port = number The port number of server to connect to. Default: 110. resolve_list = list Specify the method how the domain of the server is resolved. Possible values are dns_mx, dns_a, byname. For `dns_mx', the domain is assumed to be an MX pointer to a list of host names, these will be tried each in order (lowest preference value first, equal preference values in random order). For `dns_a', the domain is assumed to be an A pointer. For `byname', the library function gethostbyname(3) will be used. The default is "dns_a;byname". It does not make much sense here to use `dns_mx'. user = string Your login name. pass = string Your password. address = address The address where the retrieved mail should be sent to. It can be any address, but you probably want to set this to a local address on your LAN. return_path = address If set, masqmail sets the return path to this address. Bounces generated during further delivery will be sent to this address. If unset, masqmail looks for the Return-Path: header in the mail, if this does not exist it uses the From: address and if this fails, postmaster will be used. It is in most cases not useful to set this to the same address as the `address' option as this may generate multiple bounces. post- master is recommended. do_keep = boolean If you want to keep your mail on the server after you retrieved it, set this to true. It is recommended that you also set do_uidl, otherwise you will get the mail again each time you connect to the server. Masqmail does not check any headers before it retrieves mail, which may mark it as already fetched. Note that this behaviour is different to that of fetchmail. The default is false. do_uidl = boolean If set, masqmail keeps a list of unique IDs of mails already fetched, so that they will not be retrieved again. Default is false. do_uidl_dele = boolean If set, and do_uidl is also set, MasqMail sends a delete (DELE) command to the server for each message uid in the uid listing at the beginning of the session. This prevents mail to be left on the server if masqmail gets interrupted during a session before it can send the QUIT command to the server. Default is false. max_size = numeric If set to a value > 0, only messages smaller than this in bytes will be retrieved. The default is 0. max_count = numeric If set to a value > 0, only max_count messages will be retrieved. The default is 0. max_size_delete = boolean If max_size > 0 and do_uidl_dele is set, delete messages that are larger than max_size on the server WITHOUT retrieving them. Be careful with this option. Default: false wrapper = command If set, instead of opening a connection to a remote server, command will be called and all traffic will be piped to its stdin and from its stdout. Purpose is to tunnel ip traffic, e.g. for ssl. Example for ssl tunneling: wrapper="/usr/bin/openssl s_client -quiet -connect pop.gmx.net:995 2>/dev/null" AUTHOR
Masqmail was written by Oliver Kurth. It is now maintained by Markus Schnalke <meillo@marmaro.de>. You will find the newest version of masqmail at http://marmaro.de/prog/masqmail/. There is also a mailing list, you will find information about it at masqmail's main site. BUGS
Please report bugs to the mailing list. SEE ALSO
masqmail(8), masqmail.route(5), masqmail.conf(5) masqmail-0.2.30 2011-07-27 masqmail.get(5)
All times are GMT -4. The time now is 02:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy