Block outgoing email because of VPN server

We have Cisco VPN on ASA for over 4 years. Recently, barracudacentral.org blocks our outgoing email because of these reasons: •Your email server contains a virus and has been sending out spam. •Your email server may be misconfigured. •Your PC may be infected with a virus or botnet software program. •Someone in your organization may have a PC infected with a virus or botnet program. •You may be utilizing a dynamic IP address which was previously utilized by a known spammer. •Your marketing department may be sending out bulk emails that do not comply with the CAN-SPAM Act. •You may have an insecure wireless network which is allowing unknown users to use your network to send spam. •In some rare cases, your recipient's Barracuda Spam Firewall may be misconfigured. This is the undeliverable message: barracudacentral.org rejected your message to the following e-mail addresses and  gave this error: Service unavailable; Client host [VPN IP address-illinois.hfc.comcastbusiness.net] blocked using Barracuda Reputation; http://bbl.barracudacentral.com/q.cgi?ip=VPN IP Address The IP address they blocks is our VPN server. Why?                   

gmail issue
Your post is the 4th one already this morning.
This is a gmail issue, contact them.

Similar Messages

  • The email message cannot be sent. Make sure the outgoing email settings for the server are configured properly

    i have an issue when loading a workflow. it gives me a following error "The email message cannot be sent. Make sure the outgoing email settings for the server are configured properly". it doesnt send me any alerts and worlflow fails at the end
    with the above error message.

    Hi,
    I agree with Bistesh. But after Outgoing e-mail settings are configured properly, if the issue still exists,
    It may result from your Anti-Virus. Please refer to the following steps:
    Open MCAfee Console and go to Access Protection window.
    Click Anti-Virus Standard Protection and edit “prevent mass mailing 
    worms from sending emails” rule.
    Now we need to know which processes are being blocked therefore we need to check the MCAfee Log located at
    C:\Documents and Settings\All Users\Application Data\McAfee\DesktopProtection\AccessProtectionLog.txt
    you may find entries of DtExec , DtExecUI and DatabaseMail90, now these processes need to be entered in the exclusion list of selected rule .
    Reset the IIS And SharePoint Timer service to check if this works for you.
    Here are some similar issues with you, you can use as a reference:
    http://social.technet.microsoft.com/Forums/en-US/667f0d61-4914-43fa-80c1-8cf430b113bb/workflow-email-not-working-but-normal-email-alerts-working-fine?forum=sharepointgeneralprevious
    http://techsuite.wordpress.com/2008/12/08/workflow-history-the-email-message-cannot-be-sent-make-sure-the-outgoing-email-settings-for-the-server-are-configured-properly/
    Best Regards,
    Lisa chen

  • Inpect and block outgoing emails.

    Hello, I am new in Exchange Server Development. My task is to create TransportAgent that can inspect and sometimes block outgoing emails. It is important for me to inspect and block internal emails too(not only emails going out of organization). I need to
    support Exchange 2010, 2013.
    Thanks in advance,
    Vitaly

    As others have mentioned probably what you want can be done via Transport Rules.
    However if you have some form of content that can't be caught with Rules and you want to use a Transport Agent then.
    >> It is important for me to inspect and block internal emails too(not only emails going out of organization). I need to support Exchange 2010, 2013.
      Then using a routing agent
    http://msdn.microsoft.com/en-us/library/office/aa563310(v=exchg.150).aspx (the OnSubmittedMessage is probably the most appropriate) and
    http://msdn.microsoft.com/en-us/library/office/aa579261(v=exchg.150).aspx#Namespaces is the way to go as this will catch both Internal and External email. If you want to write one agent that will work on both 2010 and 2013 then you want compile with the
    2010 binaries and then use the
    http://technet.microsoft.com/en-us/library/jj591524(v=exchg.150).aspx on 2013 (or just compile a different version for 2010 and 2013).
    Cheers
    Glen

  • Hi, i am having trouble with my mac mail account, i cannot send or receive any emails because of the server connection problems. Message says it could not be connected to SMTP server. Thanks in advance for your help.

    Hi, i am having trouble with my mac mail account, i cannot send or receive any emails because of the server connection problems. Message says it could not be connected to SMTP server. Thanks in advance for your help.

    Hello Sue,
    I have an iPad 3, iPad Mini and iPhone 5S and they are all sluggish on capitalisation using shift keys. I hope that Apple will solve the problem because it is driving me crazy.
    I find using a Microsoft Surface and Windows 8 phone, which I also have, work as well as all the ios devices before the ios 7 upgrade.
    It has something to do with the length of time that you need to hold the shift key down. The shift key needs to be held longer than the letter key for the capitalisation to work. For some reason, this is a major change in the way we have learnt to touch type on computers. I am having to relearn how to type!
    Michael

  • Airport blocking outgoing emails?

    Hi, I have a new airport extreme and it seems that it is causing problems with outgoing email, I can recieve emails but can't send, when I try it says my smtp settings are wrong. My smtp settings are definitley right, is there a firewall interfering?. Any ideas how to fix this?
    Thanks
    Howie

    Did you change any of the ports on the AirPort Extreme, particularly port 25? Can you open up a terminal window and telnet to port 25 on your smtp server? If you don't know how to telnet to port 25 on your server, then let's suppose your smtp server's name is smtp.some.com, so you would type
    telnet smtp.some.com 25
    If that works when your Mac is directly connected to your network (no wi-fi), but fails when it is using wi-fi, there is indeed a problem. If it fails when directly connected, call your ISP to ask for assistance.

  • Blocked outgoing email in Exchange

    We are running SBS 2003 with Exchange Server 2003. The purpose of this question is more of an understanding how email works with exchange server. The problem started about two weeks ago when we switched ISP to Comcast. At that moment email was being blocked
    by Hotmail and Gmail. We would get the following message back.
    There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.
    <nhnr.org #5.5.0 smtp;550 OU-002 (COL004-MC4F51) Unfortunately, messages from 73.189.0.xxx weren't sent. Please contact your Internet service provider since part of their network is on our block list. You can also refer your provider to <a href="http://mail.live.com/mail/troubleshooting.aspx#errors.>"
    target="_blank">http://mail.live.com/mail/troubleshooting.aspx#errors.>
    MXTOOLBOX says that the public ip address comes on one blacklist - Spamhaus ZEN.
    Here is the question. If I send mail through exchange to a hotmail account it will be bounced back and undeliverable with the above message. If I configure a POP account and send an email to hotmail it will successfully go through. Why does the POP work and
    not the Exchange?
    Thanks
    Chris

    Thanks for the reply.
    Are you configuring the Exchange server as your SMTP server for your POP3 client?
    That is correct.
    I'll also ask the following, to see if we can fix your Exchange delivery issue:
    Do you have an SPF record in DNS?
    Yes we do have an SPF record setup in DNS zone file.
    Have you configured your system to send through the COMCAST SMTP systems, or are you sending direct using DNS? If so, is the IP address of this system included in the SPF record you have in DNS?
    The mail is setup to be sent through DNS.  Are you talking about the public IP address or the IP address of the server?  Either way neither of those IP address are in the SPF record. 
    If not, is your own IP address included in your SPF record in DNS?
    The mail is hosted by Bluehost and their IP address is in the SPF record.
    Have you contacts SpamHaus to determine why your IP address is on their blocklist?
    No I have not contacted SpamHaus yet.  I initially thought that is was Comcast problem but then they said it was not.  Anyway after trying different things I setup an email account (not using exchange) and was able to send email to the
    previously blocked addresses.  So I thought it might be some config problem.

  • Verzon Blocking Outgoing Email Server

    Have read on other posts regarding something like this. Its not the port as I have chanced between 25 and 587. There is no set up issue and no I do not need to reinstall Windows.
    I have three ISPs due to frequent travel. In the US I am able to send and reveive email from my Verizon account using Outlook without problems. Can even do this using a Verizon compeitor's servie to access the Internet.
    When abroad, incoming email using Verizon is OK. Outgoing is blocked. This is consistent.
    Can Verizon comment on this? Either admit it and I will find an alternative or provide a solution. A "whitelist" inquiry was made but unanswered. I read on another post where Verizon danced around a FIOS cussomers exact same complain.
    You have 2 business days or I'm filing an FCC complaint and encouraging everyone with the same problem to do so. It's not so much the blocking but hte failure to provide a workaround for legitimate use, failure to answer, and inclination to be indifferent while taking money form customers.

    If I understand your complaint correctly, you are unable to use Verizon's outgoing server (outgoing.verizon.net) on networks outside of the US.
    What error are you getting?
    If a forum member gives an answer you like, give them the Kudos they deserve. If a member gives you the answer to your question, mark the answer as Accepted Solution so others can see the solution to the problem.
    "All knowledge is worth having."

  • Does Verizon block outgoing email?

    I have three email accounts, one from gmail and two from owned domains.  I use Thunderbird to recieve and send email.  For the past week, I have not been able to send email from one of my email accounts.  This is the error that I receive:
    An error occurred while sending mail.  The mail server responded: Unauthorized relay msg rejected. Please check the message recipients and try again.
    I have checked my settings, and nothing has changed in the last week.  The only "work around" I have is to use send through one of my other email addresses.
    Email comes in fine for all three email addresses.  And I can send fine with two of them, gmail and one of my owned domains.
    Please let me know if Verizon has started to block the sending of some emails and what I might be able to do about it.
    Thank you,
    Anne Plouffe

    Verizon recently started implementing port 25 blocking as a way to combat spammers on their network. If you are using your non-verizon.net address to send via a pop3 client, this may be the cause of your issue.
    There is more information available at http://www.verizon.net/port25
    If you have any questions about the information found there just say so, and myself or one of the other forum members will do our best to find an answer for you.
    Hope this helps!
    If a forum member gives an answer you like, give them the Kudos they deserve. If a member gives you the answer to your question, mark the answer as Accepted Solution so others can see the solution to the problem.
    "All knowledge is worth having."

  • Outgoing emails not sending, error 'server does not allow relaying.

    This IPhone 4 is new, I have made sure that all the credentials are correct and the outgoing settings are set up but still the emails won't send.
    I just sold my Blackberry which sends emails better then any other phone, I need this e-mail for work, please help?

    No it is a AOL account, any ideas?

  • Outgoing Email Delay with Lion Server

    Hi;
    I have setup my domain and greylisting disabled in /etc/postfix/main.cf.
    It seems that I have 3 messages sitting in the mail queue which cannot be delivered due to being delayed for whatever reason.
    I can send email to myself and it's instant.
    I am attempting to email to a friend on Rogers Yahoo and Gmail.  It seems that when I try to connect to the MX for each I timeout for some reason.
    Any ideas on what could be wrong?  I am assuming that since I cannot connect to the MX for those systems that's why it's delayed.
    From what I can see, my server is trying to connect to port 25 on the remote system - as far as I know, those ports are off on Yahoo and GMail.  How can I force it to send to port 587 instead?
    My Server Firewall = Off.
    On the Airport Extreme, these ports are forwarded to the server:  25,110,143,587,993,995
    on rate 2/60s for (submission:99.226.73.47) at Oct  3 13:05:56
    Oct  3 13:09:16 server postfix/anvil[6365]: statistics: max connection count 1 for (submission:99.226.73.47) at Oct  3 13:05:26
    Oct  3 13:09:16 server postfix/anvil[6365]: statistics: max cache size 1 at Oct  3 13:05:26
    Oct  3 13:09:23 server postfix/smtp[6390]: connect to mx2.rog.mail.yahoo.com[98.139.214.154]:25: Operation timed out
    Oct  3 13:09:23 server postfix/smtp[6389]: connect to alt3.gmail-smtp-in.l.google.com[209.85.229.26]:25: Operation timed out
    Oct  3 13:09:23 server postfix/smtp[6390]: DB12F55B8B: to=<[email protected]>, relay=none, delay=503, delays=383/0.04/120/0, dsn=4.4.1, status=deferred (connect to mx2.rog.mail.yahoo.com[98.139.214.154]:25: Operation timed out)
    Oct  3 13:09:53 server postfix/smtp[6389]: connect to alt4.gmail-smtp-in.l.google.com[74.125.79.27]:25: Operation timed out
    Oct  3 13:09:53 server postfix/smtp[6389]: 4F58255B30: to=<[email protected]>, relay=none, delay=656, delays=506/0.04/150/0, dsn=4.4.1, status=deferred (connect to alt4.gmail-smtp-in.l.google.com[74.125.79.27]:25: Operation timed out)
    Oct  3 13:19:19 server postfix/qmgr[6000]: DB12F55B8B: from=<[email protected]>, size=119078, nrcpt=1 (queue active)
    Oct  3 13:19:49 server postfix/smtp[6478]: connect to mx1.rog.mail.yahoo.com[98.136.59.15]:25: Operation timed out
    Oct  3 13:20:19 server postfix/smtp[6478]: connect to mx1.rog.mail.yahoo.com[98.139.214.154]:25: Operation timed out
    Oct  3 13:20:49 server postfix/smtp[6478]: connect to mx2.rog.mail.yahoo.com[98.136.59.15]:25: Operation timed out
    Oct  3 13:21:19 server postfix/smtp[6478]: connect to mx2.rog.mail.yahoo.com[98.139.214.154]:25: Operation timed out
    Oct  3 13:21:19 server postfix/smtp[6478]: DB12F55B8B: to=<[email protected]>, relay=none, delay=1220, delays=1100/0.02/120/0, dsn=4.4.1, status=deferred (connect to mx2.rog.mail.yahoo.com[98.139.214.154]:25: Operation timed out)
    Oct  3 13:24:19 server postfix/qmgr[6000]: 4F58255B30: from=<[email protected]>, size=1249, nrcpt=1 (queue active)
    Oct  3 13:24:23 server postfix/postscreen[6525]: CONNECT from [17.148.16.105]:60340
    Oct  3 13:24:23 server postfix/postscreen[6525]: PASS OLD [17.148.16.105]:60340
    Oct  3 13:24:23 server postfix/smtpd[6526]: connect from asmtpout030.mac.com[17.148.16.105]
    Oct  3 13:24:24 server postfix/smtpd[6526]: 4233F55D22: client=asmtpout030.mac.com[17.148.16.105]
    Oct  3 13:24:24 server postfix/cleanup[6534]: 4233F55D22: message-id=<[email protected]>
    Oct  3 13:24:24 server postfix/qmgr[6000]: 4233F55D22: from=<[email protected]>, size=1217, nrcpt=1 (queue active)
    Oct  3 13:24:24 server postfix/smtpd[6526]: disconnect from asmtpout030.mac.com[17.148.16.105]
    Oct  3 13:24:25 server postfix/smtpd[6536]: connect from localhost[127.0.0.1]
    Oct  3 13:24:25 server postfix/smtpd[6536]: A103655D2B: client=localhost[127.0.0.1]
    Oct  3 13:24:25 server postfix/cleanup[6534]: A103655D2B: message-id=<[email protected]>
    Oct  3 13:24:25 server postfix/smtpd[6536]: disconnect from localhost[127.0.0.1]
    Oct  3 13:24:25 server postfix/qmgr[6000]: A103655D2B: from=<[email protected]>, size=1642, nrcpt=1 (queue active)
    Oct  3 13:24:25 server postfix/smtp[6535]: 4233F55D22: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.5, delays=0.58/0.01/0/0.92, dsn=2.0.0, status=sent (250 2.0.0 from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as A103655D2B)
    Oct  3 13:24:25 server postfix/qmgr[6000]: 4233F55D22: removed
    Oct  3 13:24:25 server postfix/pipe[6539]: A103655D2B: to=<[email protected]>, relay=dovecot, delay=0.14, delays=0/0.1/0/0.04, dsn=2.0.0, status=sent (delivered via dovecot service)
    Oct  3 13:24:25 server postfix/qmgr[6000]: A103655D2B: removed
    Oct  3 13:24:50 server postfix/smtp[6522]: connect to gmail-smtp-in.l.google.com[74.125.45.26]:25: Operation timed out
    Oct  3 13:25:20 server postfix/smtp[6522]: connect to alt1.gmail-smtp-in.l.google.com[74.125.113.26]:25: Operation timed out
    Oct  3 13:25:50 server postfix/smtp[6522]: connect to alt2.gmail-smtp-in.l.google.com[209.85.143.27]:25: Operation timed out
    Oct  3 13:26:20 server postfix/smtp[6522]: connect to alt3.gmail-smtp-in.l.google.com[209.85.229.27]:25: Operation timed out
    Oct  3 13:26:50 server postfix/smtp[6522]: connect to alt4.gmail-smtp-in.l.google.com[74.125.79.26]:25: Operation timed out
    Oct  3 13:26:50 server postfix/smtp[6522]: 4F58255B30: to=<[email protected]>, relay=none, delay=1673, delays=1523/0.02/150/0, dsn=4.4.1, status=deferred (connect to alt4.gmail-smtp-in.l.google.com[74.125.79.26]:25: Operation timed out)
    Oct  3 13:27:44 server postfix/anvil[6529]: statistics: max connection rate 1/60s for (smtpd:17.148.16.105) at Oct  3 13:24:23
    Oct  3 13:27:44 server postfix/anvil[6529]: statistics: max connection count 1 for (smtpd:17.148.16.105) at Oct  3 13:24:23
    Oct  3 13:27:44 server postfix/anvil[6529]: statistics: max cache size 1 at Oct  3 13:24:23
    Oct  3 13:40:48 server postfix/postfix-script[6847]: refreshing the Postfix mail system
    Oct  3 13:40:48 server postfix/master[5730]: reload -- version 2.8.3, configuration /etc/postfix
    Oct  3 13:40:56 server postfix/postfix-script[6862]: refreshing the Postfix mail system
    Oct  3 13:40:56 server postfix/master[5730]: reload -- version 2.8.3, configuration /etc/postfix
    Oct  3 13:41:41 server postfix/postscreen[6897]: CONNECT from [209.85.212.50]:44334
    Oct  3 13:41:47 server postfix/postscreen[6897]: PASS NEW [209.85.212.50]:44334
    Oct  3 13:41:48 server postfix/smtpd[6898]: connect from mail-vw0-f50.google.com[209.85.212.50]
    Oct  3 13:41:48 server postfix/smtpd[6898]: C4E6056082: client=mail-vw0-f50.google.com[209.85.212.50]
    Oct  3 13:41:48 server postfix/cleanup[6905]: C4E6056082: message-id=<[email protected]>
    Oct  3 13:41:48 server postfix/qmgr[6867]: C4E6056082: from=<[email protected]>, size=1058, nrcpt=1 (queue active)
    Oct  3 13:41:49 server postfix/smtpd[6909]: connect from localhost[127.0.0.1]
    Oct  3 13:41:49 server postfix/smtpd[6909]: E25D55608F: client=localhost[127.0.0.1]
    Oct  3 13:41:49 server postfix/cleanup[6905]: E25D55608F: message-id=<[email protected]>
    Oct  3 13:41:49 server postfix/smtpd[6909]: disconnect from localhost[127.0.0.1]
    Oct  3 13:41:49 server postfix/qmgr[6867]: E25D55608F: from=<[email protected]>, size=1483, nrcpt=1 (queue active)
    Oct  3 13:41:49 server postfix/smtp[6906]: C4E6056082: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.2, delays=0.17/0.01/0/1, dsn=2.0.0, status=sent (250 2.0.0 from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as E25D55608F)
    Oct  3 13:41:49 server postfix/qmgr[6867]: C4E6056082: removed
    Oct  3 13:41:49 server postfix/pipe[6912]: E25D55608F: to=<[email protected]>, relay=dovecot, delay=0.07, delays=0/0.01/0/0.05, dsn=2.0.0, status=sent (delivered via dovecot service)
    Oct  3 13:41:49 server postfix/qmgr[6867]: E25D55608F: removed
    Oct  3 13:42:12 server postfix/postscreen[6897]: CONNECT from [99.226.73.47]:46511
    Oct  3 13:42:12 server postfix/postscreen[6897]: PASS OLD [99.226.73.47]:46511
    Oct  3 13:42:12 server postfix/smtpd[6922]: connect from cpe24ab81b72821-cm0023bee0ddf0.cpe.net.cable.rogers.com[99.226.73.47]
    Oct  3 13:42:12 server postfix/smtpd[6922]: 69F7C560A1: client=cpe24ab81b72821-cm0023bee0ddf0.cpe.net.cable.rogers.com[99.226.73.47], sasl_method=CRAM-MD5, [email protected]
    Oct  3 13:42:12 server postfix/cleanup[6905]: 69F7C560A1: message-id=<[email protected]>
    Oct  3 13:42:12 server postfix/qmgr[6867]: 69F7C560A1: from=<[email protected]>, size=578, nrcpt=1 (queue active)
    Oct  3 13:42:12 server postfix/smtpd[6909]: connect from localhost[127.0.0.1]
    Oct  3 13:42:12 server postfix/smtpd[6909]: C90D0560A7: client=localhost[127.0.0.1]
    Oct  3 13:42:12 server postfix/cleanup[6905]: C90D0560A7: message-id=<[email protected]>
    Oct  3 13:42:12 server postfix/smtpd[6909]: disconnect from localhost[127.0.0.1]
    Oct  3 13:42:12 server postfix/qmgr[6867]: C90D0560A7: from=<[email protected]>, size=1003, nrcpt=1 (queue active)
    Oct  3 13:42:12 server postfix/smtp[6906]: 69F7C560A1: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.41, delays=0.28/0/0/0.13, dsn=2.0.0, status=sent (250 2.0.0 from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as C90D0560A7)
    Oct  3 13:42:12 server postfix/qmgr[6867]: 69F7C560A1: removed
    Oct  3 13:42:18 server postfix/smtpd[6898]: disconnect from mail-vw0-f50.google.com[209.85.212.50]
    Oct  3 13:42:43 server postfix/smtp[6930]: connect to aspmx.l.google.com[74.125.47.27]:25: Operation timed out
    Oct  3 13:43:12 server postfix/smtpd[6922]: disconnect from cpe24ab81b72821-cm0023bee0ddf0.cpe.net.cable.rogers.com[99.226.73.47]
    Oct  3 13:43:13 server postfix/smtp[6930]: connect to alt1.aspmx.l.google.com[74.125.113.26]:25: Operation timed out
    Oct  3 13:43:43 server postfix/smtp[6930]: connect to alt2.aspmx.l.google.com[209.85.143.27]:25: Operation timed out
    Oct  3 13:44:13 server postfix/smtp[6930]: connect to aspmx2.googlemail.com[74.125.43.27]:25: Operation timed out
    Oct  3 13:44:43 server postfix/smtp[6930]: connect to aspmx3.googlemail.com[74.125.127.27]:25: Operation timed out
    Oct  3 13:44:43 server postfix/smtp[6930]: C90D0560A7: to=<[email protected]>, relay=none, delay=150, delays=0.01/0.01/150/0, dsn=4.4.1, status=deferred (connect to aspmx3.googlemail.com[74.125.127.27]:25: Operation timed out)
    Oct  3 13:45:56 server postfix/qmgr[6867]: DB12F55B8B: from=<[email protected]>, size=119078, nrcpt=1 (queue active)
    Oct  3 13:46:26 server postfix/smtp[6930]: connect to mx1.rog.mail.yahoo.com[98.139.214.154]:25: Operation timed out
    Oct  3 13:46:32 server postfix/anvil[6902]: statistics: max connection rate 1/60s for (smtpd:209.85.212.50) at Oct  3 13:41:48
    Oct  3 13:46:32 server postfix/anvil[6902]: statistics: max connection count 1 for (smtpd:209.85.212.50) at Oct  3 13:41:48
    Oct  3 13:46:32 server postfix/anvil[6902]: statistics: max cache size 2 at Oct  3 13:42:12
    Oct  3 13:46:56 server postfix/smtp[6930]: connect to mx1.rog.mail.yahoo.com[98.136.59.15]:25: Operation timed out
    Oct  3 13:47:26 server postfix/smtp[6930]: connect to mx2.rog.mail.yahoo.com[98.136.59.15]:25: Operation timed out

    I have same problem with Apple Mail at ATT as ISP. I used the program ATTYahoo!EmailSetup from their website. Now I can rarely send any email, from my work email or from my MobileMe email. I seems like that program messed up the entire Apple Mail client so it can no longer send mail. Emails I try to send just sit the in Outbox. Does anyone have a solution?

  • Blocking OUTGOING eMail to certain addresses

    In looking up this question, I found this http://discussions.apple.com/thread.jspa?messageID=3321398&#3321398 and was wondering if I could change the RegEx to:
    /^To: .*<annoying@domain\.com>/ DISCARD
    so as to deny the server from sending any email to the annoying eMail address?
    And instead of quietly, make it known to the sender that the address is not allowed, denied, can't be sent to, should not be disturbed, etc...

    Almost.... except that the "To:" header is not present when the message first goes from the mail client to your server (or at least that is what I have found).
    The only header which can be searched is the first one added by your server (this is the bottom one if you look at the Full Headers of an incoming email), e.g,...
    Received: from [10.0.0.105] (unknown [10.0.0.105]) by mail.panoramicscotland.com (Postfix) with ESMTP id 4D3AB45133 for <[email protected]>
    So your entry in the header_check file would be (for the above)...
    /^Received.for.<[email protected]>/ REJECT No sending to this address!
    The ".*" each side of the "for" will expand to the other text in the header.
    What the sender will get is an immediate "Error" message displayed by their email client, displaying the text after the REJECT text as the reason for the error.
    Give it a go - it's real easy to set up.
    Note you need to issue a 'postfix reload' after creating/editing the header_check file.
    -david
        Server 10.4.8

  • Windows Live Mail 2012 - Outgoing Email Times Out due to Lost Server Connection

    Using Windows Live Mail 2012 on WIN7 64-bit.
    Been receiving emails seemingly without issues, but...
    Haven't been able to POST any outgoing emails now since September 16th for any of my main/sub accounts.
    Indicator is a Norton Internet Security popup stating:
    "Email Error. Your email message was unable to be sent because the connection to your email server was interrupted. Please open your email client and resend the message from the Sent Messages folder." Then it lists the from/to/subj.
    I recompose and try to resend; same results.
    I've rolled WIN7 back to September 6th, but results are the same.
    I thought perhaps NIS was blocking the SMTP port, but same results when I turn off NIS and Antivirus. I don't see anything of significance in NIS's logs.
    Of course, Verizon's mini-app that sniffs out and corrects email problems does not know or care about Live Mail. Just Outlook and OE.
    Ideas? Things to try? Thanks.
      ...Karl
    Solved!
    Go to Solution.

    GeezingInVA2 wrote:
    I noticed my email account server settings don't match what is defined on the FiOS email setup page on verizon.com.
    The server setting I have for my POP3 is "incoming.verizon.net" (not pop.verizon.net) and my SMTP server setting is "outgoing.verizon.net" (not smtp.verizon.net).
    Why don't these match? 
    Also, my port settings don't seem to match what's posted online.
    My outbound port is 25 (not 465) and my inbound port is 110 (not 995).
    Doesn't seem right to me, and I'm wondering what changed in the past week?
    The changes to pop/smtp from incoming/outgoing have been in the works for a while. Maybe Verizon finally go around to disabling the old servers?
    Either way, you should update to the latest settings.
    For the sake of example, we are going to pretend that we are setting up fictional account "[email protected]" and the password for logging into that account in webmail is "fakepassword" - Again, this is a fictitious account for the sake of an example.
    The settings for using Verizon's servers would be:
    Incoming Server: pop.verizon.net
    Server Requires Authentication: Yes
    Username: fakeacct
    Password: fakepassword
    Requires a Secure Connection (SSL): Yes
    Port: 995
    Outgoing Server: smtp.verizon.net
    Server Requires Authentication: Yes (You can set it to use the same settings as incoming, or manually enter the username and password.)
    Requires a Secure Connection (SSL): Yes
    Port: 465
    If you are given the option anywhere for Secure Password Authentication (SPA), set it to No or Normal
    If a forum member gives an answer you like, give them the Kudos they deserve. If a member gives you the answer to your question, mark the answer as Accepted Solution so others can see the solution to the problem.
    "All knowledge is worth having."

  • Outgoing emails being blocked by spamhaus. Blocking my IP address

    Good day
    My outgoing emails are being blocked. Spamhaus has blocked my IP address. How do I unblock it? This is the error message that I receive.
    This message was created automatically by mail delivery software.
    A message that you sent could not be delivered to one or more of its
    recipients. This is a permanent error. The following address(es) failed:
    [email protected]
    SMTP error from remote mail server after MAIL FROM:<[email protected]> SIZE=484112:
    host mta6.am0.yahoodns.net [98.136.216.26]: 553 5.7.1 [BL21] Connections will not be accepted from 41.76.215.245, because the ip is in Spamhaus's list; see http://postmaster.yahoo.com/550-bl23.html
    Please help as this is a business address
    Thanks

    Your email provider controls the IP address they assign you. Only they can clear the reputation of a blacklisted IP address. Contact them.

  • Outgoing Email Setup for Knology - Does anyone know the server setting?

    A friend cannot find the Knology server settings for outgoing mail...Knology company was no help.
    Does anyone know the proper settings?
    Thanks

    DBunch07,
    I was able to find this site in their support pages:
    http://support.knology.net/content/email.setup.cfm
    If the suggested setting from there smtp.knology.net, does not work, they may require different settings for when you aren't connected directly to them. For example when using EDGE or a WiFi Hotspot.
    I have found that asking email provider's tech support for what mail server settings to use while you are travelling and using a laptop will often get the correct settings to use for the iPhone. However, if they say they only offer webmail for when you are travelling, you will not be able to use their outgoing server on EDGE or at WiFi Hotspots, because they have chosen to block outgoing access when you are not on their network.
    While connected to EDGE, you can use cwmx.com to send email out. It only works while on EDGE, and does not require a username or password, since it goes off of the authentication for using EDGE with AT&T.
    AT&T's knowledge base article about cwmx.com is here:
    http://www.wireless.att.com/support/knowledgeBase.do?content=KB72769.html
    You will have to turn off WiFi when you want to send email though.
    This article discusses the issues in more depth:
    http://docs.info.apple.com/article.html?artnum=305634
    Hope this helps,
    Nathan C.

  • E-mail looses all images if mail server doesn't accept outgoing email...

    I open some web page in Safari, press Command+i, new email message is created and all web page content is inserted in the email message, including all images. Nice! I enter email address and send email.
    If for some reason outgling mailserver doesn't accept my outgoing email, the same email is shown again to let me choose another outgoing mail server.
    BUT - at this time all images in the email body are gone! Instead of the images I see blue rectangles with the white question marks on them. And if I proceed and send such email via another email server, recipients get email from me without pictures embedded in the email.
    Can Apple fix this bug? It's really annoying, because quite often outgoing mail server of my ISP is not accepting my outgoing emails and I cannot resend email through another mail server, because images are already lost - I have to delete email, switch back to Safari, again Command+i, again enter email address and then change email account and then try to send again...

    Posting this here is a good idea if you’re looking for possible solutions/workarounds, but if all you want is to let Apple know so that it’s fixed, you’d better do it in one of the following places:
    http://www.apple.com/macosx/feedback/
    http://developer.apple.com/bugreporter/

Maybe you are looking for