email from HSBC bouncing
Les
address <state...@email1.hsbc.co.uk> being bounced. This is the
second month that they have been unable to send me an email due to
it bouncing.
Strangely enough emails from that address get through from their
automated reply service when registering for online statement
notification.
--
Les
Denis McMahon
I didn't think demon bounced for anything except non RFC compliance.
I certainly get enough blatant phishing attempts in my mail here that if
they are filtering they're failing dismally.
Although, this is new C&W Demon isn't it ... You haven't enabled a mail
filtering option somewhere on an account management page have you?
Do you use pop3 collection or smtp delivery to your client? If it's
smtp, it could be your client that's doing the bouncing.
If you use pop3, do you ever use the webmail interface to check there's
nothing on webmail that hasn't been collected?
Do you have any details about the bounce? Usually there's a reason, and
you seem certain that the email is being bounced back to HSBC, so I
assume you've spoken to them at some technical level? Did they give you
the 4xx or 5xx reason code for the bounce?
RFC 2821 lists:
421 <domain> Service not available, closing transmission channel
(This may be a reply to any command if the service knows it
must shut down)
450 Requested mail action not taken: mailbox unavailable
(e.g., mailbox busy)
451 Requested action aborted: local error in processing
452 Requested action not taken: insufficient system storage
500 Syntax error, command unrecognized
(This may include errors such as command line too long)
501 Syntax error in parameters or arguments
502 Command not implemented (see section 4.2.4)
503 Bad sequence of commands
504 Command parameter not implemented
550 Requested action not taken: mailbox unavailable
(e.g., mailbox not found, no access, or command rejected
for policy reasons)
551 User not local; please try <forward-path>
(See section 3.4)
552 Requested mail action aborted: exceeded storage allocation
553 Requested action not taken: mailbox name not allowed
(e.g., mailbox syntax incorrect)
554 Transaction failed (Or, in the case of a connection-opening
response, "No SMTP service here")
Rgds
Denis McMahon
Darren Salt
[snip]
> Do you have any details about the bounce? Usually there's a reason, and you
> seem certain that the email is being bounced back to HSBC, so I assume
> you've spoken to them at some technical level? Did they give you the 4xx or
> 5xx reason code for the bounce?
4xx codes are 'soft' errors; the client (in this case, presumably HSBC)
should retry after a reasonable interval.
> RFC 2821 lists:
[421, 450, 451, 452, 500, 501, 502, 503, 504, 550, 551, 552, 553, 554]
To those, RFC 5321 adds:
455 Server unable to accommodate parameters
555 MAIL FROM/RCPT TO parameters not recognized or not implemented
--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon
| using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army
| + http://www.xine-project.org/
He who believes the past cannot be changed has not yet written his memoirs.
John Hall
Are you sure that:
1. They have the correct email address for you.
2. That it's Demon rather than your own system which is doing the
bouncing.
If the answer is "yes" to both, I wonder if there have been so many fake
phishing HSBC emails that look very similar to the genuine ones, that
Demon's Cloudmark spam filter is bouncing the genuine ones as well by
mistake.
ISTR that it's possible to turn off the filtering for one's account, at
the risk of possibly getting a very large amount of spam.
--
John Hall "[It was] so steep that at intervals the street broke into steps,
like a person breaking into giggles or hiccups, and then resumed
its sober climb, until it had another fit of steps."
Ursula K Le Guin "The Beginning Place"
Richard Clayton
McMahon <denis.m....@gmail.com> writes
>Les wrote:
>
>> Has anyone else had a problem with emails from the HSBC credit card
>> address <state...@email1.hsbc.co.uk> being bounced. This is the
>> second month that they have been unable to send me an email due to
>> it bouncing.
>>
>> Strangely enough emails from that address get through from their
>> automated reply service when registering for online statement
>> notification.
>
>I didn't think demon bounced for anything except non RFC compliance.
the OP may have Demon's spam filter turned on...
... but as usual, it's seldom possible to debug mail problems without
sight of the "bounce message" (and preferably its headers)
>I certainly get enough blatant phishing attempts in my mail here that if
>they are filtering they're failing dismally.
the senders of phish put considerable effort into evading spam filters
--
richard writing to inform and not as company policy
"Assembly of Japanese bicycle require great peace of mind" quoted in ZAMM
John Hall
>address <state...@email1.hsbc.co.uk> being bounced. This is the
>second month that they have been unable to send me an email due to
>it bouncing.
An additional thought. You could try asking them in future to send
emails to postmaster@ your domain. One would hope that Demon's spam
filtering system wouldn't bounce emails sent to that address.
Incidentally, I believe that bounce messages from Demon contain
instructions to the sender of the bounced message for what to do if a
message has been incorrectly bounced.
Andy
<nospam...@jhall.co.uk> wrote
[
>
>Incidentally, I believe that bounce messages from Demon contain
>instructions to the sender of the bounced message for what to do if a
>message has been incorrectly bounced.
The emails are probably sent entirely automatically, and from an address
that bins all incoming emails.
--
Andy Taylor [Editor, Austrian Philatelic Society].
Visit <URL:http://www.austrianphilately.com>
Ian
Salt <ne...@youmustbejoking.demon.cu.invalid> writes
>I demand that Denis McMahon may or may not have written...
>
>[snip]
>> Do you have any details about the bounce? Usually there's a reason, and you
>> seem certain that the email is being bounced back to HSBC, so I assume
>> you've spoken to them at some technical level? Did they give you the 4xx or
>> 5xx reason code for the bounce?
>
>4xx codes are 'soft' errors; the client (in this case, presumably HSBC)
>should retry after a reasonable interval.
>
>> RFC 2821 lists:
>[421, 450, 451, 452, 500, 501, 502, 503, 504, 550, 551, 552, 553, 554]
>
>To those, RFC 5321 adds:
>
> 455 Server unable to accommodate parameters
> 555 MAIL FROM/RCPT TO parameters not recognized or not implemented
>
I've been with them since they took over Midland, and the only emails
I've had from HSBC have been of the phishing variety.
--
Ian
Les
McMahon <denis.m....@gmail.com> writes
>Les wrote:
>
>> Has anyone else had a problem with emails from the HSBC credit card
>> address <state...@email1.hsbc.co.uk> being bounced. This is the
>> second month that they have been unable to send me an email due to
>> it bouncing.
>> Strangely enough emails from that address get through from their
>> automated reply service when registering for online statement
>> notification.
>
>I didn't think demon bounced for anything except non RFC compliance.
The letter I got from HSBC said that the email had been returned as
undeliverable but they seem unable to give me any other details.
>I certainly get enough blatant phishing attempts in my mail here that
>if they are filtering they're failing dismally.
I get phishing attempts supposedly from a number of banks and I have
K9 set up to trap them. All genuine mail from HSBC gets through ok
and the email address used for the reported undeliverable emails to
me got through ok when I registered to stop paper statements.
>Although, this is new C&W Demon isn't it ... You haven't enabled a mail
>filtering option somewhere on an account management page have you?
No the only filtering is done by Cloudmark and locally with K9.
>Do you use pop3 collection or smtp delivery to your client? If it's
>smtp, it could be your client that's doing the bouncing.
POP3 with Turnpike and I've never knowingly had anything rejected from
my end. I accept all mail that is sent and the headers of the mail that
K9
puts into a junk folder are scanned to be sure that any wanted mail
hasn't
been wrongly tagged.
>If you use pop3, do you ever use the webmail interface to check there's
>nothing on webmail that hasn't been collected?
I don't get a large number of emails daily but do occasionally check if
things go suspiciously quiet.
>Do you have any details about the bounce? Usually there's a reason, and
>you seem certain that the email is being bounced back to HSBC, so I
>assume you've spoken to them at some technical level? Did they give you
>the 4xx or 5xx reason code for the bounce?
I don't know if you've tried talking to a banking call centre about
technicalities, they don't really want to know.
>RFC 2821 lists:
>
>421 <domain> Service not available, closing transmission channel
> (This may be a reply to any command if the service knows it
> must shut down)
>450 Requested mail action not taken: mailbox unavailable
> (e.g., mailbox busy)
>451 Requested action aborted: local error in processing
>452 Requested action not taken: insufficient system storage
>500 Syntax error, command unrecognized
> (This may include errors such as command line too long)
>501 Syntax error in parameters or arguments
>502 Command not implemented (see section 4.2.4)
>503 Bad sequence of commands
>504 Command parameter not implemented
>550 Requested action not taken: mailbox unavailable
> (e.g., mailbox not found, no access, or command rejected
> for policy reasons)
>551 User not local; please try <forward-path>
> (See section 3.4)
>552 Requested mail action aborted: exceeded storage allocation
>553 Requested action not taken: mailbox name not allowed
> (e.g., mailbox syntax incorrect)
>554 Transaction failed (Or, in the case of a connection-opening
> response, "No SMTP service here")
>
If I could get a copy of the returned email I may stand a chance of
seeing what is happening but somehow don't think it's a possibility.
I asked the question on here just in case the address used
<state...@email1.hsbc.co.uk> had somehow been blacklisted
by Demon/C&W and someone else here had a similar problem.
I'm going to try again to see if I can talk to someone who can be
bothered to do a test with my email address to prove to them that
it does in fact work. If I get no joy they'll just have to continue
sending me paper statements.
Thanks to all that answered it's much appreciated.
--
Les
Les
<ne...@nospam.demon.co.uk> writes
>In message <50C856FD9C%ne...@youmustbejoking.demon.cu.invalid>, Darren
>Salt <ne...@youmustbejoking.demon.cu.invalid> writes
>>I demand that Denis McMahon may or may not have written...
>>
>>[snip]
>>> Do you have any details about the bounce? Usually there's a reason, and you
>>> seem certain that the email is being bounced back to HSBC, so I assume
>>> you've spoken to them at some technical level? Did they give you the 4xx or
>>> 5xx reason code for the bounce?
>>
>>4xx codes are 'soft' errors; the client (in this case, presumably HSBC)
>>should retry after a reasonable interval.
>>
>>> RFC 2821 lists:
>>[421, 450, 451, 452, 500, 501, 502, 503, 504, 550, 551, 552, 553, 554]
>>
>>To those, RFC 5321 adds:
>>
>> 455 Server unable to accommodate parameters
>> 555 MAIL FROM/RCPT TO parameters not recognized or not implemented
>>
>Are you expecting an email from HSBC?
Thinking that I'd help to save the world I signed up to have my credit
card
statement notification sent by email instead of them sending paper
statements every month. The emails they are supposed to have sent me
for the past two months have according to them been returned as not
being delivered.
>I've been with them since they took over Midland, and the only emails
>I've had from HSBC have been of the phishing variety.
I've been with Midland, HSBC or whoever they happen to be now since
Adam was a boy. I do get genuine emails from them now and again but
phishing ones are more common, for what it's worth I normally forward
them to <phis...@hsbc.com> in the hope that it could be of some
help.
--
Les
Gordon H
<L...@nospam.demon.co.uk> writes
I'm not with HSBC, but the number of emails containing Trojans or
phishing URLs from HSBC (allegedly) is a damned nuisance.
Kaspersky deals with them, but...
--
Gordon H
Remove "invalid" to reply