Really quick one - I am attempting to use mailgun for my email.
One of the requirements is to add a CNAME = mailgun.org
I am attempting to do this via WHM - and can successfully create the record under 'Edit DNS Zone' for the domain.
The problem is that it is auto-appending my domain name after the 'mailgun.org' entry
So when I save the record gets saved as mailgun.org.mydomainname.com
How can I stop the auto-append of my domain name to a CNAME??
For anyone who has this problem the answer is simple - just add a fullstop after mailgun.org (mailgun.org.)
Simplest things but when you don't know them they can be a real pain!
I had the same problem and solved it by adding an extra blank after entering mailgun.org.
So type the following: mailgun.org.(add a space after the final period)
Related
I have two accounts: account_1 and account_2 with two different e-mails, mail_1 and mail_2, respectively (both the accounts are backed-up, there is no concern of work loss).
I am a part of Team_X with account_1 and mail_1, but I am told to be a part of Team_X with account_2 & mail_2.
Does, renaming account_1 to account_old and renaming account_2 to account_1 suffice the requirement?
Or, do I have to additionally change my primary mail address from mail_1 to mail_2 too?
Or, are there any other steps that you can perform?
The best way would be ask the Team manager or concerned person to remove your old account from Team_X and add new new one. This will impact your work and commit history, You new user id will be shown for new commits.
another better way would be just remove your mail_1 from account_1 and mail_2 from account_2 and attach the mail_2 to account_1. Now you can change your username from account_1 to account_2.
There are repercussion of doing these things.
Like After changing your username, your old username becomes available
for anyone else to claim. If the new owner of your old username creates a repository
with the same name as your repository, that will override the redirect
entry and your redirect will stop working.
So deal it with precautions.
Newly Created subscription for new report fails with error " Failure sending mail: The specified string is not in the form required for an e-mail address.Mail will not be resent."
It is defined in the same way the existing one, using same ReportServer with unchanged config since it started working.
Using full email addresses (user.name#do-main.co.uk), existing SMTP Server that is set up on Exchange Server (working, other services use it successfully) but queue does not pick up new subscription emails. Security is individually managed for this report (limited acces, users added using full DOMAIN\User Name notation).
There were changes in firewall/proxy settings, but SSRS is internal anyway so don't see the connection..
Where else can I look to see what's the problem?
I deleted subscriptions and recreated them from scratch. And no errors, all works fine. Funny part is that I entered email addresses manually, in contrast with previous attempts on copy&paste them from elsewhere.
Still weird.
it is possible that when you copied they were including characters, the names must match exactly. I have had this issue, very finicky...
here are some helpful scripts for analyzing subscriptions, Microsoft does not make it easy to identify individual users and reports in the back-end, but you may find the typo here if there is one hiding:
;
WITH subscriptionXmL
AS (
SELECT SubscriptionID
,OwnerID
,Report_OID
,Locale
,InactiveFlags
,ExtensionSettings
,CONVERT(XML, ExtensionSettings) AS ExtensionSettingsXML
,ModifiedByID
,ModifiedDate
,Description
,LastStatus
,EventType
,MatchData
,LastRunTime
,Parameters
,DeliveryExtension
,Version
FROM ReportServer.dbo.Subscriptions
)
,
-- Get the settings as pairs
SettingsCTE
AS (
SELECT SubscriptionID
,ExtensionSettings
,
-- include other fields if you need them.
ISNULL(Settings.value('(./*:Name/text())[1]', 'nvarchar(1024)'), 'Value') AS SettingName
,Settings.value('(./*:Value/text())[1]', 'nvarchar(max)') AS SettingValue
FROM subscriptionXmL
CROSS APPLY subscriptionXmL.ExtensionSettingsXML.nodes('//*:ParameterValue') Queries(Settings)
)
SELECT *
FROM SettingsCTE
WHERE settingName IN ('TO', 'CC', 'BCC')
Also find this lovely article about setting up subscriptions:
http://www.sqlcircuit.com/2012/10/ssrs-implementation-of-file-share.html
I have a windows shared hosting. I have three domains hosted here.
1. www.mysite.com <-------- Primary domain
2. www.friendsite.com <------- hosted in friendsite folder/sub-directory.
3. www.anothersite.com <------ hosted in anothersite folder/sub-directory.
Above three domains are working properly. But the problem is when I open www.mysite.com/friendsite, www.friendsite.com contents are visible or if I open www.mysite.com/anothersite, www.anothersite.com contents are visible as these are hosted in two sub-directories.
Is there any way to block the view of these particular sub-directories through the primary domain i.e. www.mysite.com/friendsite or www.mysite.com/anothersite ?
I don't want to block www.friendsite.com and www.anothersite.com. I just want to block www.mysite.com/friendsite and www.mysite.com/anothersite.
.htaccess will not work as it is a windows shared hosting, but web.config may work in this problem but I do not know how.
I think, I described my problem properly.
Please do not mark this question as duplicate.
Are you not able to have a directory structure such as:
/websites/mysite
/websites/friendsite
/websites/othersite
The in IIS, create 3 different sites, each with its unique base directory, and set the bindings on the site itself to:
1. www.mysite.com:80
2. www.friendsite.com:80
3. www.othersite.com:80
??
To be clear, I want to extract the sender IP's from a GROUP of emails without going to file | properties on every single one. There are a great many to go through.
Output to a text file would be fine.
I am wondering if this is possible? Perhaps there's an app for that!
Thanks for your time.
Is this a programming question? You would need to extract the PR_TRANSPORT_MESSAGE_HEADERS property (DASL name http://schemas.microsoft.com/mapi/proptag/0x007D001F) using MailItem.PropertyAccessor.GetProperty and parse the data explicitly in your code. The IP address is not guaranteed to be there of course.
This is my 1st question on this forum... So, please, be indulgent !
I'm using TYPO3 4.7.11 (PHP 5.3.3) with extension direct_mail 3.1.1 for the intranet site of a non-profit firm.
My problem (maybe connected to Bug #51583 : http://forge.typo3.org/issues/51583) is that, after numerous tests and attempts, it seems impossible to have an updated version of a page saved as draft for newsletter in an automatic scheduler driven way : the same newsletter is produced with the same informations that were already there on the day it was first created and saved.
The specific page used for newsletter includes a content element 'Menu/Sitemap' with 'Recently updated pages' as 'Menu type'. It has been saved as 'draft (for recurring sendings)' in Direct Mail.
The scheduler contains these 2 tasks with recurring type :
- Direct Mail: Create Mail from Draft (direct_mail)
- Direct Mail: Mailing Queue (direct_mail)
Note : the manual way is fully functional and the newsletter produced is really updated. Same with option "Testmail - Simple" !
So, my problem seems to be linked to the automatic scheduled mailing ! It looks as if the newsletter draft has turned into a freezed snapshot of a specific moment and that Typo3 is unable to update/recalculate this page when invoked in scheduler mode.
On the web, I saw reported problems that could be related like "When mails get sent via the scheduler the same subject is used for all sendings ( https://review.typo3.org/21313 )" and "Adding hooks when sending direct mails via scheduler ( forge.typo3.org/issues/48994 )", but these issues seem to be fixed with direct_mail 3.1.1 version.
I made these observations and, in my opinion, there is some relevancy :
1.There is no domain proposed in the 'Domain of internal links' drop-down list in 'Set default values for mail content fetching options' in Direct Mailer, and yet I have a single record in sys_domain table with a domain name (with no protocol and no final slash). Is there a reason why this record is not considered good, or isn't it the right table ? (uid=3, pid, tstamp, crdate, cruser_id, hidden, sorting, prepend_params and forced=0, redirectHttpStatusCode=301, domain_name=site.subdomain.domain, redirectTo=)
2.In the Typo 3 Log, I get this systematic error message for user _cli_scheduler#LIVE :
Core: Error handler (BE): PHP Warning: Invalid argument supplied for
foreach() in
...typo3conf/ext/direct_mail/Classes/Scheduler/MailFromDraft.php line
125.
The concerned part of MailFromDraft.php is this function : initializeHookObjects
...
/*
* Initializes hook objects for this class
*
* #return void
*/
function initializeHookObjects() {
foreach ($GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['direct_mail']['mailFromDraft'] as $hookObj) {
$hookObjectInstance = t3lib_div::getUserObj($hookObj);
if (is_object($hookObjectInstance) && ($hookObjectInstance instanceof x_directmail_Scheduler_MailFromDraftHook)) {
$this->hookObjects[] = $hookObjectInstance;
}
}
}
...
I'm not sure of understanding very clearly the origin and the use of the hook Object... (in spite of this interesting article by Robert Lemke : typo3.org/documentation/article/how-to-use-existing-hooks-in-your-own-extension/ )
3.Nothing like the apparently requested GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['direct_mail']['mailFromDraft'] seems to exist in TYPO3_CONF_VARS (Global configuration).
Can anybody give me an advice or a clue about what's going on and why I can't get a weekly updated newsletter with the scheduler ? I feel a bit confused !
Thanks in advance for any suggestion or solution (if a miracle is possible).
Greetings.
P-H SILLIAU
I've read about this issue before, but couldn't remember where.
Googling "direct_mail draft (for recurring sendings)" helped.
Try this bug: http://forge.typo3.org/issues/4421
User Markus says:
Things work fine, when you set a domain-record in your system and
select it in the direct_mail settings!
If you don't have a domain-record and specify it in the direct_mail
setup you're able to send normal newsletters, but if you try the
draft-functionality it won't work because the getUrlBase function in
class.tx_directmail_static.php returns an unsuable URL to the System
so it can't use the fetchHTML($file) and quits - therefore not
replacing the old draft contents created when starting the first time.
I don't really get why this works the first time you set up the draft
though....
So setting up the domain-record is a work-around that works.
I hope it does!
Probably, you will find more related topics.
Else, workarounds would be
re-considering the task. As it's a NPO intranet, maybe requirements are not that required suddenly, if asked again :-)
setting up a custom notification tool that only does that precise job.
To put an end to this problem, after many attempts (and informations gleaned from the internet), here is the solution we finally used in our specific case to make the newsletter work :
1st. We created a record in table sys_domain. This was a recurrent instruction in the manual and the forums, and it was IMHO legitimate.
Important : note that the redirectTo field had to remain empty, due to global malfunction of the site if filled (whatever we put in it like /, /var/www/sitename, ...)
2nd. All images, CSS, JS included in template had to be hardcoded (i.e. http ://site/fileamin/images/xxx.png for instance). If we didn't do that, the result would have been an abort in the production of the newletter : Not Found... Maybe, by digging a bit deeper, should we be able to find a parameter we forgot or neglected in some way to solve this issue...
3rd. In the newsletter template TS setup, we added these 2 parameters :
mod.web_modules.dmail.use_domain=[uid of sys-domain]
config.absRefPrefix = / (in order to get rid of PHP DOCUMENT_ROOT (or TYPO3_DOCUMENT_ROOT ?) otherwise wrongly present in all generated links.)
The result is now a well dynamically-generated newsletter, the date is OK, all links are correct and realUrl-compliant (no ../index.php?id=nnn) .... and you know what ?... We're happy ! :-)
Hope it will help !
Many thanks to everybody who answered (Markus, Urs...) or even thought of a possible solution...
P-H Silliau