i was sending mail from my server ip is completely new and tested . thhe mail i am sending is html mail but not a single mail is getting delivered in my webmail i am getting this error
A message that you sent was rejected by the local scanning code that
checks incoming messages on this system. The following error was given:
This message was classified as SPAM and may not be delivered
------ This is a copy of your message, including all the headers. ------
i tried disabling spamassisn but no luck .
i searched everywhere did several changes in whm tweak settings but all mails are going in not even spam all are being rejected by server
Related
I'm using zen.spamhaus.org in my sendmail config.
FEATURE(dnsbl',zen.spamhaus.org')dnl
I'm using AWS SES to send email and when I try to relay an email I get:
Nov 9 09:01:00 Web-Mail sendmail[12751]: ruleset=check_relay, arg1=e226-2.smtp-out.us-east-2.amazonses.com, arg2=127.255.255.254, relay=e226-2.smtp-out.us-east-2.amazonses.com [23.251.226.2], reject=550 5.7.1 Rejected: 23.251.226.2 listed at zen.spamhaus.org
But if I go to the the spamhaus website and check the IP it says there are no issues.
https://check.spamhaus.org/not_listed/?searchterm=23.251.226.2
23.251.226.2 has no issues
This has just started happening recently. I tried white listing the SES server in my access.db to no avail.
Any help would be appreciated.
I tried white listing the SES server in my access.db to no avail.
Also tried sbl.spamhaus.org with the same results.
Turns out it's also blocking other valid MTA's
Nov 9 09:43:26 Web-Mail sendmail[12990]: ruleset=check_relay, arg1=mail-dm6nam10olkn2106.outbound.protection.outlook.com, arg2=127.255.255.254, relay=mail-dm6nam10olkn2106.outbound.protection.outlook.com [40.92.41.106], reject=550 5.7.1 Rejected: 40.92.41.106 listed at zen.spamhaus.org
Which explains why I'm getting reports from other people saying their emails are being returned.
I am experiencing a similar issue, lots of people receiving rejected email notices because of zen.spamhaus.org wrongly sending blocked responses.
As you have found going to the spamhaus website indicates no issues with the ips.
But this is the only mention of the issue that I can find!
I am using postfix
I ahve removed zen.spamhause.org from my smtpd_recipient_restrictions config for now and things are returning to normal.
Looks like the DNS for zen.spamhaus.org isn't resolving. Could be the issue
Ok looks like I was rate limited - I am working on a project that sent my 203 emails in error. I think I fell foul of samhaus's rate limiter for too many queries in a short time.
I have written an application, that successfully listens to a multicast-host 239.255.255.250:1900 and [FF02::C]:1900. I receive the desired NOTIFY and M-SEARCH messages using spring-integration-ip's MulticastSendingMessageHandler.
However: while I am able to send messages using the UnicastSendingMessageHandler, it does not seem like e.g. VLC will recognize my running server.
I went through the UPnP Device Architecture PDF back and forth and manually sent the 3+2+1 NOTIFY messages and also responded to M-SEARCH, but somehow I am not able to make e.g. VLC recognize my server.
I also see no access on my HTTP server (separate application on a different port, but properly linked in the LOCATION attribute of the NOTIFY and M-SEARCH-response messages). No attempts at all.
Do I need to send the data using MessageHeaders (headers) instead of payload? What's the pre-requisite for a possible media server to be listed? Sending the NOTIFY messages? Responding to M-SEARCH messages? More?
And what are the allowed devicetype and servicetype values? Or do they vary?
If anyone wants, I can add some code, but the listening part is working alright and messages are sent, just supposedly not understood by their receivers (sending using Unicast to the address, who sent the M-SEARCH message, but on port 1900).
Honestly: I am not sure how to even word my question(s). I tried reading through the RSSDP source code, but I still do not fully get it.
Any pointers are greatly welcomed.
I am using AWS SES to send emails from OTRS and emails are not working. Below is the error:
Mar 18 06:22:47 ip-10-210-28-141 OTRS-otrs.Console.pl-Maint::Email::MailQueue-09[30010]: [Error][Kernel::System::CommunicationLog::_LogError][Line:538]: CommunicationLog(ID:795,AccountType:-,AccountID:-,Direction:Outgoing,Transport:Email,ObjectLogType:Message,ObjectLogID:2233)::Kernel::System::MailQueue => Message could not be sent! Error message: Can't connect to email-smtp.us-east-1.amazonaws.com: !
I am able to telnet to email-smtp.us-east-1.amazonaws.com
I am able to send emails using SES from the same server via command line but OTRS is not sending email.
It's hard to debug OTRS. In your case OTRS was not possible to create an mail object. The cause can have several issue.
Maybe you are using the wrong SMTP backend module, there are 3 different options, SMTP/SMTPS and SMTPTLS (see also https://github.com/OTRS/otrs/tree/master/Kernel/System/Email)
To get more verbose feedback from the CPAN SMTP module, set $Self->{Debug} = 3; at this place https://github.com/OTRS/otrs/blob/master/Kernel/System/Email/SMTP.pm#L32 and check STDOUT what the problem is.
I noticed today that mails do not come through. Since several hours ago, all mails just get stuck in queue. I have tried to deliver them manually, by selecting one mail in WHM Mail Queue Manager and clicking on "Deliver Selected", but after few minutes I just get this error:
Code:
LOG: MAIN
cwd=/usr/local/cpanel/whostmgr/docroot 4 args: /usr/sbin/exim -v -M 1Tli6y-0002Xo-KW
delivering 1Tli6y-0002Xo-KW
Connecting to foobar.TLD [IP.ADDRESS]:25 ... failed: Connection timed out (timeout=5m)
LOG: MAIN
foobar.TLD [IP.ADDRESS] Connection timed out
LOG: MAIN
== info#foobar.TLD R=dkim_lookuphost T=dkim_remote_smtp defer (110): Connection timed out
I have searched on net, and I have found thread on this forum, similar error - http://forums.cpanel.net/f43/t-remote_smtp-defer-53-retry-time-not-reached-any-host-72383.html
and there is proposed solution, but I am not sure should it work in my case. I can not risk loosing emails in queue, my clients would hang me :)
I can see your server is unable to connect remote server to send your mail. Because you are getting "25 ... failed: Connection timed out" error in logs. I think your mail server IP is blacklisted in anti-spam databases and maybe due to that you are getting this issues.
run command
exim -bt info#foobar.tld
Copy ip address and add your CSF white list.
Or turn of Firewall and retest.
I am serving my Rails 3 app on Heroku, my mail through Google, and the domain through Enom. This is for www.challengage.com
This works 95% of the time, however, once in a while, when someone tries to reply to an email I send them, it fails with the below error message because my email, josh#challengage.com, somehow got replaced with josh#herokuapp.challengage.com when they recieved it. I think it has something to do with Mail Delivery Subsystems, but I'm not sure. It also only seems to happen when emailing University professionals.
Error Message:
From: Mail Delivery Subsystem [mailto:MAILER-DAEMON#smtp2.syr.edu]
Sent: Monday, July 15, 2013 2:08 PM
To: David DiMaggio
Subject: Undeliverable: FW: Challengage - Work Team Simulation product for interviewing evaluations
Delivery has failed to these recipients or groups:
paul#challengage.herokuapp.com
The server has tried to deliver this message, without success, and has stopped trying. Please try sending this message again. If the problem continues, contact your helpdesk.
The following organization rejected your message: challengage.herokuapp.com.
Any ideas?
Thanks everyone.
This is almost certainly because you're using a CNAME for your email records.
Although most email servers will reflect the original domain when sending a message, others will replace it with the domain that's at the end of the CNAME.
This means that instead of sending to someone#challengage.com they send to someone#challengage.herokuapp.com instead.
The mail server sees the request to send to someone#challengage.herokuapp.com and decides that it doesn't look after challengage.herokuapp.com and so from it's perspective the message is rejected.
We used to see this issue with CloudMailin customers and started to recommend that they don't use CNAMES where email is involved and just make use of adding MX records direct to the Apex domain.
With Heroku this poses a problem though as you don't have a single IP that you can use to access their servers. We eventually ended up using Route 53 to host our domain, then adding an SSL endpoint (to get load balancer details) and then adding that load balancer to Route 53's Alias command so that it automatically always gave the correct results. Alternatively you can setup some sort of static IP based system on your apex domain to redirect.